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

  • Resolved vipz1

    (@vipz1)


    7 years, 1 month ago

    i have installed the SNAP plugin but cannot get it to activate.

    i keep getting the following error:

    Fatal error: Cannot redeclare class NXS_HtmlFixer in /home/*/public_html/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc/nxs_functions.php on line 209

    Environment Stats:
    SNAP Version: 4.1.1
    WP Version: 4.9.2
    PHP Version: 5.6.33
    MySQL Version: 5.6.38

    I have read another thread that warned of potential issues with PHP, this was downplayed as simply being false positives.

    Well, I assure you that this error is NOT a “false positive”, if screenshot proof is wanted i can absolutely provide it!

    I hope we can find solution to the problem.

    thank you!

    • This topic was modified 7 years, 1 month ago by vipz1.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter vipz1

    (@vipz1)

    now tested with SNAP Version: 4.1.2

    same problem, cannot be activated.

    Plugin Author NextScripts

    (@nextscripts)

    Well. SNAP declares class ‘NXS_HtmlFixer’ only once.

    This error

    Fatal error: Cannot redeclare class NXS_HtmlFixer

    means that you either have another installed and activated instance of SNAP in some other folder or you you have some other plugin that is using code stolen from us. In either cases please disable and remove another plugin.

    You can see which one in the “previously declared” section of this error.

    Thread Starter vipz1

    (@vipz1)

    AWESOME!!!!

    I discovered the plugin that is causing the problem.

    How can i contact you so i can give you the information so you can protect your code?

    Plugin Author NextScripts

    (@nextscripts)

    Please send this info to [email protected] or just fill contact us from here: https://www.nextscripts.com/contact-us/

    Thank you.

    Thread Starter vipz1

    (@vipz1)

    Fantastic!

    I will get straight onto it. ??

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