-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add Update button behaviour whilst logged in #407
Comments
@rumca do you still see this behaviour? |
@adriancollier just tested on UAT and the issue seems to have been resolved at some point - I'll close this |
@adriancollier I've just re-encountered this issue on UAT partnersites. When a user isn't logged in: Then when they are logged in: Not sure if we need to address it or not |
After some testing I think the problem is that the Add update button is not shown when you're logged in on the updates listing page. On both the project main page and the single update page it's shown correctly when either 1) the user isn't logged in, or 2) is logged in and allowed to create an update. |
@zzgvh Incorporated your suggestions, can you check again? |
[#407] Updated logic for 'Add update' button
Merged in #683 |
The current functionality seems to grey out the Add Update button when you are not logged in - I thought this should push the user to sign in... |
@adriancollier since this is the current functionality on core RSR should we close the issue? Perhaps we can open a new one for changing it to prompt the user to sign in |
Agree - I'll create a new issue for this. |
Not sure if this is the issue that users were reporting where they were unable to add updates to their projects.
When you are not signed into RSR and are viewing the "Latest updates" page (where all of the updates are listed) there is an option to add an update if you sign in:
However for signed in users, this add update option is not available from this page. Instead users only have the option of adding from the project overview page:
The text was updated successfully, but these errors were encountered: