Closed Bug 165726 Opened 22 years ago Closed 22 years ago

install (upgrade) will not keep all of the old preferences

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mozilla, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 I upgraded from 1.1a to 1.1. After the upgrade, few of my preferences were reset. I am attempting to list each feature that changed, and am very certain about some of those, but since I use Mozilla on several machines, I am not certain about others I do not use that often. This is the list of things that were reset (possibly not exhaustive): Browsing History – remember pages for the last X days, was 10 now 30 (not absolutely positive about this one) Default Search Engine, was Google now is Netscape (certain about this) Tabbed browser: Load links in background, was selected now is not (certain about this) Open tabs on Ctrl-Enter, was selected now is not (certain about this) Security: Accept images from originating web-site only, was selected now not (not sure about this one). Reproducible: Didn't try Steps to Reproduce: Haven't tried to reproduce, if I get a chance to install Mozilla on a clean machine, will try. Do an install of 1.1a, change preferences, then upgrade to 1.1. Actual Results: Some preference setting were reset to defaults Expected Results: Should not change any preference settings
There is no "upgrading" from an older build to a newer one. That is totally unsupported. The only supported method is uninstall the old build and install the new one. Settings are not stored in the Mozilla installation directory. However, installing over a build already in place can overwrite some settings. Someone please mark this INVALID.
using moz1.1 on winme. i have to concur - reusing a prefs.js file from a previous version of moz is not technically supported at this time, since changes to the way prefs are handled can occur between versions. on top of that, wfm when i migrated my profile up to 1.1, so there's that too. resolving as invalid - if i missed something here, feel free to reopen, but add me to cc.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.