Troubleshooting

After a Firefox update, some functions might stop working. This is unavoidable until autoupdates are implemented, so this guide shall help you troubleshoot the most common problems that might arise during the installation of any of the javascript files inside any of the folders inside Multirow and other functions.

I installed x function through the patcher and it doesn't work

It could becaused by a few things:

Some distributions of Linux (like Ubuntu Mate) sometimes add extra configuration files to Firefox to change their home page or change other settings. Since the patcher uses the same method to override some configuration settings to apply the custom functions, having more than 1 config file trying to overwrite the "global configuration" setting will prevent the functions from being loaded.

The patcher will tell you if it found a non-standard configuration file and prompt you to remove it. If you didn't remove it because you added specific configurations, you will have to merge the changes on a single file inside the defaults/pref path in Firefox root folder.

For example, on Ubuntu Mate, the path you'd have to check would be:

/usr/lib/firefox/browser/defaults/pref

The only files that should be there would be channel-prefs.js and config-prefs.js after patching.

Other reasons might be that a Firefox update broke the function you installed, in which case you'd have to check the following section.

Some function stopped working after the lastest Firefox update

Mozilla tends to change selectors every few releases, so what might work in certain release might stop working in the next 2 releases.

If some function stopped working, use the newest patcher available to re-patch the outdated files to the new version (an updated version might take a few days to appear for Nightly after a new release).

If you aren't using the patcher (or if you are using Mac and it isn't available), and need to patch manually, make sure to choose the most up-to-date files you need from the master branch. Sometimes when selecting one release you might get redirected to the tag branch of that release (which will probably be outdated, since it's the start release of a new Firefox version), so make sure you are on the master branch.

Follow the explanations inside the JS Loader folder to patch manually, making sure that you got the folder locations correctly.

I copied one of the .as.css files from the CSS Tweaks folder to my chrome folder and I don't see any change

By default you can use them copying their code to your userChrome.css. If you want to use any of these files as standalones, you can do so after patching your firefox with the patcher, or following the method explained in JS Loader folder.

I am unsure if the files are being loaded at all

If you placed all the files on both the root and chrome folders correctly, the *.uc.js and *.as.css files inside your chrome folder should be getting read, but sometimes it's hard to know for sure if they actually are at all.

For those cases you can use the test file. Save it as test.as.css and place it in your chrome folder.

If you see red borders around every element next time you start Firefox, both javascript and elevated CSS files are being read correctly.

I used the patcher, all paths were correct, there weren't extra config files on the root folder, the patch was applied correctly, the files are loaded, but it still doesn't work

If after checking all the previous steps it still doesn't work, open a new issue and give as much details as you can to help debug the problem.