You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The WordPress template hierarchy allows us to use index.php to route users onward, but we're not presently passing on any paths, so internally set links such as attachment pages and permalinks shown in the admin are incorrect.
Ideally we should be able to configure the appropriate offsite routes to correspond with each template and pass on any necessary parameters such as post IDs and slugs. We'll probably not be able to set an alternate domain however so we should also conditionally redirect depending on the query.
While this is all of course possible with Apache rewrites (which can also be simplified with plugins), the goal here is surface these dependencies and get them pointing to valid pages. The underlying implementation may still rely on these however. See also #2.
The text was updated successfully, but these errors were encountered:
My understanding of how the offsite routes work is that it would depend on which hbs template in a Solidus site includes a post/page resources via the API. In theory, it could be included in any page on the Solidus site, there's not necessarily a 1-to-1 correlation. I'm not sure if there's really a way to detect the offsite routes from WordPress, so it would have to be manually entered in the WP admin.
The WordPress template hierarchy allows us to use
index.php
to route users onward, but we're not presently passing on any paths, so internally set links such as attachment pages and permalinks shown in the admin are incorrect.Ideally we should be able to configure the appropriate offsite routes to correspond with each template and pass on any necessary parameters such as post IDs and slugs. We'll probably not be able to set an alternate domain however so we should also conditionally redirect depending on the query.
While this is all of course possible with Apache rewrites (which can also be simplified with plugins), the goal here is surface these dependencies and get them pointing to valid pages. The underlying implementation may still rely on these however. See also #2.
The text was updated successfully, but these errors were encountered: