Your Root htaccess File is not Locked

[ClicksFix]

Hello,

A few times a week I will receive this error message http://i.imgur.com/riQVuVl.png. When I go to my File Lock by clicking on “Click Here” in the error message my htaccess files are all locked, as seen here http://i.imgur.com/9sq9NOs.png (personal details omitted). I then refresh the page and the error message disappears (without me doing anything).

My File Lock says “Your Host Server is using CGI. Use the CGI File Lock and Unlock options.” With those instructions I only have the CGI options locked, as seen here http://i.imgur.com/e8bqehG.png. Is this a false error message or do I need to lock something else?

[AITpro Admin]

When you visit the F-Lock file lock page it automatically reapplies your current option settings, which is kind of clunky and is pending a “fix” at some point.  So if your Root htaccess file was unlocked then just by clicking the link in the error message, your Root htaccess file will be locked since your option settings are set to lock the Root htaccess file.  What might be happening is that your web host server is automatically unlocking the Root htaccess file if your web host does not allow 404 file permissions for .htaccess files.  It is fairly common for web host servers to automated applying file permissions to all of your website directories and files.  So you probably should check with your web host to see if that is what is going on.

[ClicksFix]

When the message has been displayed, I’ve tried to write over my htaccess code and am denied — as it should be. I did this to check if my htaccess file was locked. Wouldn’t that mean the file permissions are still enabled?

I have opened a ticket with my hosting company, but I’m pretty sure I am able to apply file permissions to my website directories as I have been in the past on other installs.

Is it redundant to enable locked options for the “DR” options http://i.imgur.com/DRP5QqM.png? Would that cause the message to be displayed? I only started to see this message appear once I updated to 13.2 a little bit ago, would that have anything to do with it? (It could just be when I noticed, though.)

[AITpro Admin]

Your web host may only allow 444 file permissions for htaccess files and if they are automatically changing the 404 file permissions to 444 then you would not be able to write to a file with either 404 or 444 file permissions until the permissions were changed to either 604 or 644 file permissions.  Disregard the “DR” option settings.  F-Lock file lock is a very old BPS Pro feature created 6+ years ago and it is basically defunct/outdated.  We have just kind of left it there and may just nuke it altogether at some point.  The F-Lock Folder Lock feature was also a silly idea that someone requested a long time ago that may also be nuked at some point too.  😉  So basically anything in F-Lock (file lock or folder lock) can just be ignored/not used.

[ClicksFix]

Okay sounds good 😉 This clears it all up. Thanks for your fast support.

[Max Johnson]

The issue is because a protected directory’s subdirectories inherit their parent directory’s password protection. The lock iconindicates that Directory Privacy configurations already exist for that directory.

[Author]

Posts