Pentadactyl not working on Palemoon 32/FreeBSD

[PaleLuc]

I have an old version of Palemoon on Linux and version 32 on FreeBSD, the port provided by DBSoft.
I installed FreeBSD just a few days ago.

I copied my Linux Palemoon profile to FreeBSD and everything worked, including Pentadactyl. No problem at all.

However, when I close Palemoon and launch it again, Pentadactyl is no longer working. In the Extensions section, Pentadactyl is disabled with a warning that "Pentadactyl is not compatible with Palemoon 32."

Except that it is. The way to restore it is to import my old profile again. Then it works perfectly until the browser is closed. If it works, it's not incompatible. Something is killing it for some reason.

Please advise. If Pentadactyl is dropped, I will never update my browser again.

[moonbat]

Edit the extension's install.rdf and update the maxVersion to 32.*. You'll find plenty of threads here with detailed instructions on how to do so.

[PaleLuc]

I edited it and tried to load it. Palemoon says, "This add-on could not be installed because it appears to be corrupt."

[moonbat]

You fucked up the directory structure while re-zipping it. When you view the .xpi file in any zip viewer, all the files must be at the top level without including the enclosing directory. SO if you extracted everything to pendactyl/, then when you open the XPI in your zip application, you should NOT see the pentadactyl/ directory, but rather its immediate contents. install.rdf and everything at that level must be at the top.

[PaleLuc]

It worked. Thank you.

Whew!

[fatboy]

Sorry, don't wanna necrobump this thread, but I am trying to using pendactyl on palemoon on linux, but I see the extension only supports up to version 29?
Will this be fixed sometime?

[moonbat]

Will this be fixed sometime?

By whom? Who are you expecting to fix this? Did you even see the previous few comments about manually updating the last compatible version?

[FranklinDM]

Will this be fixed sometime?

There's already a PR at that extension's repository which should fix this issue, but the developer doesn't seem to be active for over a year now.

[fatboy]

There's already a PR at that extension's repository which should fix this issue, but the developer doesn't seem to be active for over a year now.

Thanks FranklinDM, appreciate the feedback

[Moonchild]

Since it's MIT licensed, nobody is stopping you from forking the repo and publishing an updated version either.