Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Can I move local-settings.js to omni.ja ?

  • 7 replies
  • 2 have this problem
  • 5 views
  • Last reply by cor-el

more options

Hi, all!

I managed to adapt & lock FF12 preferences/settings via a an obscured mozilla.cfg-file successfully, my question is, can I move the local-settings.js to the omni.ja file to hide it from users ? I tried to include it there, but all prefs in mozilla.cfg are ignored when there is no local-settings.js in directory defaults\pref\.

I know I can protect the .js file via the Windows rights management from being deleted or overwritten, but it would be more elegant to hide it right from the start, please help ?

Thx-in-advance, T.

Hi, all! I managed to adapt & lock FF12 preferences/settings via a an obscured mozilla.cfg-file successfully, my question is, can I move the local-settings.js to the omni.ja file to hide it from users ? I tried to include it there, but all prefs in mozilla.cfg are ignored when there is no local-settings.js in directory defaults\pref\. I know I can protect the .js file via the Windows rights management from being deleted or overwritten, but it would be more elegant to hide it right from the start, please help ? Thx-in-advance, T.

Chosen solution

hello, i've tested it and it works for me when i put the local-settings.js into the omnia.ja file inside the /defaults/preferences path with 7-zip.

Read this answer in context 👍 0

All Replies (7)

more options

Chosen Solution

hello, i've tested it and it works for me when i put the local-settings.js into the omnia.ja file inside the /defaults/preferences path with 7-zip.

more options

Hello,

Modifying installation files like omni.ja causes partial updates to fail. The file is also overwritten when Firefox is updated — every six weeks on average — and the changes must then be redone.

more options

you're right, it's a not very practicable solution!

more options

Now using 7-Zip instead of the often recommended onboard ZIP-mechanism of Windows 7 all works fine now. Thank you!!!

Practicability may be a point, yes, but due to special print layout settings automatic updates are a no-go in our environment (those settings often get lost/are overwritten by the default setup), so that casts no problem on our side.

Thx-a-lot, T.

more options

Yeah, I know you've warned me before, but after updating to FF V13.0.1 I cannot even use the original omni.ja file unzipped and then zipped again (without adding my custom local-settings.js to the defaults/pref-directory!!!) using 7-Zip, FF keeps crashing at the start until I replace it with the original omni.ja-File of version 13.0.1.

Is FF V13 using a new format of optimized jar-files which is new to 7-Zip (it can unpack it at least, the resulting omni-dir looks ok) or am I missing something ?

Thx-a-lot in advance, T.

more options

Works for me, with 7-Zip 9.20. I tried unpacking omni.ja, adding a small text file, then repacking.

Make sure you're compressing the contents of the folder where you extracted omni.ja, and not the folder itself. Your settings should be

  • ZIP archive format.
  • Normal compression level.
  • Deflate compression method.
more options

Note that you can still browse the omni.ja archive in Firefox via the resource:/// protocol.

Get the raw optimizejars.py file via the link on this page:

optimizejars.py --deoptimize ./ ./ ./
optimizejars.py --optimize ./ ./ ./