Plugin could not be activated because it triggered a fatal error.

  • Resolved latinoleader

    (@latinoleader)


    11 years, 10 months ago

    Has anyone else encountered this:

    Fatal error: Cannot redeclare filter_plugin_actions() (previously declared in /home/content/19/7561419/html/latinoleader/wp-content/plugins/nextgen-public-uploader/nextgen-public-uploader.php:90) in /home/content/19/7561419/html/latinoleader/wp-content/plugins/collabpress/includes/cp-core.php on line 43

    Is the solution as simple as deactivating the NextGen Public Uploader? Or is there something else at play, here?

    https://www.ads-software.com/extend/plugins/collabpress/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Eric Andrew Lewis

    (@ericlewis)

    I’ve fixed this in the trunk version running on the GitHub repository. if you’d like a hotfix, use the version there. It will be released in the next version to go to www.ads-software.com which should be in the next few weeks, thanks for the bug report.

    Thread Starter latinoleader

    (@latinoleader)

    Thanks for the prompt reply!

    Due to a lack of experience, can you explain how I should go about implementing the “hotfix?”

    Should I delete the plugin I downloaded from the WP repository and then upload everything in the GitHub repository to the plugins directory?

    Or… do I only need to replace the files in my plugins directory w/the files in the GitHub rep. that show that were modified “21 hours ago?”

    Thanks, again!

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.