Plugin could not be activated because it triggered a fatal error

  • Resolved Luke Cavanagh

    (@lukecavanagh)


    7 years, 8 months ago

    Currently running into this fatal error on plugin activation

    Fatal error: Uncaught Error: Class 'Fastdev\WpMimesPage' not found in /srv/www/wordpress-trunk/wp-content/plugins/fastdev/plugin-base.php:165 Stack trace: #0 /srv/www/wordpress-trunk/wp-admin/includes/plugin.php(1882): include() #1 /srv/www/wordpress-trunk/wp-admin/plugins.php(164): plugin_sandbox_scrape('fastdev/plugin-...') #2 {main} thrown in /srv/www/wordpress-trunk/wp-content/plugins/fastdev/plugin-base.php on line 165

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Andrei Surdu

    (@_smartik_)

    Hi.
    Thank you very much for report. The error was caused because file names are case sensitive in Linux but not in Windows. It’s great that you reported it so fast. I appreciate it.

    It’s fixed now in version 1.2.3.

    Best regards.

    Thread Starter Luke Cavanagh

    (@lukecavanagh)

    (@_smartik_

    Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error’ is closed to new replies.