- Merge request !22Restore ability for prettiest paths (page/category/example) to work with embedded views → (Open) created by mlncn
We had Facets Pretty Paths and Facets 3.x working great together with the no-query-string (base style, and even had
Entity Reference Filtering Link →
producing links that Facets Pretty Paths handled perfectly, in the style of /projects/services/film-media, via a patch/issue fork:
✨
Make compatible with Facets Pretty Paths
Active
… and then we switched the view from a page display to an embed display, so that content authors could edit the title and frontmatter of the view the same as any content. Notably, this is the same decision that Drupal CMS (fka Starshot) made.
And of course it all stopped working— FPP has no concept of random, technically non-Views, paths.
Observe:
The full solution is probably outside the scope of this module, but Facets Pretty Paths still needs some changes to make it possible, i think.
Or documentation on providing an alternative, and both the route subscriber and the in a separate/sub module.
Confirm/correct and expand on proposed approach.
In Facets Pretty Paths or a submodule or another contributed module,
In Facets Pretty Paths some way to set the base routes that Facets Pretty Paths needs to watch.
None, or a place to store the above base routes.
Pre-generating possibly a million routes is not the way this is done, as i understand it; the base routes are rather extended to have the possibility of up to about forty facets.
So we could produce a route like this: '/node/{node}/{facets_query}/{f0}/{f1}/{f2}/{f3}/{f4}/{f5}/{f6}/{f7}/{f8}/{f9}/{f10}/{f11}/{f12}/{f13}/{f14}/{f15}/{f16}/{f17}/{f18}/{f19}/{f20}/{f21}/{f22}/{f23}/{f24}/{f25}/{f26}/{f27}/{f28}/{f29}/{f30}/{f31}/{f32}/{f33}/{f34}/{f35}/{f36}/{f37}/{f38}'
But probably better in this case not to care about whether it is a node or what that it is being attached to, and use only the path?
'/example-path/{facets_query}/{f0}/{f1}/{f2}/{f3}/{f4}/{f5}/{f6}/{f7}/{f8}/{f9}/{f10}/{f11}/{f12}/{f13}/{f14}/{f15}/{f16}/{f17}/{f18}/{f19}/{f20}/{f21}/{f22}/{f23}/{f24}/{f25}/{f26}/{f27}/{f28}/{f29}/{f30}/{f31}/{f32}/{f33}/{f34}/{f35}/{f36}/{f37}/{f38}'
That means we do not have to worry about separating /node/123/edit or /node/123/revisions/1234/view from the facets. If somebody is using subpath aliases though, do we have to worry about conflicts?
Active
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.