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
{{ message }}
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.
I want blog posts to be accessible the same way as CMS pages are, so I wrote a router that does this. But the URLs that were generated still had the "/blog" base URL in front of them.
When I configured the base URL to be empty, it should generate the URL "https://foo.bar/mirasvit-blog", but this wasn't the case, it generated "https://foo.bar" without the URL key from the blog post behind it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I want blog posts to be accessible the same way as CMS pages are, so I wrote a router that does this. But the URLs that were generated still had the "/blog" base URL in front of them.
Instead of "https://foo.bar/mirasvit-blog" it was "https://foo.bar/blog/mirasvit-blog", even though the blog post was accessible through "https://foo.bar/mirasvit-blog".
When I configured the base URL to be empty, it should generate the URL "https://foo.bar/mirasvit-blog", but this wasn't the case, it generated "https://foo.bar" without the URL key from the blog post behind it.
The text was updated successfully, but these errors were encountered: