Fatal error: Cannot declare class ComposerAutoloaderInit

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Can you try restarting the PHP process to clear the opcode cache? That’s about the only common issue between the small handful of reports of this that I’ve seen.

    Thread Starter Jaro

    (@pixtweaks)

    I tried to purge OPcache, change PHP version, no change, still it’s throwing the same error. Any other suggestion?

    JTweb

    (@evgeniypkt)

    Greetings!

    I have the same problem. Nothing helps. Activation of the plugin generates a fatal error with any settings. How can I fix it?

    ——-
    Приветствую!

    У меня такая же проблема. Ничего не помогает. Активация плагина выдаёт фатальную ошибку при любых настройках. Как это починить?

    Thread Starter Jaro

    (@pixtweaks)

    @evgeniypkt and @johnbillion
    I’ve found it! db.php wasn’t a file, it was a link that through my hosting’s file manager wasn’t visible. Once I connected via FTP I saw it and deleted it. After that, the plugin activates fine.

    JTweb

    (@evgeniypkt)

    Here’s what I got after deleting the db.php link and activation of the Query Monitor plugin (((

    Fatal error: Cannot declare class ComposerAutoloaderInit9bc748a33ab984c092a749a74d7b8261, because the name is already in use in?/var/www/…/data/www/…/data/plugins/query-monitor/vendor/composer/autoload_real.php?on line?5

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal error: Cannot declare class ComposerAutoloaderInit’ is closed to new replies.