I just updated Tumblr Savior v0.3.16 with new “safer” code. Google has decided to force everyone to use manifest_version 2 by the beginning of November. For extension developers, this means Google has decided you can’t use convenient inline script like onclick and onload. Google is also outlawing eval. Additionally, you’ll get to run into purposely undocumented changes to the Chrome Extension API and useless debug messages to help you figure out where the problem is.
To save you the trouble of trying to figure out what’s going on, all instances of sendRequest and onRequest need to be replaced with sendMessage and onMessage. That’s what you need to do when you see the error message: “Port error: Could not establish connection. Receiving end does not exist.” Yes, Chrome won’t point out the line in your code that has the problem. And no, there is no documentation indicating that this is what you need to do.
As always you can find Tumblr Savior at these locations: