Raz @ Cloudinary

Hi @kumarbbit,

Can you please open a support ticket at [email protected], attaching this image of the error, the WP, theme, and plugin versions, while also sharing a list of all activated plugins and lastly your cloud name, so we can take a deeper look into this?

In addition, if you could state on the ticket whether you upgraded from v1 of the plugin or installed v2 from scratch and whether you see this error when trying to access wp-admin or when performing a certain action, that would be helpful as well.

Thanks,
Raz

@macmacch thanks for creating the support ticket.
Please let me know if the issue was resolved for the first cloud you were experiencing this on and also make sure that you specify within the ticket’s thread the additional cloud names of your other two WordPress sites, so the same solution will be applied for all.

Best,
Raz

• This reply was modified 4 years, 6 months ago by Raz @ Cloudinary.

Hi @macmacch,

I’m afraid that at the moment there’s no option to exclude PDFs in the sync operation.

Can you please open a ticket via [email protected], sharing your cloud name with us, so we can take a deeper look into it and help you with resolving this issue where your PDFs are stuck in syncing mode?

Thanks,
Raz

Hi Angus,

Can you kindly open a support ticket at [email protected] so we can investigate this further?
If possible, please provide a screen recording of the issue along with Dev Tools opened showing both console and network tabs for any possible errors.

Thanks,
Raz

@danielbenjamins

Our dev team assumes that they have found the root cause for the issue you are experiencing, which seems to be an edge case which they currently work on confirming.

Once confirmed this is indeed the case, we will work on issuing a fix for it as soon as possible.

Updates to follow.

Best,
Raz

Hi @sikth,

Can you please share some additional information about the issue you are experiencing?
Most importantly, the exact errors that you see when trying to log in to your WP plugin.

In addition, if you could share any example URLs of images that are currently broken on-site, it will be very helpful in debugging your issue.

Lastly, did you have the v2 beta plugin installed prior to installing the official version released to the Marketplace? If so, did you uninstall/deactivated the beta before installing via the Marketplace?

If you prefer continuing the investigation privately, please open a support ticket at [email protected] and I will make sure you will receive a lightning-fast response to your ticket from our support team.

Best,
Raz

Hi @red_wolf and @angah85,

The new plugin’s architecture is designed to keep the WordPress storage in-sync with Cloudinary. Meaning, assets are stored in both places, and that might increase the WordPress storage or the Cloudinary storage (depending on whether you’ve moved from v1 or had a fresh install).

This was implemented to deal properly with the scenario where one decides to disable the plugin. In such case, all assets must return to be delivered from the local environment, to avoid any broken URLs of delivered assets. It also allows us to fall-back to the local storage in case anything goes wrong.

With that being said, it is indeed on our roadmap to allow users to use our plugin without having to keep the assets stored in their local storage too, for as long as the plugin is active.

• This reply was modified 4 years, 7 months ago by Raz @ Cloudinary.

Hi Darren,

Have you uninstalled/deactivated v1 of the plugin before manually installing the v2 beta package?

Thanks,
Raz