You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0.1 Waterfox/56.0.1
Problem:
On Waterfox Portable in Windows, changing the path will cause extensions to break (tested with Classic Theme Restorer and Greasemonkey) .
Solution:
The problem lies with addonStartup.json.lz4 that specifies the full path (not relative!) to the extension. Manually changing the path contained in it will allow it to start as normal, but not done easily due to proprietary MozLz4 format. (See Issue Request: Remove Lz4 compression (.json.mozlz4, bookmarks, etc.) #330 . The WaterfoxPortable.exe NSIS script can change this if it was plain text.)
Changing the paths in extensions.json will only take effect after Waterfox is started twice. First start will be "broken" because of invalid path in addonStartup.json.lz4 (some addon settings like toolbar placement in CTR will be lost), but it will generate a newaddonStartup.json.lz4 for the next run.
The text was updated successfully, but these errors were encountered:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0.1 Waterfox/56.0.1
Problem:
On Waterfox Portable in Windows, changing the path will cause extensions to break (tested with Classic Theme Restorer and Greasemonkey) .
Solution:
The problem lies with addonStartup.json.lz4 that specifies the full path (not relative!) to the extension. Manually changing the path contained in it will allow it to start as normal, but not done easily due to proprietary MozLz4 format. (See Issue Request: Remove Lz4 compression (.json.mozlz4, bookmarks, etc.) #330 . The WaterfoxPortable.exe NSIS script can change this if it was plain text.)
Changing the paths in extensions.json will only take effect after Waterfox is started twice. First start will be "broken" because of invalid path in addonStartup.json.lz4 (some addon settings like toolbar placement in CTR will be lost), but it will generate a newaddonStartup.json.lz4 for the next run.
The text was updated successfully, but these errors were encountered: