Issues after update to 3.0.0

Hi @spidiman,

Thanks for reaching out.

Would you mind creating a support ticket to support@cloudinary.com with the following information:

* WordPress version.
* Cloudinary Plugin’s version.
* The theme that you use and its version.
* A full list of all other plugins that you have installed on your environment.
* Page builders that you actively use.
* A screenshot of your Media Library in list mode.
* A screenshot of your Site Health under the Tools Section.
* Hosting providers & Plan (AWS, WP-Engine, etc..)
* Multisite environment (subdomain/subdirectory)
* Do you have access to the WP-CLI?
* Screenshot of your General Settings section.

Note that since version 2.7.0, you can use the new system report feature in order to generate all the information above except the screenshots. If you can also add some assets to your report as explained here that could be helpful as well.

Once provided, we will take a deeper look into it on our end, trying to reproduce the issue to better understand the root cause for it.

In case it will be necessary, will you be willing to provide us with temporary access to a sandbox environment of your site where we can take a look and debug if needed?

Thanks in advance.
Best,
Loic

• This reply was modified 3 years, 2 months ago by loic @ cloudinary.

We have also had the same issue and after troubleshooting came to the conclusion that the issue was caused by file formats not returning properly and therefore sending a broken link.

For example, an image url would return “img-jpg” instead of “.jpg”.

I have tested this on a completely fresh install of wordpress to make sure that it wasn’t caused by another plugin or custom functions but had the same result.

I was do more tests and re-install the last version again.

first, I didn’t have style/look-feel issues.

second, I’m using Cloudinary only sync – and some pictures on my site were not loaded and some yes.
in the last version (277) no issues at all.

I’m not sure why the old version working and the new version is not.
its looks like the theme not found the pictures good with the new version.

Hi @spidiman, @sprdjors

It seems you have different issues, in order to investigate could you please open a ticket to support@cloudinary.com with the information already asked in my previous image?

Thanks in advance.
Best,
Loic

I will try to send it soon –
also, I have those logs (more than 1GB!):

Table ‘ggg.wp_cloudinary_relationships’ doesn’t exist SHOW FULL COLUMNS FROM wp_cloudinary_relationships require(‘wp-blog-header.php’), wp, WP->main, WP->parse_request, do_action_ref_array(‘parse_request’), WP_Hook->do_action, WP_Hook->apply_filters, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, WP_REST_Server->respond_to_request, Cloudinary\Sync\Push_Sync->process_queue, Cloudinary\Sync\Push_Sync->process_assets, Cloudinary\Sync->get_sync_type, Cloudinary\Sync->validate_sync_type, Cloudinary\Sync->run_sync_method, call_user_func, Cloudinary\Delivery->update_relation, Cloudinary\Delivery::update_size_relations_public_id`

I am seeing the same issue that is noted by spidiman above. I will send an email to the address listed above with more details.

Loic from Cloudinary helps me! in your database are not a table like wp_cloudinary_relationships. so add it! try this and it works without problems. make a database backup safety first before make a sql statement. thanks loic!

CREATE TABLE IF NOT EXISTS wp_cloudinary_relationships (
id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
post_id bigint(20) DEFAULT NULL,
public_id varchar(500) DEFAULT NULL,
parent_path varchar(500) DEFAULT NULL,
sized_url varchar(500) DEFAULT NULL,
width int(11) DEFAULT NULL,
height int(11) DEFAULT NULL,
format varchar(12) DEFAULT NULL,
sync_type varchar(10) DEFAULT NULL,
post_state varchar(12) DEFAULT NULL,
transformations text DEFAULT NULL,
signature varchar(5) DEFAULT NULL,
PRIMARY KEY (id),
UNIQUE KEY sized_url (sized_url(190)),
KEY post_id (post_id),
KEY parent_path (parent_path(190)),
KEY public_id (public_id(190)),
KEY sync_type (sync_type)
) ENGINE=INNODB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

• This reply was modified 3 years, 2 months ago by skome.

Hi @skome,

To be more general, the error occurs due to limitation of the DB engine which depends on your MySQL version.

Here is the code to use for any MySQL version:

CREATE TABLE IF NOT EXISTS {{wp_prefix}}_cloudinary_relationships (
    id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
    post_id bigint(20) DEFAULT NULL,
    public_id varchar(500) DEFAULT NULL,
    parent_path varchar(500) DEFAULT NULL,
    sized_url varchar(500) DEFAULT NULL,
    width int(11) DEFAULT NULL,
    height int(11) DEFAULT NULL,
    format varchar(12) DEFAULT NULL,
    sync_type varchar(10) DEFAULT NULL,
    post_state varchar(12) DEFAULT NULL,
    transformations text DEFAULT NULL,
    signature varchar(5) DEFAULT NULL,
    PRIMARY KEY (id),
    UNIQUE KEY sized_url (sized_url(190)),
    KEY post_id (post_id),
    KEY parent_path (parent_path(190)),
    KEY public_id (public_id(190)),
    KEY sync_type (sync_type)
) ENGINE=INNODB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

You will need to replace the {{wp_prefix}} with the prefix in your database, by default it is wp but it can change depending on your setup. So before running the query, I recommend checking your prefix and then filling the value in the query above.

Best,
Loic

• This reply was modified 3 years, 2 months ago by loic @ cloudinary.

thank you all,

its looks that it is solved the problem.
now I have another issue that some pictures are not loaded – BUT I think it’s related to the theme plugins.

I will check and update

update –

the address of the pictures that are not loaded is not Cloudinary – the links address is:
wp-content/uploads/2021/11/picture.jpg

(I’m using Cloudinary sync only)

when I’m back to the old version it’s working for me but in version 300 its looks that a few plugins try to get the picture from the WordPress content folder and not from Cloudinary address server.

Hi @spidiman,

Thanks for your update.

Do you mind creating a ticket to support@cloudinary.com with the information asked in my first reply?

Thanks in advance.
Best,
Loic

Hi there,

I am closing this ticket as those issues are fixed in 3.0.1.

Feel free to reach out to support@cloudinary.com if you encounter new issues.

Best,
Loic