WordPress.org

Ready to get started?Download WordPress

Forums

Acunetix Secure WordPress
[resolved] Secure WordPress Breaks Site! (23 posts)

  1. tpaine54
    Member
    Posted 2 years ago #

    There needs to be a third option to augment broken/works called "Broke my site!". Amateur hour.

    Warning: require(inc/swWSD.php) [function.require]: failed to open stream: No such file or directory in /home/content/88/7797788/html/wp-content/plugins/secure-wordpress/secure-wordpress.php on line 112

    Fatal error: require() [function.require]: Failed opening required 'inc/swWSD.php' (include_path='.:/usr/local/php5/lib/php') in /home/content/88/7797788/html/wp-content/plugins/secure-wordpress/secure-wordpress.php on line 112

  2. Tevya
    Member
    Posted 2 years ago #

    Yep, upgrading killed my site too! DO NOT UPDATE!

  3. Tevya
    Member
    Posted 2 years ago #

  4. alanpae
    Member
    Posted 2 years ago #

    I got the exact same error message about line 112. Removed the whole directory tree and will downgrade to 2.01.

    DO NOT UPGRADE!

    alan

  5. windracer
    Member
    Posted 2 years ago #

    Took me a while to figure out it was this plugin that killed my site. Thank goodness downgrading worked. Ouch.

  6. cito
    Member
    Posted 2 years ago #

    Same happened to me, I updated to new version of Secure WordPress plugin and it broke my site, not only would the admin panel no longer load the entire site would no longer load.

    Was able to fix by ssh'ing to my site and going to wp-content/plugin folder and manually deleting via rm -r secure-wordpress directory.

    then the site was back up with no problems.

    Hopefully the creator will update their plugin or post a reason why it's breaking sites all of the sudden.

  7. gshag33
    Member
    Posted 2 years ago #

    Same thing happened to me..

    Luckily did a Google search and found this thread

    Deleted SecureWP plug-in directory over FTP and site is working again

  8. zicocarioca
    Member
    Posted 2 years ago #

    Another victim here.

    Warning: require_once(inc/json.php) [function.require-once]: failed to open stream: No such file or directory in /home/content/86/7318986/html/wp-content/plugins/secure-wordpress/secure-wordpress.php on line 105

    Fatal error: require_once() [function.require]: Failed opening required 'inc/json.php' (include_path='.:/usr/local/php5/lib/php:/home/content/86/7318986/html/wp-content/plugins/instapress/instagram-php-api/:/home/content/86/7318986/html/wp-content/plugins/instapress/classes/:/home/content/86/7318986/html/wp-content/plugins/instapress/PowerHour_Geocoder/') in /home/content/86/7318986/html/wp-content/plugins/secure-wordpress/secure-wordpress.php on line 105

    DO NOT UPDATE.
    If you did, delete the plug-in directory via FTP.
    Then cross your fingers, like you do every time you upgrade anything.
    Science, pff.

  9. soullotus
    Member
    Posted 2 years ago #

    I updated 3 plug-ins..can't remember what they were, and I got the same thing. I am not all that savvy. Since I can't get onto my website, how do I fix this?
    I don't know what FTP is.

  10. galbaras
    Member
    Posted 2 years ago #

    Just updated to 2.0.2 and got a missing JSON file message. Went back to 2.0.0 and it works.

  11. soullotus
    Member
    Posted 2 years ago #

    If anyone else here is clueless like I am, I just called my hosting company, and they helped me fix this. When all else fails...good luck everyone.

  12. paulzag
    Member
    Posted 2 years ago #

    If you don't know what FTP is you probably should NOT be automatically updating plugins.

    Your site will be fine. I think the developer accidentally left the sub-directories out of the package.

    Go vote BROKEN on the plugin directory so WordPress will hopefully remove the update here http://wordpress.org/extend/plugins/secure-wordpress/download/

    As others have said just delete the plugin directory. If you don't know how to use SSH or FTP then do this:

    Log into the control panel of your site (normally cpanel or cp) use the file manager to navigate to wp-content/plugins/

    delete the secure-wordpress directory.

    install v2.0.1 from http://downloads.wordpress.org/plugin/secure-wordpress.2.0.1.zip

  13. rbmark
    Member
    Posted 2 years ago #

    Me too! I get a fatal error on line 112.

  14. microberto
    Member
    Posted 2 years ago #

    LOL. Way to test. Breaks for me on WP 3.1.x

  15. zepolo
    Member
    Posted 2 years ago #

    Yep, upgrading killed my site too

    Remove this plugin !

  16. archproject
    Member
    Posted 2 years ago #

    Same here .... damn ... got panic for a while and just deleted it via FTP and site works again. What the heck happened

  17. SaltwaterC
    Member
    Posted 2 years ago #

    The author forgot to commit all the directories that are part of the plug-in. Only the files are in. Well, I guess you don't need an attacker do DoS your WordPress. Secure WordPress does this just fine.

  18. The Sowbug
    Member
    Posted 2 years ago #

    derp... delete.

  19. formica
    Member
    Posted 2 years ago #

    Yup... me too, just remove the secure-wordpress plugin folder.

  20. WebsiteDefender
    Member
    Posted 2 years ago #

    Hi,

    First of all we are really sorry for the inconvenience caused with this plugin update.

    We already uploaded a fixed version of the plugin which can be downloaded from: http://downloads.wordpress.org/plugin/secure-wordpress.2.0.3.zip.

    If you have problems accessing your blog because of the plugin update, simply login via FTP or your host's control panel and delete the plugin directory. The default plugin directory can be found in /wp-content/plugins/ WordPress sub directory.

    While hoping you find this plugin useful, feel free to post any queries or suggestions you might have on the WebsiteDefender forums; http://www.websitedefender.com/forums.

    Looking forward to hearing from you.

    Regards,
    Robert Abela
    Technical Manager - WebsiteDefender

  21. Workshopshed
    Member
    Posted 2 years ago #

    2.0.2 on WordPress 3.1.2 on PHP 5.3 caused a white screen, version 2.0.3 works ok

  22. Natural Beauty Spot
    Member
    Posted 2 years ago #

    Hello,

    Just upgraded to 2.0.3 and it work fine. :)

    Thanks for the quick response and update.

  23. WebsiteDefender
    Member
    Posted 2 years ago #

    Glad all is working fine and thanks for using the plugin :)

    Have a great day.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic