Just a warning to everyone that Frontpage may screw up some of your files. I renamed default.htm to index.htm and said "Yes" to updating the hyperlinks to the newly renamed file. It screwed up "admin_config_colors.asp". That's all.
You should change your title to "Warning: Frontpage WILL screwup your file..." That's why we recommend you not to edit any of the forum files with frontpage. Use another editor to edit your files. I'm sure it says so in the readme.txt file...if not, it should be.
I didn't use FrontPage to edit any of the files. I use Notepad. But like I said, FrontPage automatically updated the hyperlinks when I changed the name of default.asp.
quote: You should change your title to "Warning: Frontpage WILL screwup your file..." That's why we recommend you not to edit any of the forum files with frontpage. Use another editor to edit your files. I'm sure it says so in the readme.txt file...if not, it should be.
quote: Just a warning to everyone that Frontpage may screw up some of your files. I renamed default.htm to index.htm and said "Yes" to updating the hyperlinks to the newly renamed file. It screwed up "admin_config_colors.asp". That's all.
quote: I didn't use FrontPage to edit any of the files. I use Notepad. But like I said, FrontPage automatically updated the hyperlinks when I changed the name of default.asp.
It's actually the frontpage extensions that does the corruption and not just frontpage itself. That's why visual interdev people files get corrupted too.
My experience with FP2000 is that I can publish Snitz fine from a local copy to my host, I can use FP but use Notepad or another editor to edit asp pages within FP OK. Editing a file with the FP editor or renaming files or folders seems to mess things up.
Topic Locked
Posted - 12 April 2001 : 15:18:57
