What’s with all the htaccess files?

Hi @aljuk, normally our plugin will just backup .htaccess file when user updating .htaccess content on our plugin or saving some setting (e.g. the setting with This setting will edit the .htaccess file).

May I know which cache is flush button you click will create a new htaccess backup? Is it on LiteSpeed Cache Manage page?

Hi,

usually I use the button in the admin bar whilst I’m in wp-admin.

Every time I do so, or if I disable and re-enable the plugin temporarily (which I do quite often because I use a page builder which can’t edit whilst the cache is active), several new htaccess get generated, and the number builds up quickly.

.htaccess_lscachebak_orig
.htaccess_lscachebak_01 (ten of these, numbered sequentially)
a zip file containing more

Hi @aljuk ,

A better and accepted solution would be to fix up the builder, since it is a normal process to keep a backup of the .htaccess files, if the settings are changed or rebuilt, to restore previous .htaccess file, incase something goes wrong.

Which builder do you use?

I had the same problem and manually deleted them

I develop sites with Oxygen, which replaces the standard theme system altogether. Its Sandbox is a kind of hybrid of the back and front of the site, and caching kills it. In normal front end operation it works very well with Litespeed cache.

But anyway, that was just one example. Whenever I simply flush the cache, I’m seeing multiple backups created, and they multiply quickly. One or two would be understandable, but 11+ seems a bit excessive.

I’m just a stickler for keeping my installs neat and tidy ??

Hi all, we will release the fix for this issue in version 3.0.

@aljuk, may I know which page builder are you using? We can make our plugin compatible with your builder that you do not need to switch it on and off when you editing.

Hi, that sounds great!

I use Oxygen : https://oxygenbuilder.com/

Hi @aljuk, could you please join our Slack channel or submit a ticket here, we need more details about the builder for developing the 3rd party support code, thanks!