Shopsite messes up the custom css - why?

[lolka]

Hi,
I am hoping to find an explanation for a really strange thing.
So, I'd like to modify MU-000002.css file.
Here is what I do (following the directions I've found @ this forum):

I go to the Custom Templates, then to the Includes, then Copy ShopSite Publish (and I copy the original file under different name).
Then I open my customized file, VALIDATE IT, open my custom-named copy in the backend of SS, copy my css and paste it and save.
Then I click its name (still in the backend), give it a name of the original (MU-000002.css), hoping it will overwrite the original.
It KINDA does it.
But EVERY SINGLE TIME it EATS parts of the code, usually classes' names and first curly brackets. Sometimes one, sometimes five of them. Sometimes I edit this publish about 15 times and chances are, by the 15th time it won't eat anything, but that doesn't really work for me.

I do have an access to the FTP but this is not help, either. I can copy and overwrite file via FTP just fine, but it works correctly until I open the backend... and then it replaces my custom file with the crappy half-way eaten code. This way it perfectly blocks the store owner from making any product updates, because every time the store's front end changes into a total mess.

The store is not installed in the root folder (I specifically asked Customer Support if the store can be installed in this spot and the answer was "yes, no problem"). As a result, I have two cgi-bin folders, two publish folders and who knows how many "original" css files.
Is each edit saved somehow twice and one overwrites the other or something else?

I am about to switch to different store, this thing is way too frustrating. Any help will be greatly appreciated.

[robm]

ShopSite templates use the "#" character as a comment in the template. If you need to use the "#" character as the first character on a line, try putting a space in front the # sign, which will allow it to be treated as code instead of a template comment. See if that helps.

Rob

[Jim]

What Robm said is correct. So make sure no code in the template starts with the # as the very first character on a line. Add a space in front of it and it will be ok.
Note: Files that display in the Publish area under Merchandising > Custom Templates > Includes > Publish will be processed for ShopSite template tags and then moved to the Publish folder that is in your store's output directory. If you ftp files to that location and have a file by the same name in the Merchandising > Custom Templates > Includes > Publish section the one in the output directory publish folder/directory will be overwritten on the next publish.