import-export-tools-ng
import-export-tools-ng copied to clipboard
thunderbird
Incompatible version
Dear ImportExportTools NG Developers,
I hope this message finds you well.
I am currently using Thunderbird 137 and am attempting to use the ImportExportTools NG add-on. However, I have encountered an issue where the add-on is not compatible with my version of Thunderbird. When I try to install or use it, I receive an error indicating that it is not compatible.
Could you please provide guidance on which version of ImportExportTools NG would be compatible with Thunderbird [version number]? Alternatively, if there are any plans for an update to ensure compatibility with newer versions of Thunderbird, I would appreciate your insights.
Thank you for your assistance, and I look forward to your response.
Same issue here, I'm afraid. Glad to test a beta when available. Thanks again for the work.
I just changed the max version in the manifest file, that way it works with TB137.
@tabascosw After downloading the xpi file for version 14.1.7, where do you find the manifest file?
@SafewayFan @fridok @benlundmaine @tabascosw
I am working on it. I'm testing, there is at least one change needed. @cleidigh
@fridok To edit the manifest file: Rename the .xpi to .zip. Unpack it. Edit manifest.json and change "strict_max_version": "136.*" to "strict_max_version": "137.*" (change it to whatever is the latest TB version). Save change then rename .zip back to .xpi and install the .xpi. Depending on what changes have been made in the new TB version, this workaround may or may not work. If it doesn't work, you will need to wait until Christopher brings out a new compatible version of IETNG. Or you could disable TB updates so the current version of IETNG remains working, then update TB and IETNG when Christopher releases a new compatible version.
@DrStrange Thank you for walking people through the temporary patch process. All Indeed the patch is sufficient to run everything I have tested, though maildir may not work. I am actually pretty positive I can release v14.1.8 for hopefully a quick review this weekend. If all goes well it will actually be set for both v137 & v138.
Please note that IETNG MUST BE REWRITTEN. These RC updates are killing my already slow development based on my disability. Please do not assume I will release for every RC release.
I'm doing my best, but I also have PrintingTools to take care of and am overwhelmed right now
Cheers Christopher
@DrStrange Thank you for walking people through the temporary patch process. All Indeed the patch is sufficient to run everything I have tested, though maildir may not work. I am actually pretty positive I can release v14.1.8 for hopefully a quick review this weekend. If all goes well it will actually be set for both v137 & v138.
Please note that IETNG MUST BE REWRITTEN. These RC updates are killing my already slow development based on my disability. Please do not assume I will release for every RC release.
I'm doing my best, but I also have PrintingTools to take care of and am overwhelmed right now
Cheers Christopher
Christopher, in any way, thanks for doing this work. the tools helped me a lot in the past. and if someone want to use it and you've no time, can go back to 136.x… why Mozilla is braking the APIs every x versions, I don't get it… it is like they won't have a stable userbase for FF and TB…
@toraxmalu Thanks. I actually have v14.1.8 in the review Q and it will support v137 & 138. Hopefully that will buy some time to focus on the rewite. Monthly releases are just killing me. @cleidigh
@toraxmalu Thanks. I actually have v14.1.8 in the review Q and it will support v137 & 138. Hopefully that will buy some time to focus on the rewite. Monthly releases are just killing me. @cleidigh
Is that code monkey work? Or what has to be re-written to base the plug-in on a better code-base?
@toraxmalu The core codebase desperately needs a rewrite which I have not been able to do except for the mbox code. The goal is to make IETNG as much of a modern webextension as possible and the framework more compatible with new Thunderbird architecture. @cleidigh
So question again: is it code monkey work after you laid down the framework and API design or do you have to do all by yourself? i am not very familiar with the internas of thunderbird, but stupid code grinding can do even a "monkey" - hence "code monkey work" ;) cheers
@toraxmalu Well enhancement and maintaining the code will definitely get easier, but I am disabled and slow and unfortunately have no monkeys ;-{ @cleidigh
therefor my quesition… is it possible in any way to support you with the code grinding. you as the brain an a view people with basic programming knowledge filling your frame with code.
@toraxmalu Eventually it will be easier to do pull requests. However, I don't really have the ability to make and manage a team per se. The biggest contribution people can make is testing before releases as that helps reduce errors and my testing. @cleidigh
k, thought we can support you a little bit more, but testing should be in everyone ability.
Thunderbird 139 got installed and now your wonderful extension stopped working again - tried the hack suggested at the top of the thread and Thunderbird didn't like the rezipped/renamed xpi file - said it appeared corrupted. Any suggestions? Hoping there's a solution.
@bobmartin3000 Thanks for the kudos! I released v14.1.9 several days ago with Thunderbird v139 compatibility. I don't know why you would not have had an auto update. What happens when you try to update the addon manually? If that fails, do a search under the addon tab for ImportExportTools NG and you can download from the ATN site.
https://addons.thunderbird.net/en-US/thunderbird/addon/importexporttools-ng/?src=hp-dl-mostpopular @cleidigh
Not sure why it didn't update automatically but I was able to do so manually - thank you.