Critical Error with 3.1

  • Resolved ethanb40

    (@ethanb40)


    1 year ago

    We have 2 sites that utilize this plugin. On both, updating from 3.0 to 3.1 causes a critical error. Please advise.

    PHP Warning: require(/…/public_html/wp-content/plugins/user-meta/vendor/autoload.php): failed to open stream: No such file or directory in /…/public_html/wp-content/plugins/user-meta/user-meta.php on line 30

PHP Fatal error: require(): Failed opening required '/…/public_html/wp-content/plugins/user-meta/vendor/autoload.php' (include_path='.:/usr/share/php') in /…/public_html/wp-content/plugins/user-meta/user-meta.php on line 30
Viewing 9 replies - 1 through 9 (of 9 total)
  • Jan Radosta

    (@bramatton)

    @ethanb40 We have exactly the same issue, I hope it’ll be resolved soon.

    clem90

    (@clem90)

    The same for me ??

    Une erreur de type E_COMPILE_ERROR a été causée dans la ligne 30 du fichier /home/aljm/membre.apprendre-le-jazz-manouche.com/wp-content/plugins/user-meta/user-meta.php. Message d’erreur?: require(): Failed opening required ‘/home/aljm/membre.apprendre-le-jazz-manouche.com/wp-content/plugins/user-meta/vendor/autoload.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’)

    darkstar123456

    (@darkstar123456)

    Same here…
    They forgot to include the composer librairies in the revision ??

    Fortunately, they didnt fortgot about the composer.json

    Quick fix if you can’t wait for the next update and have a SSH access with Composer, go into the install directory (wp-content/plugins/user-meta/) and install with the following command : composer install

    If you don’t have Composer installed and/or you don’t have SSH Access, I made a .ZIP Archive with the files I installed : https://greenpig.be/user-meta.3.1-vendor.zip
    Extract the files and upload them in the wp-content/plugins/user-meta/ directory

    (I will remove this link when update is available for the plugin)

    • This reply was modified 1 year ago by darkstar123456. Reason: Download link was incorrect
    rennevat

    (@rennevat)

    Thank you darkstar123456! Installing the vendor .zip package resolved our issue.

    clem90

    (@clem90)

    @darkstar123456 Thanks ??

    lordmatt

    (@lordmatt)

    Had to uninstall as this update crached my site.

    RichHelms

    (@richhelms)

    darkstar123456

    My site is on GoDaddy and will not let an unauthorized plugin upload into the site. I hope a proper update is available. I reinstalled 3.0 and set to not auto update but GoDaddy updates anyway.

    Thread Starter ethanb40

    (@ethanb40)

    The developer appears to have updated the plugin but left the version number at 3.1. Confirmed updated and working on both our sites now.

    I wish you had updated the 3.1 version info or called it 3.2. I have waited for 5 days for nothing looking for a 3.2 with the fix.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Critical Error with 3.1’ is closed to new replies.