Support » Plugin: Shield Security: Protection with Smarter Automation » Plugin could not be activated because it triggered a fatal error.

  • Resolved jeparamedia

    (@jeparamedia)


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

    Warning: require_once(/home/jeparam1/public_html/insurancelegacy.com/wp-content/plugins/wp-simple-firewall/src/features/firewall.php): failed to open stream: No such file or directory in /home/jeparam1/public_html/insurancelegacy.com/wp-content/plugins/wp-simple-firewall/icwp-plugin-controller.php on line 1491

    Fatal error: require_once(): Failed opening required ‘/home/jeparam1/public_html/insurancelegacy.com/wp-content/plugins/wp-simple-firewall/src/features/firewall.php’ (include_path=’.:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php’) in /home/jeparam1/public_html/insurancelegacy.com/wp-content/plugins/wp-simple-firewall/icwp-plugin-controller.php on line 1491

    i can’t activated, i try many time but not lucky. maybe my hosting not compatible?
    my site: http://insurancelegacy.com/
    thank Paul G and everyone

    https://wordpress.org/plugins/wp-simple-firewall/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Paul

    (@paultgoodchild)

    Can you please try deleting all the file and reinstalling the plugin?

    The plugin has all these files in there, but sometimes WordPress errors and a file doesn’t get written correctly. Shy exactly this is, I don’t know. But try installing fresh again

    i try but not work. i try to delete bulletproof and activate shield but same error. I use shield on all my web on another hosting and working well.

    in this chase maybe my hosting not compatible. ^_^
    thanks for your plugin and ur kind reply.

    Plugin Author Paul

    (@paultgoodchild)

    If you’ve reinstalled, could you look and see if the file actually exists on your web hosting? I can’t think why it wont install the file… have you tried manually uploading the files?

    i will try and go back here 🙂 thanks for your help Paul.

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