This has just happened to me as well. Reverting back to 2.1.2 fixed my issue.
Cloudinary have really dropped the ball with version 2 of the plugin. We have had a lot of issues and are now thinking of moving away from them.
Hi @mintcanary,
Can you share more detail on the issue you are having? You mentioned that the image paths stopped being replaced with Cloudinary URL, does this mean the URL points to your WP instance (wp-content/uploads/
)?
Can you let me know more about your WP environment?
- WP version
- List of all activated plugins
- Theme used
- Page builder used
Looking forward to your response.
Regards,
Erwin Lukas
@jordanairwave,
I believe you also reported this via Cloudinary Support. We will continue our conversation through that ticket.
Thanks,
Erwin Lukas
Thread Starter
Sam
(@mintcanary)
Yes, as if the plugin were disabled.
WP version: 5.4.2
Custom theme
The environment is essentially this: https://github.com/PhilippHeuer/wordpress-heroku
Hi @mintcanary,
Thanks for the update. Can you also share the list of activated plugins?
Additionally, when using v2.1.9, does this apply to all your WP images or only on certain area? If only on certain area, can you share more details on which area?
Thanks,
Erwin Lukas
Thread Starter
Sam
(@mintcanary)
WooCommerce
Printify Shipping Method
Cloudflare Flexible SSL
I can’t say for sure, I assumed all.
Hi @mintcanary
You can get the full list of plugins by going to the WP Admin page > Plugins, your URL should look like: https://www.example.com/wp-admin/plugins.php
Reason I’m asking for this is to check if there is a plugin that could be conflicting with Cloudinary’s plugin since v2.1.9 and I would like to reproduce this on my environment.
Or if it’s ok with you, I can take a look at your environment. If you are ok with that, please open a ticket on our Support Portal and provide the detail there.
Thanks,
Erwin Lukas
Thread Starter
Sam
(@mintcanary)
The list of plugins is in my previous reply.
Hi @mintcanary,
Thanks for the update. Let me check on this and I’ll get back to you.
Regards,
Erwin Lukas
Hi @mintcanary,
I am closing this thread as this issue should be fixed with any version above v2.2.0.
Best,
Loic