Bulk smush doesn’t work
-
I’m trying to compress images using bulk smush, but the progress bar always freezes at the beginning
The images have status Smush already in progress
But when I access wordpress media, I see that the images have not been compressed
I try to activate smush through WordPress media but the images have the status File processing is in progress.
Could you help me please?
The page I need help with: [log in to see the link]
-
I hope you are doing well today.
In the first place please check if there are any errors in the browser console. If so, please share a screenshot with us in your next reply.
Secondly, this issue could be a plugin conflict. Would you please run a conflict test? Please deactivate all plugins except Smush and check if the problem is gone. If so, then enable all plugins one by one and find which one is having a conflict. If there is no positive result, switch to the default WordPress theme like 2019, and see if it works. Before this test, we recommend full site backup or running this test on the staging site.
Thirdly, please let us know what is your max_execution_time and memory_limit.
And the last one: can you add this code to your wp-config.php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);also delete (if exists)
define('WP_DEBUG', false);
The line should be placed above the “/* That’s all, stop editing! Happy blogging. */”
This will generate in the /wp-content/ folder a debug.log file. Please check if there are any errors related to Smush.
Kind Regards,
KrisHi @rafaelpires20,
Since we haven’t heard back from you in a while, I’ll mark this topic as resolved. If you have any further questions or need assistance, don’t hesitate to let us know!
Kind Regards,
Nebu JohnHello @wpmudevsupport13 @wpmudevsupport14
I made a copy of the website at salvatorego.com.br/teste
I deactivated all plugins and left only smush
I changed the website theme to the default wordpress theme
max_execution_time 360
memory_limit 1024M
but I was not successful
Below is what the debug.log file reports:
[06-Nov-2024 22:10:44 UTC] Automatic updates starting…
[06-Nov-2024 22:10:44 UTC] Automatic plugin updates starting…
[06-Nov-2024 22:10:44 UTC] Automatic plugin updates complete.
[06-Nov-2024 22:10:44 UTC] Automatic updates complete. [06-Nov-2024 22:17:22 UTC] PHP Fatal error: Maximum execution time of 180 seconds exceeded in /home1/wwwsalvatoregoco/public_html/teste/wp-includes/Requests/src/Transport/Curl.php on line 275thanks
Fatal error: Maximum execution time of 180 seconds exceeded in
The above error still points the max_execution_time is 180. Could we know how you have increased max_execution_time to 360?
To confirm the current value picked, please create a PHP file, eg test.php inside the root directory and add the following code:
<?php phpinfo(); ?>
The root directory is where you notice /wp-admin, /wp-content/, /wp-includes folders.
Once done, open the file in your browser, ie suppose the domain is abc.com, you can open the file by loading abc.com/test.php
Please do check the value of max_execution_time listed in there and if it’s still 180 then it would require a change within the server side. Getting in touch with your hosting provider would be ideal to increase it.
If you still have issues even after the above then please do check how it behaves when you add the following define inside the wp-config.php file:
define('WP_SMUSH_TIMEOUT', 150);
Please make sure to add the above code before the line /* That’s all, stop editing! Happy blogging. */ in the wp-config.php file.
Regards,
Nithin
Hello @wpmudevsupport11
Follow their instructions, see this link https://salvatorego.com.br/teste/test.php I have max_execution_time 360
I also put the code define(‘WP_SMUSH_TIMEOUT’, 150); in wp-config but I still have difficulty smushing images
Hi @rafaelpires20,
but I still have difficulty smushing images
The previous suggestion was based on the debug log shared. Could you please delete the debug.log file and re-check whether you get the same error with Maximum execution time again in the newly generated debug.log?
The above will give a better idea if it’s still the same error that getting listed in the debug.log file or something new.
If it’s still the same error with Maximum execution time then could we know whether you checked with your hosting provider regarding it? As it’s still a server-specific error.
Please do let us know what your hosting provider has to say regarding the error too. Looking forward to your response.
Kind Regards,
Nithin
Hello @rafaelpires20,
I hope the above suggestions helped.
We haven’t heard back from you for some time, so I’m marking this thread as resolved. Please feel free to reopen it and reply if you need our further assistance.
Best Regards,
DmytroHello @wpmudevsupport11 ,
I deleted the debug.log file and did the bulk smush procedure again in the log file, it did not report any problems with Maximum execution time
presents this excerpt below:
[18-Nov-2024 14:21:16 UTC] Automatic updates starting…
[18-Nov-2024 14:21:16 UTC] Automatic plugin updates starting…
[18-Nov-2024 14:21:16 UTC] Automatic plugin updates complete.
[18-Nov-2024 14:21:16 UTC] Automatic theme updates starting…
[18-Nov-2024 14:21:16 UTC] Automatic theme updates complete.
[18-Nov-2024 14:21:16 UTC] Automatic updates complete.But mass smush still doesn’t work
By accessing the address https://salvatorego.com.br/teste/test.php it is possible to see that max_execution_time is 360
Hi @rafaelpires20 ,
I hope you’re doing well and I’m sorry to see that you’re facing this issue.
Could you please confirm if that’s the entire debug.log file? or are you able to see any other PHP Fatal Error there?
Could you please also use a tool like Google Drive or Dropbox to share a screenshot of the console dev tools from the Browser? You can open it by right-clicking on the bulk smush page after running the bulk smush > Inspect Element.
Here, please find the Console tab and send us a screenshot about that – https://monosnap.com/file/blepJPMP65qonMD69BukGhVwVfyFUN
I hope to hear back from you soon.
Best Regards,
Williams Valerio.
- You must be logged in to reply to this topic.