Permalinks – If your .htaccess file were writable we could do this automatically

[tcarson]

What area in the BPSpro custom code section do you put the Custom Structure code when you change your permalinks as it says:

If your .htaccess file were writable (http://codex.wordpress.org/Changing_File_Permissions), we could do this automatically, but it isn’t so these are the mod_rewrite rules you should have in your .htaccess file.

Thanks

[AITpro Admin]

You can disregard that displayed message.  Your root .htaccess file is locked so that is why you are seeing that message.  Permalinks are internal in WordPress itself and are not created in .htaccess code/files. What WordPress is trying to do here is a friendly reminder, but in this case you can disregard the message because it does not apply when you have BPS or BPS Pro installed.  BPS creates the standard WordPress .htaccess code that is required for custom permalink rewriting and of course contains all the BPS security filters combined into the standard WordPress Rewrite .htaccess code for custom permalinks.

[tcarson]

Thanks for the info.

[Lys]

[Topic has been merged into this relevant topic]

I’ve updated permalinks and don’t see this in secure.htaccess:
​Tried to put code in and it threw site offline. Deleted this and site came back on. Can you take quick look at my secure.htaccess file?
Just sent over email with site login info.
Thanks for any help on this.

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

[AITpro Admin]

You don’t want to see that code in your root .htaccess file. That is default generic WordPress htaccess code. BPS integrates that generic WP code into the secure.htaccess file already. Updating permalinks does 2 things – updates your internal WordPress permalink code and generates that generic htaccess code. Since you do not want that generic WP htaccess code added in your root htaccess file your root htaccess file should already be locked to prevent that mistake from happening.

Click the Activate buttons and the magic already happens – nothing else is required. Just make sure your root .htaccess file is always locked to prevent anything from writing code to your root htaccess file that will crash your website.

[Author]

Posts