-
Notifications
You must be signed in to change notification settings - Fork 500
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
Unable to Add Featured Items to Collections – 413 Error #11238
Comments
@ofahimIQSS could be helpful to know the accumulated size of the ten files you attach to the featured items or the size of each file. Many thanks! |
|
I've gotten up to 20 items without failing. All of the png files are large - approaching the 1M limit. Way larger than what was failing for Omer |
Hi @sekmiller , I was able to reproduce this with 2 featured items only, one image was 772kb and the other one 896kb. See screenshot below from HTTPie. Did you try to call the get featured items endpoint after that and verify that you receive the featured items data like:
If you don't receive an imageFileName and imageFileUrl it is because the file was not uplodaded, check that the fileName matches the actual file name when calling the update endpoint. |
|
22 files successful. And if I try the image url I get the file displaying correctly. |
I tried again with .png files and still failing, strange.. |
Omer is now reporting that he can no longer replicate this error |
This is an issue with a setting in the dockerized environment. Updating a config file ( client_max_body_size 20M; to our nginx.conf file) fixes it. Closing |
Description:
Unable to add Featured Items to the Root Collection or any collection. Upon attempting to add multiple items, images, and descriptions, the system displays an undefined message, and the save action fails.
Steps to Reproduce:
Expected Behavior
The system should successfully save the Featured Items and update the collection.
Actual Behavior
An undefined message appears
The save action does not complete
In the network console, a 413 Error (Request Entity Too Large) is observed
See Video and screenshot below:
IQSS/dataverse-frontend#596 (comment)
IQSS/dataverse-frontend#596 (comment)
The text was updated successfully, but these errors were encountered: