-
Notifications
You must be signed in to change notification settings - Fork 124
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
Bug: ActionController::InvalidAuthenticityToken in Hyrax::Dashboard::CollectionsController#update when updating banner. #5470
Comments
Testing on nurax-dev is showing that when editing a Collection:
@bwatson78 these are the same errors between the steps on nurax-dev but is it the same error you encountered? The original steps to reproduce reflect that any action at all in Branding causes an error but if there are no Branding files for logo or banner, uploading one or the other does work without errors on nurax-dev. |
@jlhardes It isn't the same error, but I may be able to give you a breadcrumb about the error you're receiving. If you are upgrading versions, too, you may be encountering the same problems we saw earlier. It seems that the storage process for banners and other |
@jlhardes Is there an issue opened for the series of steps you describe? These do seem to be two different issues. |
Possibly related: Issue #5464 which gets an InvalidAuthenticityToken when trying to edit a collection type |
Following steps to reproduce, I'm not able to see this issue on nurax-dev which is at Hyrax 3.3.0. I tested in Chrome.
|
What browser are you using?: This was seen on both Chrome 98+ as well as Safari 15+. |
I have found a fix that works: I've added |
Closed by #5523 |
✅ @jlhardes this ticket passed QA, and is ready to move to |
Descriptive summary
When upgrading from Hyrax v3.2.0 to v3.3.0, we've encountered the following traceback
from the request with the following parameters
I have managed to get banners to save by resetting the page's cache with the
command-shift-r
directive from a Mac, but this isn't ideal.My running theory is that
CSRF
data isn't transferring to and from the AJAX processing of the Uploaded files. Addingremote: true
somewhat fixed the behavior but also stopped the page from redirecting with any error messages that may occur elsewhere.Rationale
This impedes the end user from saving any Uploaded File changes they make.
Expected behavior
Return a message banner stating that the Collection changes have been saved.
Actual behavior
Returns the Fatal Error above.
Steps to reproduce the behavior
Related work
N/A
The text was updated successfully, but these errors were encountered: