Version 2.0.0 of the FireFox LongURL Mobile Expander has caused it to quit working in FF3.0.11.

This problem persists in Firefox 3.5 too.

Same here. Not working in FireFox 3.5 either.

I'm using the Long URL Please plug-in for now. http://www.longurlplease.com/

I've also tried the bit.ly plug-in but it seems to conflict with https sites.

LongURL Mobile Expander 1.0.1 worked fine with Firefox 3.0.11 on both of my computers.

On both computers I made the mistake of installing LongURL Mobile Expander 2.0.0, and this new version of the add-on isn't working at all. One computer is still running Firefox 3.0.11 and the other is running Firefox 3.5, and neither works with the new version of the LongURL add-on.

On the computer with Firefox 3.0.11, I uninstalled LongURL 2.0.0 and then reinstalled 1.0.1 (https://addons.mozilla.org/en-US/firefox/downloads/file/36368/longurl_mobile_expander-1.0.1-fx.xpi) and now it works again.

I also followed the same procedure with Firefox 3.5 (except that I had to click on the "Force Install" button in order to install 1.0.1 since it's only supposed to be compatible with up to Firefox 3.0.*) and now it also works.

Please fix and re-release the new version!

Additional details that may help the developer track down the problem:

* In addition to LongURL Mobile Expander, both computers also have NoScript 1.9.5, Adblock Plus 1.0.2, and User Agent Switcher 0.7.2 installed. For what it's worth, I tried adding longurl.org to the permanent whiteliste in NoScript (which I never had to do before, but I figured it would be worth a shot), but that didn't fix the problem.

* Both of my computers are Intel-based Macs (I highly doubt that this has anything to do with the LongURL bug, though).

To the developer: If you need further information about this bug, feel free to follow me back on Twitter so I can DM you. http://twitter.com/theJoshMeister

I got it working after seeing a comment here: https://addons.mozilla.org/en-US/fire...

Edit the C:\Documents and Settings\(user)\Application Data\Mozilla\Firefox\Profiles\(your profile)\extensions\{a7101e54-830c-4d33-a3ed-bedc17ec44da}\content\longurlmobileexpander.js

I am using Windows XP so your location might different.

Around line 79, change

var current_domain = document.location.href.match(/^https?:\/\/(?:www\.)?([^\.]+\.[^\/]+)/i);


To:

var current_domain = document.location.href.match(/^https?:\/\/(?:www\.)?([^\.]+(\.[^\/]+)?)/i);


After doing this and re-enabling the extension.. it started working. I can now see the tooltip popups and it's supposed to fix the current_domain is null problem.

The fix to the regexp is not enough. You'll get the error if you open a URL whose scheme isn't http or https. I recommend modifying line 89 by adding:
(current_domain != null)
as the first test in the if statement.

The only change needed to make it work in Firefox 3.5 is Steve's fix but you have to make line 89 read:


if ((current_domain != null) && (domain !== current_domain[1]) && (typeof(this.known_services[domain]) !== 'undefined')) {


Note the double opening paren has been moved to just after the if, and the && has been added after Steve's patch.

Now no more complaints about the current_domain is a null. Thanks, Steve!

Neither Steve's nor w8sdz's fixes worked for me. Version 2.0.0 is completely broken. I still have to downgrade to 1.0.1 to make this add-on work again.

I made a video tutorial showing how to modify the maxVersion string in the 1.0.1 add-on so Firefox won't nag you or force you to reinstall it every time a new Firefox update comes out:

http://www.youtube.com/watch?v=IEuI5v...

The tutorial is designed for Mac users, but it should be easy enough to adapt the instructions for Windows or Linux. Basically, you just need to trick the old 1.0.1 add-on into thinking it was designed for Firefox 3.5 or later, and it will work again.

I really want the features that were supposed to be in 2.0.0, so I hope the author of this add-on releases a working version soon.

Sean, 13 days ago you uploaded a new version of the extension to the Firefox Add-ons site. It stil had not replaced the old version. Do you know what is causing this long delay in getting it approved?