Title: Install Basic pre-Pro and Ease to Remove
Last modified: August 22, 2016

---

# Install Basic pre-Pro and Ease to Remove

 *  Resolved [jimii](https://wordpress.org/support/users/jimii/)
 * (@jimii)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/install-basic-pre-pro-and-ease-to-remove/)
 * I use WP 4.1 with the twenty ten theme. Thinking of installing BPS – would like
   to test the basic model first and then if no conflicts – upgrade to pro. My hesitation
   is that I once installed one of the other company security plugins (that then
   was just recently bought out), and its transition went sideways badly. So I am
   a bit reticent.
 * I realize no guarantees – and so I’ve read the instructions on install and uninstall–
   as well as have trialed this on a very basic site which had a minor issue that
   you helped me solve right away – very impressive – as is your support close rate.
   If this doesn’t work with my site (ie plugin conflicts) – is it as easy as it
   seems to remove? And is the basic first and pro later the approach to take?
    
   Thank you. jim
 * (Site is a a multi-user site with just me as admin and all others as agents /
   editors / contributors posting property content. So it has a role or user switching
   plugin in place – allowing me to post as clients). The HT access code currently
   deployed has rewrite referer code in place and options -index plus super cache.
   Most of the other plugins are very standard).
 * [https://wordpress.org/plugins/bulletproof-security/](https://wordpress.org/plugins/bulletproof-security/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Thread Starter [jimii](https://wordpress.org/support/users/jimii/)
 * (@jimii)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/install-basic-pre-pro-and-ease-to-remove/#post-5598983)
 * On a leap of faith I installed the basic module and all good but the WP Super
   Cache needed to have the mod-rewrite refreshed to have it properly activated.
 * Unlocked the htaccess – clicked link to wpsc but receive the message:
 * You must have BEGIN and END markers in ” domain address url here ” for the auto
   update to work. They look like this and surround the main WordPress mod_rewrite
   rules:
 *  # BEGIN WordPress
    RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME}!-
   d RewriteRule . /index.php [L] # END WordPress
 * Refresh this page when you have updated your .htaccess file.
 * Do I insert the code above in the BPS htaccess file editor page – ? top or bottom?
   Is there something else I should be doing to this? thank you.
 *  Thread Starter [jimii](https://wordpress.org/support/users/jimii/)
 * (@jimii)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/install-basic-pre-pro-and-ease-to-remove/#post-5599002)
 * I believe I have resolved this myself, finding an article suggesting I ‘test’
   the wp super cache – which i did with a matching result.
 * Although wpsc plugin still shows the ‘ mod rewrite unable to update” it seems
   that is not unusual. If i am incorrect on this please let me know – otherwise
   I’ll tag as resolved in 24hrs.
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/install-basic-pre-pro-and-ease-to-remove/#post-5599012)
 * Oops it looks like you found an outdated error message that needs to be changed/
   corrected in BPS. The htaccess files no longer use BEGIN WordPress and END WordPress
   markers as of a few versions ago.
 * WP Super Cache htaccess cache code needs to be added to BPS Custom Code.
 * 1. Copy the WPSC htaccess cache code to this BPS Custom Code text box: CUSTOM
   CODE TOP PHP/PHP.INI HANDLER/CACHE CODE
    2. Click the Save Root Custom Code button.
   3. Go to the BPS Security Modes page, click the Create secure.htaccess File AutoMagic
   button and activate Root folder BulletProof Mode.
 *  Thread Starter [jimii](https://wordpress.org/support/users/jimii/)
 * (@jimii)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/install-basic-pre-pro-and-ease-to-remove/#post-5599063)
 * thank you very much for this – all seems fine with BPS as before – however still
   see the ‘cannot update the mod rewrite’ showing up in WPSC.
 * When pasting the WPSC into the custom code box – i did not include the #begin
   WP and the #end WP that was below it (there were no code rules in between just
   the begin and end statements). Should I have included those? Possibly – even 
   though nothing in there it would then allow WPSC to update the mod rewrite? (
   When “testing the cache” – it cleared just fine – same files – just the update
   ability seems off).
 * separate question on limiting log access will post new / separately. thank you
   again.
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/install-basic-pre-pro-and-ease-to-remove/#post-5599067)
 * Just copy WPSC code to BPS Custom Code and do the Custom Code steps. If you need
   some additional visual help click the Custom Code Video tutorial link on the 
   Custom Code page.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Install Basic pre-Pro and Ease to Remove’ is closed to new replies.

 * ![](https://ps.w.org/bulletproof-security/assets/icon-128x128.png?rev=1731938)
 * [BulletProof Security](https://wordpress.org/plugins/bulletproof-security/)
 * [Support Threads](https://wordpress.org/support/plugin/bulletproof-security/)
 * [Active Topics](https://wordpress.org/support/plugin/bulletproof-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bulletproof-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bulletproof-security/reviews/)

## Tags

 * [pre-install](https://wordpress.org/support/topic-tag/pre-install/)

 * 5 replies
 * 2 participants
 * Last reply from: [AITpro](https://wordpress.org/support/users/aitpro/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/install-basic-pre-pro-and-ease-to-remove/#post-5599067)
 * Status: resolved