Plugin Author
AITpro
(@aitpro)
BPS creates new htaccess files for your website. To combine any old pre-existing htaccess code and any new custom htaccess code that you want to add/create and save it permanently use BPS Custom Code.
https://wordpress.org/plugins/bulletproof-security/faq/
Restore your old root htaccess file from a backup. Then use BPS Custom Code to combine your old htaccess code into your new BPS htaccess files.
http://forum.ait-pro.com/video-tutorials/#custom-code
Plugin Author
AITpro
(@aitpro)
A decision has been made to add a check for pre-existing custom htaccess code using the Setup Wizard Pre-Installation Checks to avoid this type of problem in the future. Currently your pre-existing root htaccess file is backed up when the Setup Wizard is run, but if the Setup Wizard is run again then that original root htaccess file backup is overwritten each time you run the Wizard. Instead of going the direction of creating multiple root htaccess backup files it is smarter to just not create a new BPS root htaccess file if pre-existing custom root htaccess file code is detected. If pre-existing custom htaccess code is detected in the root htaccess file then display manual steps/instructions on how to use BPS Custom Code to combine pre-existing custom htaccess code into the new BPS standard root htaccess file.
In the past, it has been pretty rare that someone will have created any custom htaccess code in their root htaccess file, but these days it is much more common so this new Setup Wizard check is important to do.
Important Note: BPS standard htaccess files are master htaccess files that incorporate the WordPress Rewrite loop, therefore appending or automating inclusion of other pre-existing htaccess code is not possible to do in order for everything to work correctly. Combining custom htaccess code in the appropriate places in the root htaccess file using BPS Custom Code is the only way to ensure that all additional custom htaccess code is in the correct places/positions/hierarchy of the root htaccess file.
Thread Starter
SJW
(@whitsey)
Thanks for the feedback.
All wordpress sites using permalinks will have created custom entries in the .htaccess.
Also, I 301 redirect the non-www to the www url on every site I create.
Plugin Author
AITpro
(@aitpro)
Ok use BPS Custom Code to add your custom htaccess code to combine it into the standard BPS root htaccess file. This Custom Code video tutorial: http://forum.ait-pro.com/video-tutorials/#custom-code shows the basics of how to add things like redirect code. If you need a specific answer to a specific question like “which Custom Code text box do I put X code in” then post your custom htaccess code and I will tell you where it goes.
Plugin Author
AITpro
(@aitpro)
All wordpress sites using permalinks will have created custom entries in the .htaccess.
Hmm I wonder if you think that the standard WordPress Rewrite htaccess code is custom htaccess code. If so, it is not custom htaccess code and is just the standard block of htaccess code that WordPress creates when you use any/all custom permalink structures. BPS already includes/incorporates that standard WordPress Rewrite htaccess code in the BPS root htaccess file.
Plugin Author
AITpro
(@aitpro)
Here is a post that has instructions on how to add non-www to www and www to non-www Rewrite/Redirect custom htaccess code to BPS Custom Code: http://forum.ait-pro.com/forums/topic/htaccess-redirect-www-to-non-www-htaccess-redirect-non-www-to-www/#post-5566
Thread Starter
SJW
(@whitsey)
Hmm I wonder if you think that the standard WordPress Rewrite htaccess code is custom htaccess code. If so, it is not custom htaccess code and is just the standard block of htaccess code that WordPress creates when you use any/all custom permalink structures. BPS already includes/incorporates that standard WordPress Rewrite htaccess code in the BPS root htaccess file.
Not fussed about what to call it but moreso, it was there before BPS, then after activation, this was blown away and no links worked until I restored permalinks.
Plugin Author
AITpro
(@aitpro)
Yep, we found a bug that was doing that and it has been fixed in BPS .52.9. Anyway it is good to use the exact technical terms for everything so that everyone knows exactly what the other person is talking about. ie orange = pineapple is not going to work to well. 😉
Plugin Author
AITpro
(@aitpro)
The bug was fixed in .52.9:
http://forum.ait-pro.com/forums/topic/bps-changelog/
BugFix: Additional conditional check added for standard WP rewrite code block removal. Only remove the standard WP rewrite block of code if the root htaccess file is a standard BPS root htaccess file.
Setup Wizard Root htaccess File Backup feature was added:
http://forum.ait-pro.com/forums/topic/setup-wizard-root-htaccess-file-backup/
The Setup Wizard checks your current root htaccess file for any existing custom or additional htaccess code that is not standard WordPress htaccess code or BPS standard htaccess code. This is a one-time event that occurs the first time you install BPS. If the Setup Wizard detects any existing custom or additional htaccess code in your root htaccess file, a message is displayed to you with a “Download Root htaccess File” button to download your root-htaccess-file.zip file to your computer as a backup.
