I want to create a video from the images in my FTP.

Atanu
Atanu Member Posts: 2
edited November 6 in Developer APIs

I am using php and wordpress. I have created a custom plugin for this. I can access the class now by changing the name of the namespace from Cloudinary to Cloudinarysdk. But I am getting error now on the class name as ClassUtils.

Fatal error: Uncaught Error: Class "Cloudinarysdk\ClassUtils" not found in /home/httpd/vhosts/air-production.ch/new.air-labs.ch/wp-content/plugins/timelapse/lib/cloudinarysdk/src/Configuration/BaseConfigSection.php:208 Stack trace: #0 /home/httpd/vhosts/air-production.ch/new.air-labs.ch/wp-content/plugins/timelapse/lib/cloudinarysdk/src/Configuration/BaseConfigSection.php(156):

Tagged:

Comments

  • Vdeub
    Vdeub Member, Cloudinary Staff Posts: 78

    Hi @Atanu,

    You already have a ticket with us so there is no point in creating other tickets using other threads like github or this forum.

    Please share everything in your current ticket with us.

    Regards,

    Loic

  • Atanu
    Atanu Member Posts: 2

    Thanks for the information Loic I will share over there.

  • OllyBe
    OllyBe Member Posts: 3
    edited November 8

    The error indicates that WordPress is unable to locate the ClassUtils class under the Cloudinarysdk namespace. Here are a few troubleshooting steps:

    1. Confirm Namespace Consistency: Make sure that all occurrences of Cloudinary in the original code are changed to Cloudinarysdk, not only in BaseConfigSection.php but also in any file that references ClassUtils or BaseConfigSection.
    2. Autoloading: Ensure that the autoloader is configured to include the new namespace (Cloudinarysdk). Check your plugin's composer.json (if using Composer) or the autoload file to verify that it’s mapping Cloudinarysdk correctly.
    3. Class Location: Verify that the ClassUtils file is located in the expected path within your project, under the correct namespace. If it's missing or misnamed, you’ll need to adjust it accordingly.
    4. Check File Permissions: Make sure that WordPress has read access to the files in your custom plugin directory, as restricted permissions can sometimes cause issues.