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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

My theme won't stay enabled

  • 17 antwoorde
  • 2 hierdie probleem
  • 1 view
  • Laaste antwoord deur rlnoonan

more options

Since the update to version 66, my themes won't stay enabled, no matter which one I choose. I've tried uninstalling and reinstalling the themes, (restarting firefox in between), redownloading and installing firefox itself...all to no avail. It reverts to the default theme when it finishes loading, no matter what I do. I can re-enable it manually...and, here's the odd part, it shows while firefox is loading! Anytime firefox is started, this happens, and it doesn't seem to matter what them I select. When I close firefox, it disables itself.

Since the update to version 66, my themes won't stay enabled, no matter which one I choose. I've tried uninstalling and reinstalling the themes, (restarting firefox in between), redownloading and installing firefox itself...all to no avail. It reverts to the default theme when it finishes loading, no matter what I do. I can re-enable it manually...and, here's the odd part, it shows while firefox is loading! Anytime firefox is started, this happens, and it doesn't seem to matter what them I select. When I close firefox, it disables itself.
Aangehegde skermkiekies

Gekose oplossing

Note that the Weave folder is part of Sync (Sync was formerly name Weave), so it is possible that Sync was interfering.

Lees dié antwoord in konteks 👍 0

All Replies (17)

more options

Are you logged in as the Admin/Owner?

more options

This can happen if there is a problem with the extensions.json file or the prefs.js file in the profile folder.

Do you have cleanup software that might affect files in the hiden profile folder?

Location used for the main profile that keeps your personal data in "AppData\Roaming" (Root Directory on about:profiles).

  • C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\Profiles\<profile>\

There is software like Advanced SystemCare with its Surfing Protection feature that can protect files in the Firefox profile folder against changes. If you have such software then check the settings or uninstall this software.

more options

WestEnd said

Are you logged in as the Admin/Owner?

Yes.

more options

Where you download that theme from? Mine doesn't show those?

more options

The currently selected theme is stored as the first theme in this pref that you can find on the about:config page.

  • lightweightThemes.selectedThemeID = 1
  • lightweightThemes.usedThemes = {JSON data}

If you do not keep the value of this pref then Firefox will fallback to the default theme.

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

more options

cor-el said

The currently selected theme is stored as the first theme in this pref that you can find on the about:config page.
  • lightweightThemes.selectedThemeID = 1
  • lightweightThemes.usedThemes = {JSON data}
If you do not keep the value of this pref then Firefox will fallback to the default theme. You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

The place where you have {JSON data} is just a pair of square brackets. I'm betting that's where the boggle is....Now, I just need to know what to put there!

more options

I am having the exact same problem. I also have the square bracket problem. My prefs are:

   lightweightThemes.selectedThemeID = <blank>
   lightweightThemes.usedThemes = []

Is the value 1 required for selectedThemeID? How can we figure out what to put in for the JSON data?

more options

This means that not themes are installed and selected because otherwise selectedThemeID and usedThemes would have a not-blank value.

  • lightweightThemes.selectedThemeID = <blank>
  • lightweightThemes.usedThemes = []

JSON data uses curly brackets with key:name pairs ({"key":"value"}) for its data. The enclosing square brackets are required because this pref can be an array of comma separated lightweight themes: [{<theme-1>},{<theme-2>}].

You can install and enable a theme to see what this JSON data looks like.

[{"id":"1","name":"Unknown","headerURL":"https://addons.cdn.mozilla.net/","footerURL":"https://addons.cdn.mozilla.net/","textcolor":"#","accentcolor":"#","iconURL":"","previewURL":"","author":"Unknown","updateURL":"","version":"1.0","updateDate":"","installDate":""}]

more options

That actually helped me find the dratted prefs.JSON file. It was in the "Weave" folder, in the subfolder "Failed." From that, I took a wild guess that something went wrong with it between the last two updates. I copied my bookmarks backup folder out to the desktop, just in casepulled a reinstall and ran the firefox refresh twice, till it showed only the default theme (It had been flashing mine up for the few moments before firefox was fully started, only to have it vanish as soon as it had.) and then reinstalled my themes from their pages.

All seems to be working fine at the moment. Selected my theme, closed firefox, wated a few, then reopened it, and my theme was still there!

more options

Gekose oplossing

Note that the Weave folder is part of Sync (Sync was formerly name Weave), so it is possible that Sync was interfering.

more options

cor-el said

Note that the Weave folder is part of Sync (Sync was formerly name Weave), so it is possible that Sync was interfering.

So, for others having this issue, just deleting the weave folder might work?

more options

I wouldn't know whether deleting this folder helps, this folder merely stores data that is used by Sync. It is possible that for some reason there is some sticky Sync data stored in the folder and syncing preferences is enabled. Themes are part of Sync:

  • about:config ->
    services.sync.prefs.sync.lightweightThemes.usedThemes = true
    services.sync.prefs.sync.lightweightThemes.selectedThemeID
more options

cor-el said

This means that not themes are installed and selected because otherwise selectedThemeID and usedThemes would have a not-blank value.
  • lightweightThemes.selectedThemeID = <blank>
  • lightweightThemes.usedThemes = []

This is strange. I have a total of 13 additional themes installed (beyond the "default", "light", and "dark"), including three that are animated. I currently have selected a theme called "Galaxy Green" that I downloaded from addons.mozilla.org (where I got all of my themes from). Yet I just checked my prefs and it is still showing these blank values. This is after my theme stayed put for the entire weekend.

I'm using this same theme on two separate machines (sync'ed) and they both show the same blank values. Could there be some kind of sync issue? Note, I found my prefs.json file in the same place mentioned by meowwl (in Weave), but it seems to be empty. The only thing in there is: {"ids":[]}

Maybe I should try removing and then re-installing the theme to see if the prefs are fixed.

more options

I wanted to post a quick update: I unchecked "Add-ons" in the account sync options and the problem seems to have gone away. I've had "Green Galaxy" working on machine one and "Animated Matrix" working on machine two for well over a day now. Not ideal, since it doesn't allow me to keep my extensions in sync, but since I have most things set up how I like them, I can just re-check when I make changes to the extensions.

A further note: using a suggestion from another thread I also set the two preferences mentioned above to "false":

   lightweightThemes.selectedThemeID = false
   lightweightThemes.usedThemes = false
more options

You can set the two Sync lightweight theme prefs to false to prevent the themes from getting synced.

  • services.sync.prefs.sync.lightweightThemes.selectedThemeID = false
  • services.sync.prefs.sync.lightweightThemes.usedThemes = false

That way you should be able to sync other add-ons.

The various services.sync.prefs.sync.* prefs set what prefs to include in syncing preferences.

more options

Great option. I'll try it and report back. Thanks.

more options

Unfortunately, setting those items to false did not seem to work. Both machine's themes disabled a short time later. So for now, I'm back to unchecking "Add-ons" in the sync options. That has continued to work for me.