loic @ cloudinary

Hi @rubymuse,

Thanks for reaching out.

Could you please reach out to [email protected] so we can investigate further? I don’t think it is a bug, we just display the transformations at the taxonomy level when we think it can be useful.

Thanks,
Loic

Hi @qianming,

Basically, what this error means is that your site requires more memory than the default allocated memory provided by your server. It seems quite common with Docker.

You can create the php.ini (or any name.ini) and follow the steps here: https://www.cloudytuts.com/tutorials/docker/how-to-set-php-options-for-wordpress-in-docker/.

Loic

Hi @qianming,

You will need to bump the memory of your Docker instance by adjusting the memory in your php.ini (or creating it) as mentioned here.

Please let me know if that helps.
Best,
Loic

Hi Iver,

Thanks for reaching out.

We are aware of an issue with Unicode characters on ACF where the slash is actually stripped so it might be definitely related to what you mentioned.

You are mentioning 3.0.4 but the issue should also be in 3.0.3. Do you mind letting me know the issues you are facing on your side so we can add this to our test when a fix will be ready?

Thanks in advance.
Best,
Loic

Hi @parakeet,

Effectively, there will be probably some conflicts. On our side, we do need the guid of the asset to be accessible so we can sync it to Cloudinary. I had some cases where users were offloading their assets to S3 and the guid weren’t accessible anymore so you might have this kind of conflict.

On a side note, looking at the support post you opened on the WP Offload Media plugin page, here are some comments:

• You can sync your assets to Cloudinary and use our backup feature to backup your assets to your own storage as documented here so assets are stored in Cloudinary and you have a backup of those in S3 or Google Cloud.
• You mention deleting assets in your WordPress Media Library. Please do not delete assets as they will be deleted in Cloudinary as well (Assets deleted in Cloudinary won’t be deleted from WP but assets deleted in WP are deleted in Cloudinary). What you can do here is use the Cloudinary Only storage options of the plugin to remove assets from your WordPress storage.

Hope that helps.
Best,
Loic

Hi @archonic08,

Thanks for reaching out.

As mentioned in the note here, the plugin only works with a Programmable Media account.

Hope that helps.
Best,
Loic

Hi Fellipe,

Thanks for reaching out.

Normally it shouldn’t have any impacts as it is just a parameter. I had a look at your website but I wasn’t able to locate the issue. Would you mind reaching out to [email protected] with a system report? You can find out how to generate a report here.

Thanks,
Loic