Yep it looked like that is what was going on with the WordPress rules. BPS actually allows users to automatically create their htaccess files with an fwrite that creates an entirely new htaccess file or uses one of the pre-made master files instead of appending / writing to an existing htaccess file. So basically BPS overrides Super Cache completely if BPS htaccess files are activated or reactivated after WP Super Cache settings are changed or modified in regards to mod_rewrite. :( I originally started out having the htaccess coding appended, but this turned out to be a huge nightmare due to people not having custom permalinks set up and some other issues so i switched over to having the htaccess file created for them automatically. A warning notification is displayed until they set up custom permalinks. I could write an exception for WP Super Cache, but I think the smarter and simpler approach to avoid any future issues is just to have Super Cache write to the top / beginning of the htaccess file instead of appending to the bottom. I will then make any necessary coding changes on my end so that BPS and WPSC will play nicely together - creating a notification that WPSC settings need to be saved again with a link to the WPSC settings page and whatever else needs to be done. I would just grab your htaccess code, but this could be problematic if people change their WPSC settings at some point so I think just a notification that WPSC settings need to be saved again if BPS is reactivated after WPSC. This seems like the best way to ensure that things are all working together correctly. And not a big inconvenience either - 1 warning notification and 2 clicks. If you have a better idea let me know. Thanks.