The only red error we can find when installing the imagify helper plugin is this one:
https://imgur.com/LMol414
Here is the detailed PHP error when trying to optimize an image:
[Sat May 08 16:57:33.860103 2021] [proxy_fcgi:error] [pid 8755:tid 140276660012800] [client XX.77.60.XXX:467XX] AH01071: Got error 'PHP message: PHP Warning: fopen(/tmp/D8A7D8B9D984D8A7D986-D981D98A-D8B4D8A3D986-D8B9D985D984D98AD8A7D8AA-D8A7D984D8AAD8B3D8ACD98AD984-D8A7D984D8AED8A7D8B5D8A9-D8A8D8A7D984D986D8A7D8ACD8ADD98AD986-XXXXXX-D985D8A8D8A7D8B1D8A7D8A9-D8AAD988D8B8D98AD981-D8A3D8B7D8B1-D8A7D984D8A3D983D8A7D8AFD98AD985D98AD8A9D88C-D8A7D984D985D986D8AAD985D98AD986-D984D8ACD987D8A9-D981D8A7D8B3-D985D983D986D8A7D8B3-D981D988D8AC-2021-1_page-0011-qtdrsX.tmp): Failed to open stream: File name too long in /home/XXXXX.cloudwaysapps.com/appname/public_html/wp-includes/Requests/Transport/cURL.php on line 138PHP message: PHP Fatal error: Uncaught TypeError: fclose(): Argument #1 ($stream) must be of type resource, bool given in /home/XXXXX.cloudwaysapps.com/appname/public_html/wp-includes/Requests/Transport/cURL.php:409\nStack trace:\n#0 /home/XXXX.cloudwaysapps.com/appname/public_html/wp-includes/Requests/Transport/cURL.php(409): fclose()\n#1 /home/XXXXX.cloudwaysapps.com/appname/public_html/wp-includes/Requests/Transport/cURL.php(177): Requests_Transport_cURL->process_response()\n#2 /home/XXXXX.cloudwaysapps.com/appname/public_html/wp-includes/class-requests.php(381): Requests_Transport_cURL->request()\n#3 /home/XXXX.cloudwaysapps.com/appname/public_html/wp-includes/class-http.php(394): Requests::request()\n#4 /home/XXXXX.cloudwaysapps.com/appname/public_html/wp-includes/class-http.php(626): WP_Http->request()\n#5 /home/XXXX.cloudwaysapps.com/appname/public_html/wp-includes/http.php(68): WP_Http->get()\n#6 /home/XXXXX.cloudwaysapps.com/appname/public_html/wp-admin/include...', referer: https://www.domain.com/wp-admin/admin-ajax.php?action=imagify_optimize_media&nonce=9dbf9c0c79
Hi @dreamjobma
Thanks for your patience!
What I see, the problem is happening in the tmp folder which is used for processing images.
File name too long
I am not sure if original image name is long as well or it’s just created during the process.
Can you confirm it is Imagick module used in your installation (can be seen in Imagify Tools page)?
If so, can you confirm (or try again) you replaced it with GD as explained in our documentation?
If nothing helps, it would be good to ask Cloudways for some additional help regarding reading logs.
Let’s see what we will get with these and see what to do further.
Best Regards
Marko
Hello,
We have the temporary resolved the issue.
Here is what is happening.
When the file name is too long, imagify just stops working.
You cant optimize any new media.
We had to find all the images with a name too long and delete them 1 by 1 to make it work again.
Here is an example of file too long: https://imgur.com/YIFldsa
The file name lenght seems normal on arabic, but arabic is converted to this:
D8A7D8B9D984D8A7D986-D981D98A-D8B4D8A3D986-D8B9D985D984D98AD8A7D8AA-D8A7D984D8AAD8B3D8ACD98AD984-D8A7D984D8AED8A7D8B5D8A9-D8A8D8A7D984D986D8A7D8ACD8ADD98AD986-XXXXXX-D985D8A8D8A7D8B1D8A7D8A9-D8AAD988D8B8D98AD981-D8A3D8B7D8B1-D8A7D984D8A3D983D8A7D8AFD98AD985D98AD8A9D88C-D8A7D984D985D986D8AAD985D98AD986-D984D8ACD987D8A9-D981D8A7D8B3-D985D983D986D8A7D8B3-D981D988D8AC-2021-1_page-0011
Thats too long for imagify.
Please fix this asap.
Thanks.
Hey,
Thanks for letting me know.
It would be ideal if you could do the test from my previous message and let me know if the same thing happens when GD is active instead of Imagick. Is there a chance to try it out?
Thanks!
