Unable to Restore Bookmarks

RESOLVED INCOMPLETE

Status

()

Firefox
Bookmarks & History
--
major
RESOLVED INCOMPLETE
10 years ago
8 years ago

People

(Reporter: Linda Ewen, Unassigned)

Tracking

({dataloss})

3.0 Branch
x86
Windows XP
dataloss
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

I see the backup file bookmarks-2008-06-24.json but FireFox says it is unable to restore.

Reproducible: Always

Steps to Reproduce:
1. organize bookmarks
2. restore from backup
3. select backup
Actual Results:  
Message: Unable to restore from backup.

Expected Results:  
It should have restored the bookmarks.
Component: Bookmarks → Places
QA Contact: bookmarks → places
bug 458683 and bug 448584 are possible causes of this
we can't check which of them is the culprit without looking at current json or
places.sqlite, so resolving incomplete.
feel free to reopen if you can provide one of them, hwv this should be fixed
for 3.1
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Depends on: 458683, 448584
Resolution: --- → INCOMPLETE
Keywords: dataloss
Version: unspecified → 3.0 Branch
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
You need to log in before you can comment on or make changes to this bug.