HTML list description removed when saved

I am running a J!4.4.1 website with AcyMailing Starter 5.13.0 configured to use its own "AcyMailing Editor". The default editor of my website is JCE 2.9.57 configured not to check or filter HTML code for super users. JCE works as intended for all articles of my website (the content is correctly formatted).

This is different when I want to enter a formatted description of a list. This did work as intended, when I created the first lists some years ago. In the meantime, I have migrated from J!3 to J!4, from PHP7 to PHP8.1 and from AcyMailing Starter 5.9.6 to 5.13.0. Now, I wanted to add a new list with a HTML formatted description of exactly the same style as the the other old lists (a simple paragraph with one italic sentence). I can specify the desired formating in the AcyMailing Editor and it is correctly displayed as long as I do not click on "Apply" or "Save" of the corresponding AcyMailing dialog. However, as soon as I click on either button, the HTML formating is completely removed.

In order to find the root cause, I have configured AcyMailing to use other editors (JCE, TinyMCE), but without any effect on the formating of the final description. While both editors work as expected and display the formatted contents correctly, the HTML formating is again removed as soon as I click on the "Apply" or "Save" of the corresponding AcyMailing dialog.

I have also verified the Global "Configuration > Text Filters > Super Users". It is configured as intended for "No Filtering". And I have verified that I did login as a super user .

Do you have an idea what causes this unexpected behavior and let me know how to fix it?

Thanks & Regards
Hans

[unknown]
Thanks for your explanation. However, I have the problem to add a bilingual description to each list. Without any format support it is not very intuitive for the reader to distinguish the description in language A from the description in language B. Of course, I could use a character to separate both languages e.g.

<description A> / <description B>

however, since I cannot even use a line break, the user has to read and interpret the entire contents. With format support, it is much easier, e.g.

<description A>
<description B>

Finally, I am well aware that Acyba provides powerful products and deserves to be paid for theses products and their service. However, actually I do not need all those nice features that are certainly important for commercial sites. All I need is a GDPR-compliant tool to register and self-administer users. I even do not send mails to mailing lists with AcyMailing. So, it does not pay off for me to purchase an Essential or Enterprise license. However, since I still benefit from your work, I try to be nice and point out bugs or missing features so that your developers can improve your products and make them even more attractive for your customers.

Well, if the HTML code removal is deliberately introduced, it does not make much sense to propose a modification. At least I have found a way, to bypass the removal by directly editing the corresponding entry in the database.

jvstratum
Thanks for your explanation. However, I have the problem to add a bilingual description to each list. Without any format support it is not very intuitive for the reader to distinguish the description in language A from the description in language B. Of course, I could use a character to separate both languages e.g.

<description A> / <description B>

however, since I cannot even use a line break, the user has to read and interpret the entire contents. With format support, it is much easier, e.g.

<description A>
<description B>

Finally, I am well aware that Acyba provides powerful products and deserves to be paid for theses products and their service. However, actually I do not need all those nice features that are certainly important for commercial sites. All I need is a GDPR-compliant tool to register and self-administer users. I even do not send mails to mailing lists with AcyMailing. So, it does not pay off for me to purchase an Essential or Enterprise license. However, since I still benefit from your work, I try to be nice and point out bugs or missing features so that your developers can improve your products and make them even more attractive for your customers.

Well, if the HTML code removal is deliberately introduced, it does not make much sense to propose a modification. At least I have found a way, to bypass the removal by directly editing the corresponding entry in the database.