1
Add concurrency protection for generated CSS writes when uploads use remote stream wrappers
Source: elementor/elementor#35790 · opened by @rajandangi
Describe the Problem Elementor currently writes generated CSS files directly to the uploads directory. On sites where wp-content/uploads is backed by a remote stream wrapper, such as S3, Cloudflare R2, or another object-storage offload plugin, concurrent requests can attempt to write the same generated CSS file at the same time. In our case, Elementor Core generates this file: uploads/elementor/design-system-sync/design-system-sync.css When several frontend/admin/REST requests trigger generation at the same time, the same object key can be written multiple times concurrently. This is problematic for object-storage providers. Cloudflare R2, for example, limits concurrent writes to the same object key and returns: Reduce your concurrent request rate for the same object. This causes PHP warnings like: Propose a Solution It would be helpful if Elementor added concurrency protection around generated CSS writes, especially for shared/generated files like: design-system-sy…
No pledges yet. Be the first to back this.
Comments
Similar requests
Allow overriding Elementor uploads directory (decouple from wp_upload_dir())
1 vote · 0 comments
Improve RTL (Right-to-Left) support for multilingual sites
3 votes · 0 comments
🐞 Bug Report: Add a per-page custom css section, as opposed to the current, per element.
1 vote · 0 comments
[Feature Request] Implement functionality to Remove Unused CSS the same way Perfmatters and Flyingpress do
3 votes · 0 comments
Element Manager for Custom CSS
4 votes · 0 comments
No comments yet.