Critical error after after updating to version 3.1.6

Hi there,

Could you please submit a support ticket at https://support.cloudinary.com/ and generate a system report to help us better investigate this for you?

https://support.cloudinary.com/hc/en-us/articles/360022260599-How-to-generate-a-system-report-on-the-WordPress-plugin-

In addition, please specify the error message (full tracelog) and the error from WordPress as well?

Thanks,

Wissam

Sure. I will create a support ticket there.

This is the error message

An error of type E_ERROR was caused in line 786 of the file /home/synthwavelabs.com/public_html/wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/php/class-assets.php. Error message: Uncaught Error: Call to undefined method Cloudinary\Delivery::clean_url() in /home/synthwavelabs.com/public_html/wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/php/class-assets.php:786

Should I submit the report created in v3.1.5 or v3.1.6? The issue persists with the v 3.1.6.

• This reply was modified 10 months ago by Tharusha Induwara.

Thank you for sharing the error message.
Once you will create the ticket, add the system report with version 3.1.6 where the issue persists.

In addition, if you can share what is the side effect of this error?

Thanks,

Wissam

I experienced a similar problem today, looking for an update before re-activating the plugin – thanks

Wissam, the side effects of this issue are not loading frontend of the website at all, and all the pages are not displaying any content.

Beknowin, you don’t need to deactivate the plugin. Just roll back to the previous version which is v3.1.5.

You can download the previous version via here

Hi @beknowin, as @timaxx mentioned, the issue disappears if you downgrade.

We have an internal ticket on our side for this issue and if you are both able to create a ticket to [email protected] and send a system report as Wissam mentioned earlier, that would definitely be helpful.

Thanks!

Loic

I have raised a ticket with the system report. Also, this is what happens after updating to the newest version v3.1.6. The backend is fine. But the frontend is completely down.

@timaxx thank you.

I had the same issue with the home page but oddly it didn’t impact other pages on my site.

Hi @beknowin, @timaxx,

The issue seems to occur in different ways. We have been able to reproduce it with a specific scenario and the team is working is currently working on a fix for this. We are still gathering data on our side in case the fix doesn’t cover other scenarios that we are able to reproduce.

We will let you know when the fix is released. You can downgrade to 3.1.5 if needed as the error doesn’t occur with this version.

Best,

Loic

• This reply was modified 10 months ago by loic @ cloudinary.

Hi there,

We have just released 3.1.7 that fixes the issue. You should now be able to upgrade without experiencing this issue.

Regards,

Loic

Thank you so much for letting me know about the update. Everything is perfectly working now. Thanks for focusing on this issue and pushing the fix with the update.