Install Greasemonkey Scripts In Chrome

How to install user scripts in Chrome There are two methods for installing UserScripts in Chrome. The first is to install the extension, which makes installation simple and easy. The second is to follow these instructions below: Note: As of Chrome 35 (late May 2014), downloaded user scripts cannot be installed using the second method. Please use the extension. • Click on the link to the.user.js file found in the post • Look for the confirmation at the bottom of your browser and click Continue. • Chrome will warn you that you can't install the script. Because Google has disabled the direct installation of extensions that are not downloaded from their Web Store, you'll have to perform a few extra steps before you can use the script.

Now most Greasemonkey scripts work in Chrome. Chrome 4 Supports Greasemonkey Userscripts Without an Extension. When you install a userscript in Chrome.

• The script should have appeared in your downloads bar. • If the file name is modified to.user ().js, rename the file so it ends with.user.js. Note: If file extensions are not displayed on your system, the name has to end with.user. • Open the extensions manager. Go to Menu button >Tools >Extensions to open the extensions manager • Drag drop the file from the downloads bar to the extensions page. If you had renamed it, drag-drop it from your file manager.

• Release the mouse if the text 'Drop to install' appears. • A dialog appears. Click Add to finish the installation. • The script should now be installed. Refresh all tabs affected by the script to start using it. How to install user scripts in Firefox • Install the add-on for Firefox if you haven't done so already • Click on the link to the.user.js file found in the post. • A Greasemonkey Installation dialog will appear.

Review the sites on which this script will work on, view the source of the script if so desired and confirm that you wish to install the script • The script should now be installed. Refresh all tabs affected by the script to start using it.

How to install user scripts in Safari GreaseKit (The hack approach, for Safari 4 and earlier) • – (From the SIMBL website), SIMBL, pronounced like “symbol” or “cymbal” enables hacks. In other words, you can “patch” Mac applications to add functionality to them. To install it, drag the GreaseKit.bundle file to ~/Library/Application Support/SIMBL/Plugins. If you don’t have a SIMBL/Plugins/ folder, just create it, then drop GreaseKit.bundle into it. • Restart Safari, and you will see a new entry in the menu bar for “GreaseKit”. • Click on the link to the.user.js file found in the post to install the userscript. • The script should now be installed.

Refresh all tabs affected by the script to start using it. From NinjaKit (a Safari 5 extension) • Go to the. The page is in Japanese, but don't worry—the install link is in English. • Click on the 'NinjaKit for Safari' link. • If you are prompted to open or save the file, select open.

If the file automatically downloads, find the downloaded file ( NinjaKit.safariextz) and double-click it. • When Safari pops up a message confirming you want to install NinkaKit, click install.

How to install user scripts in Opera 15 and newer versions Install, which makes installation simple and easy. How to install user scripts in Opera 12 and older versions • Create a folder for userscripts.

(eg, C: Program Files Opera Browser Userscripts - it does not need to be within the Program Files folder, anywhere is fine.) • Within Opera, go to Tools >Preferences. • Click the Advanced tab. • Click Content in the choices on the left. • Click JavaScript options.

• For the 'User JavaScript files', click Choose. • Select the userscripts folder created in step 1. And click OK.

• Click on the link to the.user.js file and save it to the userscripts folder created in step 1. • Refresh the tab(s) affected by the script to start using it. From Development resources • - a site to host Greasemonkey scripts.

I've written a about a script of mine which aims to enhance the read later list this page in general. Unfortunately, as I didn't have the notion or muse yet to sign up at userscripts.org, the script is only in text form there in the post. I can see how this would raise the question on how to install it. So how would you install a Greasemonkey script that is only in text form? This little checklist applies to all such scripts (I don't think there are many, I might be the only one because I'm lazy)! I'm also going to assume that your Browser already has the Greasemonkey addon installed. Wouldn't make much sense any other way.

I'm not sure if the following works on Chrome, as I've only tested it on Firefox. Copy the entire script into the clipboard. This includes the header part, it should start with '// ==UserScript==' 2. Create an empty file (A normal text file will do fine) anywhere on your PC, and paste the script from your clipboard into the file and save.

Now we have to rename the file. As we have to change the file extension, you have to disable the Windows Explorer option to hide file extensions!

Name the file after the name of the script, which is found in the header part of the script after the '@name' identifier. Replace every space with underscores.

Then add '.user.js' after the name. For example: If the script has the name 'FiMFiction Enhancer', the file should be 'FiMFiction_Enhancer.user.js', not 'FiMFiction Enhancer.user.js.txt' or any variation! This is the script like you'd download it from userscripts.org.

To finally install it, just open it in Firefox. Right clicking and choosing Open With->Firefox or, in Firefox, clicking File->Open will do just fine. If you've made no mistakes, then Firefox will recognize this as a valid user script and present you with a dialog to install the script.

Click on Install. You can now delete the file that you created if you want, but the script should now be working. That wasn't to hard, was it? Once you know how to, it becomes easy If you want to, and know a little bit about JavaScript or programming in general, you can even modify the script to your liking before you install it!

Neat, isn't it? (You can do that with already installed scripts, too, so this is no advantage.) I hope this cleared some questions! In the future, I might just as well finally register on userscripts.org. Thanks^^ Well, I've never looked into the code of FimFiction enhancements 10 so I can't say for sure.

My guess is that knighty changed the html-code in a way that the userscript no longer recognizes comment boxes on stories, so it won't add the emoticons. The script also broke various other things for me after the site update, so I uninstalled it. I didn't look, but maybe there is a new version on userscripts.org, and the auto-updater doesn't update, for some reason? If that's the case, make a manual update/reinstall and try again. If nothing changes, though, I'd say that FimFiction enhancements are just out of date and maybe even no longer updated. Would make sense, seeing as pictures are hidden automatically now, which makes these emoticons kind of useless in my eyes. They were cool while they worked, though!

I just had the idea for an enhancement script that automatically opens all image boxes that contain smileys, and leaving the others untouched. It would emulate the old behavior, but would only work for those who have the script installed as well, the others would still have to open the image as it is now. Don't count on me writing this, though, I have some private stuff to take care of, first (My Bachelor Thesis, to be specific). I might have a go at it if I'm in the mood and have enough time, but it could be a while.

I just realized that this might be the longest comment I've written yet. Well, give me the right topic.

Sorry, I might not be the best of help, since I haven't been using Greasemonkey for a year now (Some bug was causing my Firefox to crash.) One thing I can think of, though: If the script was opened in a new tab as plain text, then Firefox/Greasemonkey did not recognize it as a Greasemonkey script. Maybe the file extension wasn't right. If you have your file extensions hidden, you might not see that right away. Especially Notepad likes to add a hidden '.txt' file extension. Also make sure the file not only ends with '.js', but with '.user.js'. The header inside the userscript also needs to be intact, without any empty lines in front of it.

It does not hurt to check this even if the file did not open in a new tab.