WordPress.org

Ready to get started?Download WordPress

Forums

Ultimate Security Checker
[resolved] Plugin could not be activated because it triggered a fatal error (14 posts)

  1. juggledad
    Member
    Posted 3 years ago #

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

    Parse error: syntax error, unexpected $end in /Users/Paul/Sites/wp301/wp-content/plugins/ultimate-security-checker/wp-ultimate-security.php on line 161

  2. bsndev
    Member
    Plugin Author

    Posted 3 years ago #

    I updated the code, should work now.. not sure why it doesn't work for you though. I tested on all blogs i had - it activated successfully. So if it's still broken for you - tell me more about your PHP & OS where do you run this script.

  3. juggledad
    Member
    Posted 3 years ago #

    mac os 10.5.9
    php 5.2.9

    every other plugin I use works fine - there is a blank line in the plugin after the closing ?>

  4. bseidner
    Member
    Posted 3 years ago #

    I have the same issue. Just downloaded and tried to install it on 1-20-11 5:20pm CST
    Server is Windows server 2003 with IIS 6
    PHP version 5.3.5

  5. bsndev
    Member
    Plugin Author

    Posted 3 years ago #

    please update 2.1.5 and let me know if it works

  6. nzde
    Member
    Posted 3 years ago #

    Hi - The plugin works but your site, to which apparently users can go to for help with security risks, is down/has been compromised...

  7. bseidner
    Member
    Posted 3 years ago #

    I still get the error message with new plugin version. Does it matter if I am using multisite feature of WordPress?

  8. juggledad
    Member
    Posted 3 years ago #

    version 2.1.5

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

    Parse error: syntax error, unexpected $end in /Users/Paul/Sites/wp301/wp-content/plugins/ultimate-security-checker/wp-ultimate-security.php on line 160

  9. bsndev
    Member
    Plugin Author

    Posted 3 years ago #

    check please it shoudl be fixed in 2.1.7

  10. juggledad
    Member
    Posted 3 years ago #

    Try again, I still get

    Plugin could not be activated because it triggered a fatal error.
    Parse error: syntax error, unexpected $end in /Users/Paul/Sites/wp301/wp-content/plugins/ultimate-security-checker/wp-ultimate-security.php on line 183

    and I see in my console log

    Wednesday, March 2, 2011 11:58:59 AM US/Eastern
    [Wed Mar 02 11:59:04 2011] [error] [client 192.168.48.99] PHP Parse error: syntax error, unexpected $end in /Users/Paul/Sites/wp301/wp-content/plugins/ultimate-security-checker/wp-ultimate-security.php on line 183, referer: http://192.168.48.99/~paul/wp301/wp-admin/plugins.php
    [Wed Mar 02 11:59:08 2011] [error] [client 192.168.48.99] PHP Parse error: syntax error, unexpected $end in /Users/Paul/Sites/wp301/wp-content/plugins/ultimate-security-checker/wp-ultimate-security.php on line 183, referer: http://192.168.48.99/~paul/wp301/wp-admin/plugins.php?error=true&plugin=ultimate-security-checker%2Fwp-ultimate-security.php&_error_nonce=c82a568adf
    [Wed Mar 02 11:59:08 2011] [error] [client 192.168.48.99] PHP Parse error: syntax error, unexpected $end in /Users/Paul/Sites/wp301/wp-content/plugins/ultimate-security-checker/wp-ultimate-security.php on line 183, referer: http://192.168.48.99/~paul/wp301/wp-admin/plugins.php?error=true&plugin=ultimate-security-checker%2Fwp-ultimate-security.php&_error_nonce=c82a568adf

  11. bsndev
    Member
    Plugin Author

    Posted 3 years ago #

    Hey,

    thanks for an update. Try out the 2.1.8, should be fixed there

  12. juggledad
    Member
    Posted 3 years ago #

    Well congratulations it finally activates...but you have to be kidding me, I have to put up with you jumping out to twitter and then all you say is

    Your blog gets 35 of 100 security points.
    Some medium sized security holes have been found in your blog.
    If you need a help in fixing these issues contact us.

    and you don't even output messages telling me what the errors are???

  13. juggledad
    Member
    Posted 3 years ago #

    you have a bunch of <?= where you should have <?php

  14. bsndev
    Member
    Plugin Author

    Posted 3 years ago #

    Thanks, I made an update - should be ok now

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic