I read this page:
http://www.alain.knaff.lu/howto/MozillaCustomization/

and found the headline 'Putting into place locked configuration settings'

There are a description, how to use an additional file, to lock or set default prefs.

I tried it in k-meleon, but it does not work, IMHO.

Should it work?

Just create a user.js file with all the prefs you don't want changed.

jsnj,

> Just create a user.js file with all the prefs you don't want changed.

I already have it. In our network, every user has a user.js. But I'd like to have a network.js, because it would be useful, to set (and change) some prefs with primacy, for example proxy-settings and so on.

Robert:

"Just create a user.js file with all the prefs you don't want changed."


Shelumi`El
Jordan

S.D.G

MonkeeSage,

I already have a user.js with all the prefs, and every user in our network has it too. But it is not really a user.js, because it is read-only. The file includes all the prefs, which may not changed by the users.

This is the reason for my question in my first posting.

I have no idea what you mean. Any K-Meleon pref can be placed into User.js and it will override the pref if it is set anywhere else.


Shelumi`El
Jordan

S.D.G

MonkeeSage,

> I have no idea what you mean. Any K-Meleon pref can be placed
> into User.js and it will override the pref if it is set anywhere else.

That's right, but it's not my problem: I talk about a network-installation of k-meleon. The program-folder is at the server, the profile-folders of each user are in the home-directory at the server too. Every user has a user.js in his profile-folder, but the tile is read-only, because it includes prefs, which may not changed by the user. The result is, the users cannot use the user.js, because they have no write-acces at it.

An additional file, with primacy before user.js and prefs.js could include all prefs, which may not changed by the users. It would be useful, because I could give the users full acces at user.js.