Which .js file settings take preference in the users profile; prefs.js
or user.js? I ask because we have two distinct users on one machine.
We have had some problems with default browser homepage settings and I'd
like to figure out whether there is some way to change settings in the
individual user.js file to control the individual browser homepage setting.

This may be a separate issue; but one user profile keeps adding new
sequential prefs-#.js files to the profile directory while the other
user profile directory contains only one prefs.js file. It appears that
the new prefs files are added each time the user accesses firefox. I
have deleted the sequential files naming the most recently used prefs to
be THE prefs.js file; but the sequence starts all over again.

I have edited the prefs.js files in both user profiles and tried adding
individual user.js files in the separate user profile directories. I
think that somehow I may have created the conflict and would really like
to get things back to a more tidy condition.

BTW the multiple pref-#.js files don't SEEM to have any detrimental
effect on the actual browser function other than slowing down things.
--

Howard H. Heflin
NOSPAM_HHHeflin@netscape.net
The usual removals are required to reply.

Stop SPAM !!!!

On 2/22/2006 10:38 AM On a whim, Howard Heflin pounded out on the keyboard

> Which .js file settings take preference in the users profile; prefs.js
> or user.js? I ask because we have two distinct users on one machine.
> We have had some problems with default browser homepage settings and I'd
> like to figure out whether there is some way to change settings in the
> individual user.js file to control the individual browser homepage setting.
>
> This may be a separate issue; but one user profile keeps adding new
> sequential prefs-#.js files to the profile directory while the other
> user profile directory contains only one prefs.js file. It appears that
> the new prefs files are added each time the user accesses firefox. I
> have deleted the sequential files naming the most recently used prefs to
> be THE prefs.js file; but the sequence starts all over again.
>
> I have edited the prefs.js files in both user profiles and tried adding
> individual user.js files in the separate user profile directories. I
> think that somehow I may have created the conflict and would really like
> to get things back to a more tidy condition.
>
> BTW the multiple pref-#.js files don't SEEM to have any detrimental
> effect on the actual browser function other than slowing down things.

Hi Howard,

prefs.js is the main config file used. Users should NOT add items to it.
user.js is for users to add prefs. When you add a pref in user.js, it
is imported into prefs.js. Although when you remove a pref from user.js,
it is NOT removed from prefs.js. You have to remove it there also (flaw
IMO).

The multiple prefs.js files has come up before. First check to see if
the original is not marked as Read-Only (right-click the file in
Explorer and select Properties). FF should ALWAYS be closed before
editing files.



--
Terry

On 2/22/2006 11:16 AM, Terry wrote:
> On 2/22/2006 10:38 AM On a whim, Howard Heflin pounded out on the keyboard
>
>> Which .js file settings take preference in the users profile; prefs.js
>> or user.js? I ask because we have two distinct users on one machine.
>> We have had some problems with default browser homepage settings and I'd
>> like to figure out whether there is some way to change settings in the
>> individual user.js file to control the individual browser homepage setting.
>>
>> This may be a separate issue; but one user profile keeps adding new
>> sequential prefs-#.js files to the profile directory while the other
>> user profile directory contains only one prefs.js file. It appears that
>> the new prefs files are added each time the user accesses firefox. I
>> have deleted the sequential files naming the most recently used prefs to
>> be THE prefs.js file; but the sequence starts all over again.
>>
>> I have edited the prefs.js files in both user profiles and tried adding
>> individual user.js files in the separate user profile directories. I
>> think that somehow I may have created the conflict and would really like
>> to get things back to a more tidy condition.
>>
>> BTW the multiple pref-#.js files don't SEEM to have any detrimental
>> effect on the actual browser function other than slowing down things.
>
> Hi Howard,
>
> prefs.js is the main config file used. Users should NOT add items to it.
> user.js is for users to add prefs. When you add a pref in user.js, it
> is imported into prefs.js. Although when you remove a pref from user.js,
> it is NOT removed from prefs.js. You have to remove it there also (flaw
> IMO).
>
> The multiple prefs.js files has come up before. First check to see if
> the original is not marked as Read-Only (right-click the file in
> Explorer and select Properties). FF should ALWAYS be closed before
> editing files.
>
Look in the active pprofile directory (the one with the pref-n files)
If there is a file with the extension .moztmp - delete it/them.

as Terry said "FF should ALWAYS be closed before
editing files."

regards:captjlddavis