User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008042609 Minefield/3.0pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008042609 Minefield/3.0pre The import and backup menu on the History section of Places still acts upon the bookmarks rather than the history. This is really strange, since one would expect this menu to import/backup the history especially when comming form History > Show All History. Reproducible: Always Steps to Reproduce: 1. Click History Menu 2. Click Show All History 3. Click Import and Backup 4. Click backup Actual Results: Backup will back up the bookmarks Expected Results: Backup should back up history. If we don't intend to provide an easy method to back up the history then we could always just disable this menu, but I'm sure someone out there wants to back up the History.
This is in a way related to bug 389804 -> bug 362985 (automatic backups).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h". In Thunderbird 3.0b, you do that as follows: Tools | Message Filters Make sure the correct account is selected. Click "New" Conditions: Body contains places-to-b-and-h Change the action to "Delete Message". Select "Manually Run" from the dropdown at the top. Click OK. Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter. Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
History backup would allow us to solve a bunch of problems related to: - hard corruption - soft corruption - downgrades - schema-incompatible upgrades
Summary: Import and Backup on History still acts on bookmarks - no way to backup history → Provide a history backup
not actively working on this atm.
Assignee: mak77 → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.