Home › Forums › WordPress Plugins › Hide My WP › Can't activate HMWP without getting an internal server 500 error

This topic is: resolved
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • November 30, 2017 at 7:20 pm #19019
    Hyperknight
    Pro
    Post count: 28

    One of my theme support guys disabled HMWP during testing (despite me telling them specifically not to because disabling it always seems to cause an issue) and now I can’t re-enable the plugin without getting an internal server error that makes the site inaccessible.

    If I remove the text in htaccess between the tags <IfModule mod_rewrite.c> and </IfModule> access is restored, but as soon as I re-enable the plugin it automatically puts back the settings between those tags and the internal server issue recurs.

    I even tried deleting HMWP and re-uploading it so I could re-enter the settings from scratch, but it remembers the previous settings automatically and breaks the site again.

    I have no idea what the issue is with the settings and the conflict within the htaccess file as they functioned fine in the past (prior to disabling the plugin) but I’d really appreciate your help with a fix so I can actually get HMWP working again.

    Many thanks!

    November 30, 2017 at 7:50 pm #19020
    Hyperknight
    Pro
    Post count: 28

    Ok don’t worry about it. After messing for too long, I eventually deleted the following tables from my database:

    – hide_my_wp
    – hide_my_wp_undo
    – hmwp_ids_installed
    – hmw_all_plugins
    – external_updates-hide_my_wp

    And that seems to have reset the settings and allowed the plugin to function. Now I just need to reconfigure it all.

    December 1, 2017 at 4:47 am #19028
    Suman M.
    Post count: 12480

    Alright! The issue above usually happens if you have renamed wp-admin path name. If you did rename wp-admin, then when you deactivate HMWP you’ll also need to remove a line that you added in wp-config.php file.
    Let us know if any other queries.

    December 1, 2017 at 9:24 am #19034
    Hyperknight
    Pro
    Post count: 28

    Hey,

    Yes, I’ve been through similar issues before. Unfortunately this time the WP-CONFIG file already had the wp-admin path name removed – and I’m not sure if it was its removal that was causing the 500 error or not, but it definitely wasn’t there.

    Anyway, resetting via the database has worked out.

    Many thanks!

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.