Version 6 of the CMS, with its Firefox-ready interface, seems to not like people who work fast. If you're having trouble with pages that don't seem to save correctly, or disappearing content, slow down! Back off on the reins a bit and give the CMS a chance to do its thing.
If you've lost content, use the History tab to find it again. You can actually revert to older versions of a page through the history tab as well.
We're hoping that this will be corrected in later patches.
It can be tempting, when removing anchors or LinkSetEntries to simply delete the text without Unmarking the page for publish. This can result in disaster.
If you see a page that is completely trashed visually, you've seen a page suffering from this malady. To fix it, the empty page must be found and unmarked for publish.
To prevent this always unmark for publish pages that you want to get rid of. If you have a page that you expect to use next year, or if you just want to keep a copy of a certain page type around for later use do not merely remove the text.
If you should even be stuck with your cursor as an hourglass for a long period of time, don't panic. This can often happen if you attempt to check in a page while we're sending out a publish, or if you try to check in a large section of the tree.
Avoid closing or killing the CMS client if this happens. While it hasn't occurred recently, in the past there were some instances of pages becoming "stuck" between being checked out and being checked in when the client was closed during the process.
While the table editor has improved in the newest version of the CMS, empty table cells cause all kinds of grief.
Empty table cells must be filled with a character other than a space. Most commonly, "--" is used.