Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Be aware of possible data loss when saving from iWeb' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Be aware of possible data loss when saving from iWeb
Authored by: phrayzee on Dec 19, '06 09:28:58AM

I don't think this is a bug per se. The default behavior of OS X is that if two folders have the same name but different contents, when you "copy" the contents of folder A over the contents of folder B, the contents of folder B are deleted and replaced with the contents of folder A. While this is an issue, it doesn't sound like a bug to me.



[ Reply to This | # ]
Be aware of possible data loss when saving from iWeb
Authored by: Dave Andrews on Dec 19, '06 11:27:44AM

Of course it is a bug. A copy operation took place without your express knowledge. The destination folder had never been used before by iWeb, it contained information not intended for iWeb. I did not ask iWeb to copy its output to this folder, iWeb chose to do this - without warning.
If you don't think its a bug then create a web site and call it any of the following
'Users', 'Applications', 'System', or 'Library' and save it to the top level of your hard drive. When it trashes your system without warning, remind yourself its default OS X behavior!

WARNING - DO NOT TRY THE ABOVE EXAMPLE



[ Reply to This | # ]
Be aware of possible data loss when saving from iWeb
Authored by: frgough on Dec 19, '06 12:02:44PM

I doubt that would work; you don't have write privileges for anything in System, so that will fail. Replacing Applications or Library will also probably fail since some of the files in those folders also will not be writable by you so you will not be able to replace them.

That said, the lack of confirmation of overwrite is a nasty bug.



[ Reply to This | # ]
Be aware of possible data loss when saving from iWeb
Authored by: fbitterlich on Dec 20, '06 02:38:38PM

Hmmm? Of course OS X does _not_ work this way. If it would replace the _contents_ of a folder every time you copy the _contents_ of another folder into it, with no name conflicts, how would you ever merge the contents of two folders?

OS X itself (read: the Finder) does never replace anything as long as the names are different. The problem described in this hint is unique to the iWeb application and is caused by iWeb thinking it "owns" the published folder. Serious bug if you ask me, and definitely against Apple's own guidelines.



[ Reply to This | # ]