• I’m using iThemes on several websites for some time now. After updating iThemes today on my own website all iThemes settings I had selected earlier were gone. I had to go through all the blocks and change all settings again.

    This causes an unnecessary security risk. And it means a lot of work for me on every website.

    Why does this happen? Why are settings not retained? Why is there now warning that original security settings are lost after the update?

    https://wordpress.org/plugins/better-wp-security/

Viewing 15 replies - 1 through 15 (of 24 total)
  • @boriskrielen

    Sounds like a bug since iThemes states in the New Dashboard FAQs section on this page that all old settings are migrated to the new iTSec Dashboard when updating to the 5.4.0 release.

    dwinden

    A bug? This is a great big screw up, we have 100’s of sites using this plugin and I am getting notice after notice of lock outs, backup zip files being emailed from sites we never had set up to email along with ’email lockout notifications being set to enable, all other settings lost on multiple installations.

    It is not a user friendly ‘new improved’ dashboard, where is hide the back end feature and now my email is automatically added to receive updates under the Network Brute Force Protection? Each section has to be saved individually or your new settings will revert back, sometimes it refreshes back to the top sometimes it doesn’t.

    Did they do any QA or testing before launching…sure doesn’t seem like it was very intensive if there was. Unfortunately a lot of our sites are set to auto update, going to change that straight away and going to delete this plugin and use something else. I would highly advise NOT to update this plugin and look for an alternative or wait until they sort it out.

    oh and you can’t disable 404 detection…

    ‘Away Mode’ has no options in it to do anything

    After update I cannot find “hide login area” anymore.

    Can’t disable ‘local brute force protection”
    Can’t disable “File Change detection” automatically sets to email notifications on update too.
    Malware Scanning option is gone…oh wait is it only available in pro now.

    What a disappointment.

    Oh my mistake malware scanning is there, off in the right sidebar now.

    Ok, I found it in “advanced” settings. This new interface is not so clear.

    @jefflloyd11

    I understand the frustration this new 5.4.0 release brings.

    However this topic was not created by someone else so that you can randomly dump anything you run into.

    @spatdesign

    Please have look at the 5.4.0 Introduction page. Especially the Advanced settings section.

    dwinden

    Thanks dwinden, I solved. The new interface has disoriented me. Can you tell me why I get a 404 error when I click on “forgot password”? I opened a topic about this but have not received replies. Thank you very much anyway.

    Had the same issue on at least one site (holding off on updating others).

    Some settings that were previously enabled were now disabled.

    @dwinden thanks for the tip on where to find advanced settings and things that are missing, I was pre-occupied trying to fix settings and stop being inundated with email notices.

    I’m sorry if you are offended by me posting related experiences and problems I’m having with the update of this plugin, and in your eyes it’s equal to a “randomly dump anything” mindset on my part. Granted I went off a bit quick but these are problems we are experiencing and besides not being able to find things easily at first there are other issues.

    I didn’t realize you were a moderator and dictate how people should respond, my apologies. Will you be answering the questions posted initially by @boriskrielen which is the same thing I am experiencing plus other problems or just stick to “Sounds like a bug since iThemes states in the New Dashboard FAQs section on this page that all old settings are migrated to the new iTSec Dashboard when updating to the 5.4.0 release.”

    That’s not really helpful…but thanks just the same.

    @drivenfaroff and @boriskrielen

    According to the 5.4.0 Changelog:

    Bug Fix: Fixed a bug where some modules would be enabled or disabled when they shouldn’t be after upgrading to the latest version.

    So it looks like this issue is still not fully under control.

    It’s probably a wise decision to wait till the child diseases are over …
    (I guess I’ve listened too much to van Gaal at Manchester …)

    dwinden

    @jefflloyd11

    No worries. I wasn’t offended at all.
    Just wanted to prevent receiving dozens of irrelevant emails related to this topic. I guess I could also unsubscribe from this topic …

    Oh, I’m not a moderator. We’ve all read the wordpress.org forum houserules πŸ˜‰ and know how to correctly use this forum. You don’t have to be a moderator to instruct\teach others πŸ˜‰

    Really think iThemes should deal with this issue.

    Did add another post when I digged up some relevant info from the 5.4.0 Changelog. Based on that info I’m confident iThemes knows exactly where to further deal with this particular issue in the plugin code.
    It’s their mess not mine πŸ˜‰

    dwinden

    Hey All,

    I’m really sorry to hear that you’ve run into this. This is something we did not see in testing. You can use the query below to revert your post-update options. Then you can update to 5.4.1. Please note these are two different queries. One is for a single site install, the other is for a Multisite install.

    1. -- Single Site - remember that the prefix could be something OTHER than wp_
    2. --
    3. DELETE FROM <code>wp_options</code> WHERE <code>option_name</code> = 'itsec-storage';
    4. UPDATE <code>wp_options</code> SET <code>option_value</code>=REPLACE(<code>option_value</code>, 's:5:"build";i:4041', 's:5:"build";i:4040') WHERE <code>option_name</code> = 'itsec_data';
    5.
    6.
    7. --
    8. -- Multisite - remember that the prefix could be something OTHER than wp_
    9. --
    10. DELETE FROM <code>wp_sitemeta</code> WHERE <code>meta_key</code> = 'itsec-storage';
    11. UPDATE <code>wp_sitemeta</code> SET <code>meta_value</code>=REPLACE(<code>meta_value</code>, 's:5:"build";i:4041', 's:5:"build";i:4040') WHERE <code>meta_key</code> = 'itsec_data';

    Thanks,

    Gerroald

Viewing 15 replies - 1 through 15 (of 24 total)
  • The topic ‘Original iThemes security settings lost after iThemes update’ is closed to new replies.