Upon further review, consideration, and feedback, I am modifying my previous statement in this subsequent post.

Quote Originally Posted by mc12345678 View Post
I realize this is somewhat of a dated post that I am commenting on. The suggestion above was to rename the extension of a replaced file with bak as the only extension or to add a hyphen and the bak. While I do not work in the SEO business nor for any of the search engine groups, etc. Reports have recently been that the final extension should not be simply bak. Ie, in the above example MyStylesheet.bak would be considered a potential pci scan issue. The practice of renaming the extension of a file to be disabled is a good practice. There are some directories though that will read all files that for example end in .php and future development may expand the extension(s) that are autoread . The disabled files should be removed from the system however, once identified unnecessary and no longer needed there. A backup copy should be kept though, just in case.
While the impact of my incorrect statement would be to significantly minimize extraneous files on the server, it would have a negative impact on understanding of how ZC works, the expectations when making modifications, and ways to use that functionality when developing (and troubleshooting) new programs and plugins.

So when "disabling" a file, modifying the filename say from filename.php to filename.phpold14-09-23 would be sufficient (if not overly so) to prevent the file from being loaded by the default ZC code. As shown above, this filename also would indicate to reviewers that it was renamed on the 23rd day of the 9th month of the "14th" year. (Sequence chosen to facilitate sorting of files by name as this sequence, YY-MM-DD, will sort keeping the year and month in sequence and any day adjacent to the next/previous.)

Happy Zenning!