Using master, 0.11.0-DEV, on mantisbt 2.27.1 (and previous versions), on some rare e-mails on import we get a
APPLICATION ERROR #11: A necessary field "Body" was empty. Please recheck your inputs.
Unfortunatly, the mail -is- imported into mantis, but due to the error the delete is not done on the message in the imap folder, resulting in a continuous import of the same message on every cronrun
The mail itself is not big, raw 44K and I'm mildly convinced that the plugin is working as-intended, in regards to the behaviour of not deleting the message, but apparantly it can construct something that is half-way accepted by mantisbt
consistent Applicaton Error #11 on some e-mails
Moderators: Developer, Contributor
Re: consistent Applicaton Error #11 on some e-mails
What value is in this configuration option: https://mantisbt.org/wiki/doku.php/mant ... escription.
Please enable debug mode in EmailReporting.
Make sure that the directory is writable so that EmailReporting can save the email contents.
If the issue occurs, please share the raw email by direct message.
Please enable debug mode in EmailReporting.
Make sure that the directory is writable so that EmailReporting can save the email contents.
If the issue occurs, please share the raw email by direct message.
Re: consistent Applicaton Error #11 on some e-mails
Thanks for the reply,
with debug mode enabled, and a different string in mail_nodescription there was no change.
However, I now also see that whenever I do a manual (GUI) added addition on this issue, that it also yields the error #11
As such, I'll have to find in mantisbt itself, thanks for the effort.
with debug mode enabled, and a different string in mail_nodescription there was no change.
However, I now also see that whenever I do a manual (GUI) added addition on this issue, that it also yields the error #11
As such, I'll have to find in mantisbt itself, thanks for the effort.
Re: consistent Applicaton Error #11 on some e-mails
I suggest checking the other plugins that are active.
But good to hear that it's likely not EmailReporting thats the cause.
If that changes please let us know here.
But good to hear that it's likely not EmailReporting thats the cause.
If that changes please let us know here.