-
Notifications
You must be signed in to change notification settings - Fork 493
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
Broken 403 Error pg #5967
Comments
Randomly found this warning/error
|
|
It appears that there was a problem with some special characters in the analytics code (thank you, @landreev), as the first screenshot above outlines. With a little digging, it appears a workaround is the "CDATA trick" added inside the
Creating a pull request for this quick fix, but still plan to investigate if there are other places we should also add the CDATA section to inline javascript code. |
Reviewed all of the
Smoke tested various pgs and features. Can log in, create dataset, upload files, ingest, publish and load version differences as expected. Found a problem on My Data, which was related to |
… Configuration, as well as a release note [ref #5967]
I have been seeing this horrible yellow error pg in my localhost (Firefox, develop v 4.15) a lot lately, while I believe most of them are of the 500 variety, I am creating this issue specifically for the 403, because that's easier for me to reproduce.
Navigate to an unpublished dataset as an admin in one browser, copy and paste the URL into another browser, when prompted log in as a user without access permissions, and boom, ugly error pages.
The Google Chrome version ain't much better.
The 404 pg works as expected, for what it's worth.
This behavior also appears on demo (v 4.14 build 1326-57a392d). However, dataverse-internal (v. 4.15 build 1359-631db06) is properly displaying the 403 error pg in both Firefox and Chrome
The text was updated successfully, but these errors were encountered: