Support » Plugin: BulletProof Security » Steps required after updates

  • Resolved Dumel

    (@dumel)


    Why are there steps required after updates? I updated one of the 31 blogs I support this morning (I update them using WPRemote) just to see if I will be required to do the two step tango again after this update (as was the case with the previous one) and right enough, there was the warning message. The warning message went away after visiting the plugin section so now I don’t know if I have to do these two steps or not? I would not be able to continue using this plugin if it requires physical intervention on each blog after an update.

    https://wordpress.org/plugins/bulletproof-security/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author AITpro

    (@aitpro)

    The one-time update steps should only happen once. The check to trigger/display the one-time update steps is if the “BEGIN WordPress” and “END WordPress” placeholder text exists in your root htaccess file. So if the placeholder text is added to the root htaccess file at a later time by something else (another plugin, etc) then you may or may not see the update steps help message displayed to you depending on how quickly BPS can automatically fix/correct whatever mistake was made by something else (another plugin, etc). Since the update help message went away on its own I assume the BPS self-correcting/self-fixing automation kicked in to correct a mistake/error that was made by something else (another plugin, etc).

    The alternative to BPS doing self-fixing/self-correcting/self-repairing automation for whatever causes these types of problems is your website would crash or all of your website links would be broken or other various problems. So I will look into a way to see if it would be smarter just not to display any help messages and just automatically fix, repair and correct mistakes made by other things.

    I will test wpremote and do some remote installations and see if I can recreate this scenario.

    Plugin Author AITpro

    (@aitpro)

    hmm maybe you saw the other BPS error messages about a root and wp-admin htaccess file not being a valid BPS htaccess file? There is a known condition caused by installing multiple plugin updates at the same time which will delay or throw off the BPS checks. If that is what occurred then you would just need to click anywhere or refresh your Browser so that BPS can overcome whatever problem caused that delay in BPS error checking. The end result is still the same – BPS automation is designed to be self-repairing/self-healing/self-fixing.

    FYI – with PHP code processing you will always be seeing the past in regards to error messages and not the present.

    Example: function A is processed and contains a text error message when function A is processed. The text message is displayed after function A is processed. That text message reflects the present at the moment function A is processed and then it would reflect the past after that.

    In other words, the BPS error messages you saw were leftover from the past and BPS already automatically took care of what needed to be done.

    Thanks for both your replies. If I understand you correctly, the fact that I see those error messages is not a problem because by then BPS has done its self-healing thing? You see, it is not a problem to just click anywhere or refresh my browser, the problem is that I have to do that 31 times. But if those errors are nothing to be concerned about then I won’t worry too much. Unless of course if I do click somewhere else and they don’t go away. Then I will take action. I always first test one update on one blog first, then visit the blog to check the effects of the update before doing the rest. So this doesn’t happen only when I update many plugins in one go. Today I first tested by doing one update on one blog, and I saw the warning messages. It would be great if you could do some testing, I appreciate the effort.

    Plugin Author AITpro

    (@aitpro)

    Yep it is not a problem. Here is another way of looking at it. You only have to do something about a BPS displayed error or help message if it does not automatically go away on its own. We are a split camp over this issue now for over a year. ie Should we do automated things silently or should we display messages? A more advanced approach (and the leading direction considered by all parties involved) would be to do automated things silently and then at Cron intervals do error checking.

    I have already done testing and have confirmed that if the BPS upgrade installation takes longer than 1 minute (either direct or remote) or if you do not login to your website within that 1 minute installation period then instead of seeing – “BPS did everything you are good to go” (slang of course) you would see the error messages displayed. The upgrade check is based on a 1 minute upgrade/installation time period.

    Long story short – we are looking for a perfect balance. ie some folks want to see “all is well in the world” or “all hell has been unleashed” messages and other folks do not want to see anything. I believe the advanced concept with Cron interval error checking above is going to be the winner.

    Plugin Author AITpro

    (@aitpro)

    “…or if you do not login to your website within that 1 minute installation period…”

    Oops forgot to add the most important scenario relevant to remote installations. Updated above…

    Plugin Author AITpro

    (@aitpro)

    Also this is important to point out with remote installations. BPS will ONLY complete the additional automated things during a BPS upgrade based on your User Role. You must be an Administrator or BPS will not do those automated things. So since it is not possible to verify your User Role from a remote location (other website) then BPS can only verify that you are an Administrator by the fact that you are logged into the site as an Administrator.

    Flow: BPS plugin files are installed remotely >>> you log into the site as an Administrator >>> BPS verifies that you are an Administrator >>> BPS completes the additional automated upgrade steps that require Adminstrator permissions.

    Plugin Author AITpro

    (@aitpro)

    And one final thing: The additional automated upgrade steps are simply updating the htaccess files. Everything else is already completed when you perform the remote installation. So let’s say you don’t log into a site for a week. This would only mean that BPS is using the older htaccess files in the previous version. The first time you login to that site again (a week later) the htaccess files would be automatically updated.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Steps required after updates’ is closed to new replies.