Pull Request resolves #48704 .

• I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

administrator/components/com_config/tmpl/component/default.php builds $dataShowOn for a fieldset that has a showon attribute and loads the showon script, but the attribute was never printed on the <fieldset> element (the output was lost when Global Configuration moved to custom-element tabs in 4.0). This PR outputs it on both fieldset tags, so showon on a fieldset in a component's config.xml works again.

Testing Instructions

1. Edit administrator/components/com_users/config.xml and, inside the integration fieldset, add a second child fieldset after integration_customfields:

<fieldset name="integration_test" label="Test showon fieldset" showon="custom_fields_enable:1">
	<field name="test_text" type="text" label="Test text" />
</fieldset>

The added fieldset is a dummy for testing only. "Edit Custom Fields" is used just as an existing Yes/No field for its showon to depend on; its own behaviour is not changed by this PR.

2. Go to Users > Manage > Options > Integration tab.
3. Toggle "Edit Custom Fields" between Yes and No.
4. Apply the PR and repeat steps 2-3.

Actual result BEFORE applying this Pull Request

The "Test showon fieldset" fieldset is always shown. The <fieldset id="fieldset-integration_test"> element has no data-showon attribute.

Expected result AFTER applying this Pull Request

The "Test showon fieldset" fieldset (including its legend) is hidden when "Edit Custom Fields" is No and shown when it is Yes. Fieldsets without showon are unchanged.

Link to documentations

Please select:

• Documentation link for guide.joomla.org:

• No documentation changes for guide.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed

Screenshots