Cloudinary v2.0.3: Call to a member function cloudinary_url() on null

The result and severity of this error is that unless this plugin is disabled the site is non-functional!

Can you please open a support ticket? I would like to take a look at your staging environment.
At this point, I’m speculating there could be something that’s conflicting with another plugin or theme.

Hello @erwincloudinary

I made an attempt to copy my client website to my local environnement (Windows with Xampp, production server is php 7.3 while dev environnement is 7.4.3 ) and I got a similar error, see below. I will open a ticket.

Notice: Undefined index: connect in C:\xampp\htdocs\bidules\wp-content\plugins\cloudinary_wordpress_v2\php\class-connect.php on line 316

Fatal error: Uncaught Error: Call to a member function cloudinary_url() on null in C:\xampp\htdocs\bidules\wp-content\plugins\cloudinary_wordpress_v2\php\class-media.php:1208 Stack trace: #0 C:\xampp\htdocs\bidules\wp-content\plugins\cloudinary_wordpress_v2\php\class-plugin.php(277): Cloudinary\Media->setup() #1 [internal function]: Cloudinary\Plugin->Cloudinary\{closure}(Object(Cloudinary\Media)) #2 C:\xampp\htdocs\bidules\wp-content\plugins\cloudinary_wordpress_v2\php\class-plugin.php(271): array_map(Object(Closure), Array) #3 C:\xampp\htdocs\bidules\wp-includes\class-wp-hook.php(288): Cloudinary\Plugin->setup('') #4 C:\xampp\htdocs\bidules\wp-includes\class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array) #5 C:\xampp\htdocs\bidules\wp-includes\plugin.php(478): WP_Hook->do_action(Array) #6 C:\xampp\htdocs\bidules\wp-settings.php(523): do_action('init') #7 C:\xampp\htdocs\bidules\wp-config.php(159): require_once('C:\\xampp\\htdocs...') #8 C:\xampp\htdocs\bidules\wp-load.php(37): require_once('C:\\xampp\\htdocs...') in C:\xampp\htdocs\bidules\wp-content\plugins\cloudinary_wordpress_v2\php\class-media.php on line 1208

• This reply was modified 4 years, 7 months ago by leiho.

Hi @leiho ,

Thanks for opening a ticket, I will follow-up with you on that ticket.

Regards,
Erwin Lukas

Issue solved by updating the Cloudinary plugin, I was using version 2.0.0.beta and missed the 2.0.3 update that fixed the migration issue.

Thank you all, @www404 you may have a try if you’re using a lower version

I can confirm that we are unfortunately still having an issue with version 2.0.3.

@www404, can you please share what issue that you are having?
Please open a support ticket from our support portal with the details

The issue is as mentioned at the top of this support page and a ticket has already been created. I’m awaiting an updated solution. Thanks

@www404, my apologies, yes, this is confirmed a bug that we are working on the fix.