Good but only for specific use cases

And I want to word this very, very carefully and not point any fingers at anyone in particular, but this is a sad fact: We have seen competitors choose not to fully secure websites (using advanced, cutting edge or complex security systems) because doing that would potentially cause problems or complaints made to them. We will never do anything like that. We would rather create cutting edge security software and hear complaints then create or sell a product that does not secure a website 100%. 😉

@ashf – yep we will be eliminating things like AutoMagic buttons so that someone only need to do a one button click instead of several button clicks. This is a horrible thing for Developers and Coders, but great for the average person so that is the direction we are going in – less manual controls|less choices – simply just one button clicks. 😉

We have looked at the Wordfence and AIO UI’s and we don’t like either of them visually or functionally and in general. BPS does have the capability to turn all features on and off individually. We intentionally did not go the route of breaking up each section of htaccess code into separate options since that is actually much more of a pain in the neck than using BPS Custom Code, which allows someone to customize their entire htaccess files in one shot. So what we think is the real problem is that we have not made things clear enough in regards to Custom Code and explained why BPS Custom Code is far superior to any other methods used in other plugins like AIO or Wordfence.

I think the biggest problem is that a lot of folks get intimidated by copying and pasting htaccess code into BPS Custom Code. ie fear of making a mistake, fear of something going wrong, etc. Clicking a button or option setting is/does the same thing, but the code fear/intimidation factor does not exist because someone is not directly copying and pasting code. The obvious difference between the average person and someone who is a coder is a coder would prefer to see and handle code directly and an average person would prefer not to see and handle code directly and just click a button instead.

So in summary, we understand where the problems are, but are not exactly sure how to make all of this work for both Developers|Coders and average folks. ie removing things that Developers|Coders want is not smart so we need to figure out how to have both. Working on that.

Another possible idea is to leave all the manual control tools as they are and instead display a message to re-run the Setup Wizard. ie BPS detects something that requires the Setup Wizard to be re-run, someone re-runs the Setup Wizard and the Setup Wizard would automatically add|fix|install, etc. whatever that is.

Yeah that is what we were doing before and the complaint when we were doing that was “there is not enough help information directly on the page”. 😉 I don’t think we will change the terminology and phrasing of things because that would cause a lot of confusion. So whether or not Activate and Deactivate are the best choice of words, they are words/terminology that have used for years now so it would not be smart to change that.

With that said, if we do create a Simple Mode then it will be very simple with very little explanation of what is going on directly inpage. The assumption would be that someone either does not care to know what is going on or would not understand the help text anyway. 😉

@chrisplaneta – I think you are getting too much into personal preference with the Idle Session Logout settings vs overall best method to cover everyone’s preference/needs. If we did that then we would get lots of questions like “how do I disable X Role”. How do I know that? Because previously this help text did not exist: “Check to enable. Uncheck to disable. See the readme help button for more details” and we were asked that question over and over. 😉