-
Notifications
You must be signed in to change notification settings - Fork 111
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
media cleanup #1975
Comments
Hi @felixtech-msp, Thanks for your suggestion. I will forward this suggestion to my team and will need to check the likelihood of adding this feature in future releases. Thanks! |
Is there maybe any quick fix for this? All the created garbage produces catastrophic performance problems (page load time of ~ 5.7 seconds) from selecting so much stuff from the database and loading way too much images to the client. |
Is there any progress on that? Or website is frequently crashing because of the bloard rtMedia folder. |
Hi, Thank you for your patience. We are currently working on finding a solution for it. Hopefully, we will make a fix for it in upcoming releases. I'll keep you updated if we make any progress. Thanks. |
Can you share a bit more details like are you currently using the free version or the paid version of rtMedia, also are you using any add ons. |
As far as I'm aware our customer uses the free version and no special addons. |
By default, rtMedia creates four image sizes in addition to the original image. Additionally, any custom image sizes that are registered in the WordPress theme or by other plugins will also generate corresponding image copies. A possible solution is to disable unused image sizes using the
Note : Regenerate thumbnail will only work with WordPress media library and won't work for a s3 bucket. |
Is your feature request related to a problem? Please describe.
WordPress and rtMedia procude for every image uploaded around 10 copies in total. I have around 78k photos according to rtMedia but over 800k files in the uploads folder. This bloats the filesystem so much that it becomes extremely slow and full.
Describe the solution you'd like
The text was updated successfully, but these errors were encountered: