@zero-24 @SniperSister can you take a look at rips please

Failure: Can't connect to the API

I have tested this item ✅ successfully on 3f98219

I have tested this item ✅ successfully on dabc0f6

RTC

thx

thx

thanks

Could the introduction of this new version of Tiny MCE cause issues in modules that are created by third parties? I am using third party modules in which HTML markup is used, in textarea fields. Until J 3.9.6 this was no problem, but in J 3.9.8 all HTML markup is stripped out. Besides the update to J 3.9.8 no other settings were changed regarding Text Filtering and so on.
I have looked at the settings in the Tiny MCE plugin and tried different settings, without good result, the HTML markup gets stripped out of all fields in the third party module.

No this would have no impact

There is an issue with custom subfields and filtering html from textarea and edtor fields.
This is already fixed for the next version.

Do you mean this?

Hope the screenshots makes clear what I mean. In J3.9.6 HTML is allowed and saved properly.
After update to J3.9.8 exactly the same module gets stripped out of HTML.
As said before, I haven't changed or updated anything else besides the Joomla version.

I know it is not core Joomla, but I would not have expected this.

This problem is fixed in #25189 it will be fixed with the next version. In the meantime you could apply the patch.

I have downloaded both files from #25189 and replaced them in my local Joomla setup, but it does not solve the issue. The HTML is still stripped. For Custom module (core) is works good, but for the third party modules not.

I will download staging tomorrow and give it try again.

Just downloaded and installed J 3.9.9-dev, but still seeing the same issue.

After entering

Training

@ReLater could you please check if its releated to your PR and if we can fix it?

It's not related to my pr directly. I just provided a fix for a similiar issue for subform fields in com_fields::repeatable. And the issue here is not related to TinyMCE

All extensions that use subform fields MUST add an attribute filter to their subform child fields of type editor, textarea, text (maybe others, too) since Joomla 3.9.7 like it's common for "normal" JForm fields if you want to allow HTML input. Otherwise the validation falls back to STRING, which is the common behavior for "normal" JForm fields.

e.g.
filter="safehtml"
filter="JComponentHelper::filterText"
filter="raw" (bad decision in most cases)

Reason is a SECURITY fix in Joomla 3.9.7. Subform child fields weren't validated before that fix and for example JavaScript injections were possible without any cleaning.

Before that fix filter attributes in subform child fields were completely effectless!!

Example from core for a "good" field declaration:

<field
	name="tag_list_description"
	type="textarea"
	class="inputbox"
	label="COM_TAGS_SHOW_TAG_LIST_DESCRIPTION_LABEL"
	description="COM_TAGS_TAG_LIST_DESCRIPTION_DESC"
	rows="3"
	cols="30"
	filter="safehtml"
/>

FYI: Added info to docs: https://docs.joomla.org/Subform_form_field_type#Beware.21

Maybe it should be propagated at other locations, too.

Thx @ReLater for the confirmation.

@BurtNL can you please contact the author of the extension und notify him/her of this change?

Thanks @ReLater and @HLeithner , I have informed the author of this module already and send him the links to this thread and the docs.