E_ERROR after Version 1.0

  • Resolved leogc

    (@leogc)


    5 years, 5 months ago

    Hi there after installation of Version 1.0 my WP Page was detroyed and luckylie i have Version 5.2 which offer a recovery mode, so i am able to check the problem:

    This is what WP says: E_ERROR in Line 15 of file /var/www/vhosts/XXXX/XXX/wp-content/plugins/posterno/vendor/posterno/import-export/component-loader.php

    Uncaught Error: Class ‘PosternoImportExport\Export\Admin’ not found in /var/www/vhosts/XXXX/XXX/wp-content/plugins/posterno/vendor/posterno/import-export/component-loader.php:15 Stack trace: #0 /var/www/vhosts/XXXX/XXX/wp-content/plugins/posterno/vendor/composer/autoload_real.php(66): require() #1 /var/www/vhosts/XXXX/XXX/wp-content/plugins/posterno/vendor/composer/autoload_real.php(56): composerRequire7f3b1a8783d8c28bf70361802884922d(‘e5c69fdc6826b81…’, ‘/var/www/vhosts…’) #2 /var/www/vhosts/XXXX/XXX/wp-content/plugins/posterno/vendor/autoload.php(7): ComposerAutoloaderInit7f3b1a8783d8c28bf70361802884922d::getLoader() #3 /var/www/vhosts/XXXX/XXX/wp-content/plugins/posterno/includes/class-posterno.php(271): require(‘/var/www/vhosts…’) #4 /var/www/vhosts/XXXX/xxx

    so i have deactivated the Plug In, and this helps for the moment. You sould quick investigate this ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Alessandro Tesoro

    (@alessandrotesoro)

    Hi @leogc

    Apologies about the issue, I’ve received another report from another user too but I still haven’t been able to replicate the issue on my end.

    I really want to fix this, could you please send me an email to [email protected] with a temp admin/ftp account so I can see what’s happening?

    Please let me know so I can fix this asap.

    Thread Starter leogc

    (@leogc)

    As we are in testmde the website is not available to reach from outside, so unfortuneately i can not send you any log in details in the moment.

    With the full Error Code i posted here, you should and will find the prblem i think ??

    Plugin Author Alessandro Tesoro

    (@alessandrotesoro)

    Hi @leogc

    Unfortunately the stack trace is useless in this case, it’s basically saying that a class is missing but that’s not true because the class should have been loaded dynamically in by composer. Even though I’ve tested it multiple times on my end I still can’t replicate it hence why I’d need access to the site to see what’s happening on your end.

    Thread Starter leogc

    (@leogc)

    As said we are unable to give away any log in in the moment, besides that, FTP is something we would never give away, sorry. And in Admin i have given you all what is showing to me, so we will see if the error will be still there after the next update.

    You can tell me what you like to see and i create screenshots if that helps.

    Plugin Author Alessandro Tesoro

    (@alessandrotesoro)

    Hi @leogc

    I really appreciate your help, unfortunately I’m shooting in the dark here, could you please download this slighly modified version of the plugin https://www.dropbox.com/s/dmurw7lqly7g6lp/posterno.zip?dl=0, unzip it and replace the existing folder into your site to see if that helps?

    Unfortunately ftp would have been the only way because I’d need direct access to the file of the new import/export functionality to see how the composer autoloader is loading but no worries I understand if you don’t want to mail me the ftp details, that’s absolutely fine.

    Plugin Author Alessandro Tesoro

    (@alessandrotesoro)

    Hey @leogc

    I’ve identified the issue, it’s an incongruency with folder names and how web servers read folder names. My local server uses a non case-sensitive system while web server use case-sensitive systems.

    Once again apologies about the issue, I’m releasing a fix shortly in v1.0.1

    Thread Starter leogc

    (@leogc)

    Ah ok, so i don’t need to try it with the dropbox file, so i wait till the release ??

    Thread Starter leogc

    (@leogc)

    Ok it works again! Thank you!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘E_ERROR after Version 1.0’ is closed to new replies.