Closed Bug 250733 Opened 22 years ago Closed 22 years ago

Profiles aren't portable after installing extensions/themes

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 246209

People

(Reporter: whimboo, Assigned: bugs)

Details

The last days I'm trying to get my profile to work with different OS. So I moved it to another partition which is accessible from Windows and Linux. Without any installed extensions/themes it's working properly. But trying to share a profile with extensions or themes, the profile sharing doesn't work. This problem still came up with the integration of the new extension manager for Firefox and Thunderbird. After analyzing the chrome registration I recognized that all extensions and themes are stored with absolute paths within the chrome.rdf. c:baseURL="jar:file:///e:/firefox/extensions/%7Bbf591015-b599-4125-9428-3cb746ddca31%7D/chrome/mnenhy.jar!/content/mnenhy/" This is definetely the wrong way cause this way deny any sharing of profiles. Instead a relative path should be used for every extension/theme. Cause we know that they are located within the profile we don't need any absolute path. IMO it should be implemented soon.
Asking for blocking Aviary1.0RC1 cause this a nasty bug which should be fixed.
Flags: blocking-aviary1.0RC1?
Dupe of Bug 246209?
This is covered in bug 246209. It has unfortunately been -'ed by bsmedberg for 1.0. *** This bug has been marked as a duplicate of 246209 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
v.
Status: RESOLVED → VERIFIED
Flags: blocking-aviary1.0PR?
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.