- Issue created by @yurg
- 🇫🇮Finland phonkala
Hey @yurg!
In your use case, I don't think you are using paths at all. Actually, you propably don't even have path aliases on those, based on your example having those IDs in the URL. I mean, aren't the store/1, user/1 and node/1 just default routes with entity id at the end? I think you could just use the basic entity ID (or user ID etc) as the contextual filter and it would work.
For my use case, let's say I got content types "Activity Tracker" and "Activity". I add new "Activity Tracker" called "Fitness Log". For my "Activity Tracker" content type, I set the pathauto pattern to be "/activity-trackers/[node:title]", instead of "/activity-trackers/[node:nid]".
So basicly, I wanted to list all the "Activities" added to that "Fitness Log" activity tracker in "/activity-trackers/fitness-log/activities", instead of the basic "/activity-trackers/1/activities". For this I needed a way to get the entity id from path alias, as the ID wasn't in the URL.
For your use case, I think you would need this module if you want your stores have the name of the store in the URL, for example "/store/my-store" (store ID 1). Then, you could make a View page with path "/store/%/products" and if you used the contextual filter to be converted from path alias, you could access the products via "/store/my-store/products" instead of "/store/1/products".