Support » Plugin: hCaptcha for WordPress » 1.8.0 Update has Fatal autoload.php error

  • Resolved KZeni

    (@kzeni)


    I have multiple sites using this plugin and 1.8.0 update now has them all reporting a site-wide fatal PHP error!

    Here’s the specific error:

    
    Warning: require_once(/wp-content/plugins/hcaptcha-for-forms-and-more/vendor/autoload.php): failed to open stream: No such file or directory in /wp-content/plugins/hcaptcha-for-forms-and-more/hcaptcha.php on line 50
    
    Fatal error: require_once(): Failed opening required '/wp-content/plugins/hcaptcha-for-forms-and-more/vendor/autoload.php' (include_path='.:/usr/share/pear7:/usr/share/php') in /wp-content/plugins/hcaptcha-for-forms-and-more/hcaptcha.php on line 50
    

    It’s happening on multiple sites so it doesn’t seem like a hiccup or anything.

    Please roll back this update or put out a hotfix where 1.8.1 is the previously working version so as few sites as possible update/auto-update to this version that appears to break the whole site when active.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter KZeni

    (@kzeni)

    I can confirm that require_once HCAPTCHA_PATH . '/vendor/autoload.php'; is on line 50 of the plugin’s main hcaptcha.php file, and that the file trying to be referenced doesn’t exist. Heck, the whole vendor folder appears to be missing!

    So this version, as it is now, does indeed have a matter-of-fact fatal error that should be affecting everyone (site-wide) per something going wrong during this version release, or something (not sure how exactly files could be left missing like this to then be distributed to thousands of sites.)

    Thread Starter KZeni

    (@kzeni)

    As an aside, the 1.7.0 version doesn’t appear to have been tagged (https://plugins.svn.wordpress.org/hcaptcha-for-forms-and-more/tags/) so it’s not showing in the version dropdown for downloading past versions at https://wordpress.org/plugins/hcaptcha-for-forms-and-more/advanced/ so one needs to roll back to 1.6.4 as the latest available version on WP.org without this fatal issue, currently.

    Thread Starter KZeni

    (@kzeni)

    I checked version 1.6.4, and it doesn’t have any vendor folder, and the hcaptcha.php file doesn’t have any reference to an autoload.php file.

    The changelog didn’t really point to something like autoload.php being included or anything (the biggest thing was CI being added in 1.7.0 which is actuall ironic since this is the type of thing CI should prevent, right…?)

    As such, I just commented out that one line in hcaptcha.php where it references autoload.php, and the site went back to working! There might be more to the fix than that, but at least the site’s not completely down anymore.

    Thread Starter KZeni

    (@kzeni)

    Okay, it appears version 1.6.5 has been released as the hotfix for the moment (albeit with the changelog in the readme being malformed… though it is tagged properly https://plugins.svn.wordpress.org/hcaptcha-for-forms-and-more/tags/ [might need to clean up that 1.8.0 version tag that’s still hanging around.])

    I can confirm that the version 1.6.5 hotfix works (with 1.7.0 and 1.8.0 being unpublished so this lower version number can be offered [with, again, the 1.8.0 tag needing to be cleaned up yet.])

    That said, those on 1.7.0 and 1.8.0 already won’t get the 1.6.5 update unless removed & re-installed / rolled back manually per the version being seen as older even though it’s the newest one (using 1.8.1 for this hotfix would’ve avoided that behavior.)

    Thread Starter KZeni

    (@kzeni)

    Hopefully, the next version can have the latest updates, avoid this issue, and has a version number that’s higher than 1.8.0 so those on 1.7.0 and 1.8.0 have their setup actually offer the latest version rather than being left behind until that higher version number comes around.

    Plugin Author hcaptcha

    (@hcaptcha)

    Hi @kzeni , sorry about this: we pushed 1.6.5 within a few minutes after realizing the issue, and 1.8.1 a few minutes after that. Should be resolved now.

    Humorously enough, this issue was a side effect of a large effort in 1.8.x to add 100% test coverage, and integration tests on all plugins.

    Thread Starter KZeni

    (@kzeni)

    Yeah, I wondered if that was the case, heh.

    I appreciate the update & seeing things as working properly now!

    Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.