The only 'problem' is trying to figure out which one(s) to delete. FP cannot work with just a regular .htaccess file and must attach a number to it -- so it knows the last one it was working with. If you create a regular .htaccess file (with no numbers) it will prevent FP from working properly.
So, to remove the extra ones, best to have the account owner use their FP program to try and delete the ones not needed.
So, to remove the extra ones, best to have the account owner use their FP program to try and delete the ones not needed.
Hi Website Rob,
Would it work to examine the filedate? Like with 'ls -al'? Would that tell you the 'last' one? Or is there more to it than that?
That would tell 'you' when the last one was, but do you really want to add this type of maintenance to your 'to do' list? And if (accidents do happen 
) the wrong one is deleted, there will be some explaining to do, to the Client -- since FP will no longer work for them.
Much easier IMHO, to have the Client be aware of what FP is doing in this regard, and pass the maintenance over to them. If the situation seems to get out of control (many, many, FP .htaccess files being created) you can always make maintaining them 'an account requirement' and see if that helps.
Just a thought.
) the wrong one is deleted, there will be some explaining to do, to the Client -- since FP will no longer work for them.Much easier IMHO, to have the Client be aware of what FP is doing in this regard, and pass the maintenance over to them. If the situation seems to get out of control (many, many, FP .htaccess files being created) you can always make maintaining them 'an account requirement' and see if that helps.
Just a thought.