Editing configuration/Troubleshooting

up to Editing configuration

If you make changes to a configuration file but the changes seem to have no effect, here are some common causes that you can check:

• You edited the wrong file, or created the file in the wrong place.

Check that you found the profile that is actually being used by the application, not some other profile, and not the application's installation directory.

If you are editing userChrome.css or userContent.css, check that you are saving files in the chrome folder in the profile, and not in the profile directory itself.

• The file contains errors.

If you found the preference settings or CSS rules or on a web page, copy and paste from the web page to avoid typing errors.

If you have to edit the content, ensure that you preserve the correct punctuation.

Check that the font in your text editor makes it easy for you to see the difference between parentheses (), square brackets [] and curly braces {}, and between colon : and semicolon ;.

In the application, choose Tools – JavaScript Console... (or Tools – Web Development – JavaScript Console...) to see error messages.

Note:  The JavaScript console does not always show errors relating to preference settings.. In recent versions of some Mozilla applications, it does show CSS errors.

• CSS rules are being overridden by other rules.

Try adding !important to any CSS rule that has no effect. Add it just before the semicolon at the end of the rule.

If you are using a theme that you installed, try the CSS rules with the application's default theme.

See Also

• Editing configuration/Manual editing