I’m seeing some odd behavior with permalinks on our site. I have a permalink set up to https://support.glitch.com/office-hours which works from a fresh session (in an incognito window, for instance, or even just a new tab) By “works” I mean it returns a 301 redirect to the location configured in /admin/customize/permalinks as I’d expect
I have that link inside a different post on the forum, though, and when that link is followed I get this:
The correct page loads on refresh, but as you might imagine this looks pretty unprofessional to our members. Is there some reason I don’t know about that would prevent that from working?
Permalinks are intended to remap inbound links to your Discourse instance, and are useful when migrating from another platform. They catch inbound traffic and reroute those requests to the new destination, which is why they work when you hit refresh.
They’re not going to work within Discourse itself, please use the correct internal URL, rather than the permalink that you’ve created which redirects to it.
Thanks for the replies, y’all - I’m not managing that Discourse instance any more and we no longer “need” this functionality, but it’d be nice to know it’s there.
@tshenry it seems to me that your example is what was discussed above as an “external” link, though, right? Taking a request from an external source and redirecting it to the proper Discourse URL - what we were hoping to do would be akin to redirecting support - Discourse Meta to Pull requests · discourse/discourse · GitHub (if you all accepted issue reports there, of course), which worked (as I recall) for folks coming into the site from outside, but failed to redirect on the first page load when following a link from a Discourse page.
Ha, I initially thought you meant there was an example on that page - once I realized you meant that was the example, then yes, that seems to do what we wanted. Thanks!!
- once I realized you meant that was the example, then yes, that seems to do what we wanted. Thanks!!