• Resolved kaotik

    (@kaotik)


    I’ve got multiple sites down because of conflicts that result to other plugins using “ClassLoader.php” and running version 7.1.15 and same conflict persists. Please fix asap!

    • This topic was modified 6 years, 1 month ago by kaotik.
Viewing 11 replies - 16 through 26 (of 26 total)
  • I replied to another thread but I’m experiencing problems even with 7.1.15. The admin panel looks weird and is slow to respond. FYI.

    Somewhat similar issues here for my website, https://bodyshepherd.com/ but the error is “Too many redirects.”

    Hi @jbmaca and @brandshepherd,
    These do not sound like the same issues. The previous posters in this thread were having error messages from ClassLoader.php and upgrading to 7.1.15 seems to have resolved that.

    Please start your own threads here in the forum and describe in as much detail as you can what the current problem is and what you have tested so far (deactivated Wordfence etc).

    Thanks!

    Actually, it was caused by the same thing in 7.1.14. From my dev team:

    We found the problem. Wordfence 1.14 update caused the 500 error.

    Then it created a redirect that basically created a redirect-loop in the htaccess file. We have removed the code in the htaccess file.

    Site is back up and running

    So it sounds like 7.1.14 had all kinds of problems!

    Hi @brandshepherd,

    This thread is about error messages from ClassLoader.php. We haven’t had any other reports of redirect-loops as far as I’m aware. If you can get your dev team to explain a bit more how the redirect-loop was happening and post that in your own thread, we’ll be happy to have a look as soon as we can.

    Thanks!

    I just discovered a similar issue with my site cdspvideo.com. It hadn’t been reported to me, and it’s not a particularly active site, so I don’t know how long it’s been going on.

    I see the topic says it’s resolved, but what is the resolution?

    Here’s the error I get when I try to visit the site as a user. (I get a similar message when I try to reach the login screen.)

    Fatal error: Cannot redeclare Composer\Autoload\includeFile() (previously declared in /data/50/5/89/78/5089730/user/6121027/htdocs/wordpress/wp-content/plugins/s2member/src/vendor/composer/ClassLoader.php:410) in /data/50/5/89/78/5089730/user/6121027/htdocs/wordpress/wp-content/plugins/wordfence/vendor/composer/ClassLoader.php on line 445

    Hi @mvhplank,
    The issue was in 7.1.14 and the fix is to upgrade Wordfence to 7.1.15.

    Thanks much! Do I do it via FTP? The site is currently inoperable.

    Hi!
    Yes, to get the site back up, delete the “wordfence” folder in wp-content (using FTP or any file manager your web host provides will work). Then you can reinstall Wordfence from the “Plugins” page in WordPress admin.

    My fatal error message is locking me out of both my main site & my administrative site making it impossible for me to delete classloader or wordfence, install any newer versions or adjustments – to install ANYTHING. How do I get rid of the paralyzing message & re-gain access to my administrative panel?

    ?Fatal error: Cannot redeclare Composer\Autoload\includeFile() (previously declared in /home/uuessay/public_html/wp-content/plugins/php-compatibility-checker/vendor/composer/ClassLoader.php:442) in /home/uuessay/public_html/wp-content/plugins/wordfence/vendor/composer/ClassLoader.php on line 445?

    Hi @maxmulf,
    You need to delete the “wordfence” folder located in wp-content/plugins via FTP or any file browser you have via your web host. Then you can install Wordfence again. It will then be version 7.1.15 which does not have the above issue.

Viewing 11 replies - 16 through 26 (of 26 total)
  • The topic ‘Major conflicts via last update’ is closed to new replies.