-
Notifications
You must be signed in to change notification settings - Fork 245
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
File Field: Optimize inital field load to remove ajax #1083
Comments
Hm I have read into the code and I see why you guys do it like this now. But I think we can cache the network request. The file shouldn't change unless someone uses a file replace plugin. But even then they can clear the cache in their browser. |
Same here + |
I encountered a similar situation with over 100 requests that were additionally timing out due to Nginx limit_req rules. In my scenario, "tabs" are used for the file structure, and each tab holds many files. Is there a way to only load the current tab and ajax request the others when clicked on? Or, was there a further resolution to this issue by introducing caching or other means? |
Same here! Is there any way to disable the AJAX requests? Or maybe apply lazy loading? |
Version
Expected Behavior
The file field should load the file data as a html element property initially without an ajax request.
Actual Behavior
The file field sends 40 ajax requests when there is 40 file fields which makes no sense when you have large repeater fields.
Container definition
Steps to Reproduce the Problem
Comments
I tried to debug this myself but ran into dependency issues, what NodeJS version are you using for this project?
My idea is to just remove the ajax code and add necessary information to the React component using attributes. By the time the user loads the page the second time the attachment should be cached anyway and this removes setting up a new network request just to get a singular file, or 40 when there is a lot.
The text was updated successfully, but these errors were encountered: