goglcost.blogg.se - Corrupt firefox profile manager

#Corrupt firefox profile manager how to#
#Corrupt firefox profile manager pro#
#Corrupt firefox profile manager code#
#Corrupt firefox profile manager zip#
#Corrupt firefox profile manager download#

From it, I launched one of my ff versions, with one of my profiles, chosen as I wanted, launched as I wanted. Going one level up on the ftp directory, I saw you have a beta2.

I downloaded it and got an error message on trying to launch it. If all I cared about was how fast the browser loaded, I’d still be using IE. While I’m certainly not a typical user, I’m hardly the only “power user” who uses Mozilla products so I *can* do things like that.

#Corrupt firefox profile manager code#

I can understand the logic to wanting to pull the ProfileManager code out of FF and other Mozilla products, but there *has* to be a replacement for the functionality before it goes away. Is there a way to tell ProfileManager where things live when it can’t find them? Profiles are all under D:\Mozilla\Profiles\\version\ D: is the principal data drive, shared across OSes. There are a dozen profiles defined in that profiles.ini file. My profiles.ini file lives in F:\Documents and Settings\Dennis McCunney.ARDA\Application Data\Mozilla\Firefoxį: is the XP boot drive. (I occasionally use -no-remote to have more than one active at a time.) I have multiple Mozilla products, with multiple profiles per product, and shift between them using appropriate “-p ” statements on the shortcuts that start them. So I use ” -P” to access ProfileManager, and create profiles in specific desired locations to make management easier. I don’t care for where Mozilla code creates profiles by default under Windows. The desktop machine has five physical drives.

#Corrupt firefox profile manager pro#

The main OS in use is Windows XP SP3, though Win2K Pro SP4 qnd Ubuntu Linux 10.10 are available. The ProfileManager window flashes on screen briefly then disappears. ” nsresult: “0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)” location: “JS frame :: chrome://profilemanager/content/utils.js :: getFile :: line 287″ data: no] Running it, I see the same error reported by others: I just downloaded and installed what I believe is the current version of ProfileManager. Using a different location than the one specified adds no value for most testers (there are better ways to protect a profile and its not even an issue if you are the only one with access to the PC) and prevents this tool from being used to move a profile. Please consider either changing the behavior, adding a optional setting to enable the current behavior, or adding some menu command that updates profiles.ini to use a profile at the specified location. I realize the bug report states this is not a end user tool but Mozilla removing support for the profile manager and this utility being the only available substitute creates a real problem. when I tell it to create a profile at C:\Users\eric\Profiles\Firefox\tanstaafl it created a b0myawu9.tanstaafl subdirectory there and updated profiles.ini to use it instead. That doesn’t work with this utility as it creates a subdirectory with a different name instead. It relies upon the profile manager updating profiles.ini with the specified location when you create a profile.

#Corrupt firefox profile manager how to#

That is why documents how to move a profile using the profile manager. Our experience has been that moving a profile is a common user task, and that editing profiles.ini is very error prone for many users. I’m a moderator on the MozillaZine forums. To use it with the profiles of a different xulrunner app, pass the name of the app to it as an argument, e.g., ‘profilemanager thunderbird’. Note: by default, ProfileManager works with Firefox profiles. Myself and the others who have worked on this (principally Jeffrey Hammel and Mark Côté) would love feedback feel free to leave comments or file a bugzilla bug if you find problems.

#Corrupt firefox profile manager download#

You can download a build of the 1.0_beta1 version from.

allows user to launch any profile with any version of Firefox installed on his system, as shown in the graphic below.

ability to manage multiple versions of Firefox, and associate profiles with specific Firefox versions.

#Corrupt firefox profile manager zip#

ability to save/restore profiles to zip archives (which makes it easy to move them between machines).

The profile manager which is built into Firefox is going away after 4.0, so this new app will be the best choice for managing profiles in future Firefox versions, but it works great with 4.0 and earlier versions as well, not to mention Thunderbird. ProfileManager is a standalone app that can be used to manage profiles for Firefox and other xulrunner apps.