I’m using the source theme and im trying to have a custom page editadble from a user perspective. I’m using the dynamic routes like this
routes:
/:
data:
post: page.home
template: page
collections:
/events/:
permalink: /events/{slug}/
template: index
filter: primary_tag:events
/newsletter/:
permalink: /newsletter/{slug}/
template: index
filter: primary_tag:newsletter
taxonomies:
tag: /tag/{slug}/
author: /author/{slug}/
When this is used, posts are made and emailed out and the “View in Browser” link doesnt work. but if you go directly to the post view. Am i doing something wrong in the routes? i think ive worked around this in a previous theme by using a custom page template and then using {content} of a #page somehow but cant recall how that was used either. im mostly confused why the view in browser link is going to a 404 with the above routes.
how this differs is with the default collection base url
collections:
/:
permalink: /{slug}/
template: index
if i have the above in the collections along with the events and newsletter filters mentioned previously they do not display any posts but the view in browser link in the email does work.it does look like its loading the partials/components/post-list.hbs in the default source theme as it does display the sidebar section and there is a main.hg-main element when looking in dev tools.
another way to explain what im seeing i guess is say a post is created without the proper tag to have a permalink. the post gets emailed, and someone clicks on the link, it goes to a 404. the view in browser seems to not be stored correctly im guessing in the reference url which looks like some sort of guid that gets stored somewhere. if you add the proper tag later how do you update that?