Addon not working on Thunderbird 60

Hi,
I read a few comments today, that the addon is not working on new thunderbird version 60.
Is there a chance to get it working?

Sure is there a chance but just take a look on the folders timestamps https://github.com/nextcloud/nextcloud-filelink. Last release on 29 Sep 2017

It seems like development has nearly stopped. My bugreports and problems that other users have are does not care anyone. Only the “Issues”-tab is active. Maybe the demand for this addon isn’t high enough so that noone will continue developing and invest time into the addon :disappointed_relieved:
With the right marketing and a roadmap (or another kind of plan), users could see that there is a addon in the empty, new Thunderbird-60-store which could be useful and is maintenanced -> raising of demand.

So what’s needed to solve your problem is either raising demand so that nextcloud developers will continue development or a guy who needs the addon and can write XUL/JavaScript.

Now to your Question specific to Thunderbird 60:
Thunderbird is going to rebuild it’s API-systems like in Firefox 60 (Quantum). This means that every addon has to be rewritten on the new WebExtensions model, otherwise it’ll not work. For Firefox the Mozilla Foundation published a manual how to port legacy addons to the new system, maybe they’ll do it again for Thunderbird.
So the solution is to merge the pull request Compatibility with thunderbird-60, fixes #55 #59

I hope that Nextcloud will help with “demand improvement” for filelink (and finally merge this pull request) @jospoortvliet

Edit: After reading another article and taking a look into the mozilla wiki, WebExtensions support will come with TB63, but other Quantum technologies will be implemented in TB60.

Thunderbird is going to rebuild it’s API-systems like in Firefox 60 (Quantum). This means that every addon has to be rewritten on the new WebExtensions model, otherwise it’ll not work.

Thunderbird 60 does not require WebExtensions, and not every add-on must be rewritten. Some only require minimal or no changes. Some are just initialization changes, some language changes, some API changes.

I reference to this thread: Any chance to get this plugin under develpment again?
Development continued trough an bounty. The Process is described there.

Just to clear the list of open questions please mark this thread as solved (mark any answer as solution)