Programatically changing taxonomy description always resets text format to "Full HTML"

Here is a patch to fix the issue.

The Needs Review Queue Bot → tested this issue.

While you are making the above changes, we recommend that you convert this patch to a merge request → . Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)

Thanks for working on this. As this is bug, I think we would need to add a tests (according to the Steps to reproduce). Adding a tag.

Please use only one MR for further work.

zniki.ru → made their first commit to this issue’s fork.

Thanks for great issue summary.
I really enjoy the idea to be able to use array as argument for setDescription.
I created test case.

zniki.ru → changed the visibility of the branch 11.x to hidden.

MR failure was a random javascript one,

Before marking this one can we figure out why setDescription is overriding the text format? Want to make sure we aren't masking a larger issue.

Term description field is "text_long" type.
And for that type properties value, summary, format are supported.
Implementation of function setDescription just ignores other properties.
I think functions setDescription, getDescription, getFormat, setFormat can be removed in future, because in Node entity there are no such methods.

But then why do no other entities have this problem or do they?

Should be documented in issue summary why taxonomy is unique.

Also MR needs to be updated to 11.x as the current development branch.

I believe it came from D7 taxonomy module, then description was convert to text field, I find issues about it:

• #2016701: Expand TermInterface to provide methods →
• #569434: Remove taxonomy term description field; provide description field for forum taxonomy →

And part of last issue is to remove these methods.

I convert changes to 11.x and create new MR 5880

I tested the modifications locally, and in both scenarios, the functionality behaves as expected:

$term->setFormat('plain_text');
$term->setDescription('Test');

and

$term->setDescription('Test');
$term->setFormat('plain_text');

However, if no format is provided, like when excluding the code $term->setFormat('plain_text');, the system is storing the Description with the text format set as Basic HTML. This behavior aligns with the expected outcome and does not match the description in the issue summary, where it is being saved as Full HTML.

Thank you.

I've been able to replicate the issue in my local D11.x. However its reseting to whatever Text format is at top position in the Text formats and editors (/admin/config/content/formats) page, rather that reseting to Full HTML only.

I've tried programmatically changing description. The MR !5880 fixed issue in my case.

However its reseting to whatever Text format is at top position in the Text formats and editors

Do we want to check this settings during the tests?
And create a test case with changing the filters order?

In response to #21 believe that does need to be worked on. If the format saves as a different format that may be an issue. Hopefully doesn’t set to a format the user doesn’t have access to.