-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trac RSS links broken #204
Comments
Hi and thanks for the report, it's much appreciated. I can indeed reproduce the behavior you're describing, and I agree that it doesn't work as it should. These links are generated automatically by Trac, so I've had a dive in the source code 🤿 . It seems that Trac uses a special Unfortunately I don't see a way to work around Trac's behavior here (not without reimplementing a bunch of templates which is not maintainable), so the solution that remains is to fix #195 . So I'm going to close this issue as a duplicate, but please reopen (or comment) if you have an idea for how to solve this specific issue independently of #195. Have a nice day! ✨ |
Of course after writing this comment I realized there was an easy workaround after all: #206 |
When you are already logged into Django's Trac, the RSS links go to a login page rather than the RSS feed, and there's no obvious way to actually get the RSS.
To reproduce:
Results: you are redirected to the login page (despite already being logged in), with the query "referer" param set to the RSS feed url. But trying to login again there (with GitHub) sends you to the Trac homepage rather than the RSS feed (likely because of #195).
Expected: you should end up on the appropriate RSS feed
Note: these RSS feeds don't actually require login. Also, the "Comma-delimited Text" and "Tab-delimited Text" links at the bottom of the query page don't have this problem.
Workaround: either logout first (the links aren't broken when you're logged out), or ignore the RSS links and instead just append a
format=rss
query param to the query/timeline URL.The text was updated successfully, but these errors were encountered: