-
Notifications
You must be signed in to change notification settings - Fork 1
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
Notification rework #501
Notification rework #501
Conversation
Thanks for checking it out. Which type of notification is behaving this way, e.g. 'request accepted', 'role change'? I'm having issues replicating the fault. I don't think the tests cover all types of notifications. Does the issue still occur if you replace |
@chrisma It happend with a "Sudo rights granted" notification. |
While this is a fix, it also diminishes functionality somewhat. I would be interested in a regression test that involves a |
We should definitely think about it! |
This reverts commit 422673c.
Even with empty links on notifications, I cannot reproduce this error. In the Rails console: The only weird behavior I found was with external links, e.g. |
As I'm currently not able to reproduce the issues, neither manually nor with the automated tests, I'm merging this, so that development can continue with these changes. However, please open another issue if errors are found. |
sudo rights granted
notification (i.e. callingmark_as_read_and_redirect
) and runs into "too many redirects"