Crash of importexporttools_ng-14.1.8-tb - when exporting a folder in html-format with index and attachments

[kramar-1471]

Dear programmer of this extremely useful tool,

I hope my English is good enough to explain my problem.

I've only recently started using your tool. I need to export over 1,000 emails from individual subfolders in TB to make them accessible in a structured format for further use with other applications.

I would have preferred it if it were possible to generate the emails as PDF files with hyperlinks to the attachments. Since that unfortunately didn't work, I wanted to see if I could continue working with HTML files. To be able to work quickly with the index file for this variant, I wanted to try changing the date format of the index file and, if possible, the order of the columns in the index file. I wanted the date to appear at the very beginning of the index file.

While experimenting with the settings, including the advanced settings "importexporttoolsng.export.xxx," the app now crashes when I try to export the folder I've been using for experiments. I'm actually sure that exporting as HTML with index and attachments worked with this folder before my attempts.

The most difficult thing was probably my intervention in "extensions.importexporttoolsng.export.index_date_custom_format" Since your help file listed the variable ${subject} as a possible input here in addition to the date formats (but that was probably an oversight on your part), I've now also specified this variable in the field "extensions.importexporttoolsng.export.index_date_custom_format"

My questions to you:

1.) Is it possible that my experiments during export also corrupted the existing data or the structure of the data in TB? Or can this hopefully be ruled out as a source of the error?
I've uninstalled and reinstalled the app, but the error persists. My default settings were also applied when I reinstalled it, as my settings are probably stored in the Windows Registry. However, the emails are displayed correctly in Thunderbird.

The error message is:

_[Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIFileOutputStream.init]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://mboximport/content/mboximport/exportTools.js :: IETwriteDataOnDiskWithCharset :: line 2332" data: no]

Exporting: Folder: WEG_Versammlg_Dez_2021
Msg: 1110 Wien, Rinnböckstraße 23 - Einladung zur Eigentümerversammlung am 01.12.2021 in unseren Kanzleiräumlichkeiten in 1180 Wien, Semperstraße 60/12

IETwriteDataOnDiskWithCharset@chrome://mboximport/content/mboximport/exportTools.js:2332:12
onAfterStopRequest@chrome://mboximport/content/mboximport/exportTools.js:1979:37
exportAsHtml/result</onStopRequest/<@chrome://mboximport/content/mboximport/exportTools.js:1699:23_

2.) Would it be possible to export emails as PDFs that include hyperlinks to the attachments or something similar?

3.) Would it be possible to format the index file as well?

Please excuse my lengthy explanation. Thank you for your work and I would be very happy to receive a reply.

Best regards,
Martin

[kramar-1471]

Dear Christopher,

I'm still trying it out, but perhaps my error message has something to do with the email titles being too long and not with my other settings. I had increased the email title limit to 150 characters.

I've now received an error message in another context, which I was able to resolve by reducing the character length.
I'll give you more feedback on whether reducing the character length resolves the previous problems.

The only remaining question is the one from before regarding linked PDF attachments and
the ability to format the index table.

Thanks for now,
Martin

[cleidigh]

@kramar-1471
I do have a bug with very long filenames with attachments added also.

I'm not sure why you mention the preferences, these should not be edited directly.

The custom date format has nothing to do with the subject so I'm not clear about that comment.

The index order cannot be changed, that is something I will be doing in my rewrite of the export code.
@cleidigh