Closed Bug 314137 Opened 19 years ago Closed 19 years ago

Custom search plugins are deleted upon installation/upgrade.

Categories

(Firefox :: Search, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 311626

People

(Reporter: mto, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 Previouss custom search engines are deleted when installing Firefox 1.5 RC test build. I had many search plugins installed, I even had many custom made ones for my own personal use that took many hours to create. When I upgraded installing 1.5RC all search engines were removed and replaced by the 1.5 default ones. They are not even backed up! - Custom search engines should not be removed, just as bookmarks should not be removed. - It would be ok to add or update to existing search plugins, but never remove them. Reproducible: Didn't try Steps to Reproduce:
In firefox 1.5 search plugins are installed into the user profile so updating will not overwrite them. Unfortunatly the update from 1.0.x to 1.5 will overwrite the search plugins. *** This bug has been marked as a duplicate of 123315 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
I think it's great that search plugins be keept from 1.5 on in the user profile... sounds ideal. But removing current ones during update from 1.0.x to 1.5 is a terrible thing to do, a huge mistake. They should either be backed up somewhere, keept for all users, or moved to existing user profiles.
I've been reading bug 123315 I dont see how this is a duplicate of it. It is a bug, regresion caused by the fix in 123315, but not a duplicate of it. - 123315 is about the need to move search plugins to profile, and I think that's great. - This here is about a bug in how it was implemented: Custom search plugins are DELETED while till now they were always keep. (REGRESSION). Its a bug caused by the fix in 123315, but not the same bug. I dont think this should be marked as resolved duplicate and if fact should be a 1.5 blocker.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
*** This bug has been marked as a duplicate of 311626 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.