Fatal Error on update via Jenkis build

  • Resolved Dino

    (@dinoelav)


    4 years, 3 months ago

    Hello, after updating Yoast version 13.3 to latest (14.6.1) I’m getting this error:

    PHP Fatal error:  Uncaught Error: Class 'Yoast\WP\SEO\WordPress\Wrapper' not found in /var/www/html/wp-content/plugins/wordpress-seo/src/generated/container.php:419
Stack trace:
#0 /var/www/html/wp-content/plugins/wordpress-seo/src/generated/container.php(1534): Yoast\WP\SEO\Generated\Cached_Container->getWPSEOAdminAssetManagerService()
#1 /var/www/html/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php(271): Yoast\WP\SEO\Generated\Cached_Container->getStructuredDataBlocksService()
#2 /var/www/html/wp-content/plugins/wordpress-seo/src/loader.php(206): YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container->get('Yoast\\WP\\SEO\\In...')
#3 /var/www/html/wordpress/wp-includes/class-wp-hook.php(287): Yoast\WP\SEO\Loader->load_integrations('')
#4 /var/www/html/wordpress/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
#5 /var/www/html/wordpress/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#6 /var/www/html/wordpress/wp-settings.php(540): do_action('in in /var/www/html/wp-content/plugins/wordpress-seo/src/generated/container.php on line 419

    We use Jenkins job to build and deploy our application via git pipeline. We tested the compatibility by manually updating the plugin (thread link) via admin interface and it works just fine. We also tested cleaning the cache from Cloudflare and W3TC (Total Cache). So the problem seems to occur during the build process.

    Wordpress version: 5.4.2
    PHP version: 7.2.21

    I need some help to get this update done using Jenkins service please.

    Thanks in advance.

    Dino

Viewing 8 replies - 1 through 8 (of 8 total)

  • Hi @dinoelav,

    Thanks for the details about the problem. The “class not found” errors are usually related to missing or corrupted files, so thank you for confirming that updating manually fixes the problem.

    We haven’t heard any reports about Jenkins, but we’ve had some similar reports of this error updating with Composer that seem to be related to the plugin maintaining compatibility with PHP 5.6.

    Although we don’t offer support for custom edits to the plugin, you can find out more about the issue and a possible solution in this user’s pull request: https://github.com/Yoast/wordpress-seo/pull/14921.

    Thread Starter Dino

    (@dinoelav)

    Thanks for your answer @priscillamc

    We compared the plugin files (diff) after the build process with the files from the manual update, there were no differences between them, so we assumed the files were ok.

    Is there any process that happens during the update via admin interface that could impact this?

    Once again, thanks in advance!

    Plugin Support Rumejan Barbarona

    (@onlyincebu)

    Hello Dino!

    This typically occurs when the update (or installation) couldn’t complete correctly probably due to server interruption or server hiccups during the process. Uninstalling the reinstalling the plugin usually fixes this issue.

    Thread Starter Dino

    (@dinoelav)

    Thanks for your reply @onlyincebu

    Since we update via build process using Jenkis, we download the plugin directly from Yoast and extract it locally on our repository. We made several validations (diff and md5 hash comparing downloaded latest version), and the plugin used in the build process of our application wasn’t corrupted.

    Untill the version 13.3 we didn’t experience any problems with our deploys via Jenkis.

    Just to make sure: Is there any process that happens when you install the plugin via admin?

    Plugin Support devnihil

    (@devnihil)

    @dinoelav Installing the plugin via admin is going to check for whether the plugin already exists during the extraction process of the .zip file. Do you mean specifically for the update?

    Also, you can monitor some of this using the query monitor plugin if you are looking for additional processes: https://www.ads-software.com/plugins/query-monitor/

    Thread Starter Dino

    (@dinoelav)

    @devnihil Thanks for your reply. Yes, I mean specifically for the update. We test it on a development server before going to production. We have the Yoast version 13.3 running in production today.

    Here is an overview of our process for updating the plugin:

    1 – Download latest version of Yoast
    2 – Remove yoast plugin directory in our repository
    3 – Copy/ Extract the updated-yoast-plugin.zip inside plugins directory
    4 – Stage and commit the updated-yoast-plugin
    5 – Build Dev (dev branch) to test in development environment
    6 – Merge dev-> master (if dev was successful)
    7 – Build production

    Our process stops at the stage 5.When we update via admin, it goes well, that’s is why I asked about any process during update made via admin interface.

    Thanks in advance!

    Plugin Support Jerlyn

    (@jerparx)

    Hi @dinoelav ,

    We are not aware of any other processes involved during the plugin update apart from what Carl mentioned. Can you please confirm if you are experiencing the same issue with Yoast SEO 14.7?

    Also, after removing the plugin folder from the directory (step 2), have you tried clearing the cache first before extracting the new plugin files to the server?

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Fatal Error on update via Jenkis build’ is closed to new replies.