Fieldsets with Custom Names Disappear When Filtering by Translation Status

Issue

• In the web content editor, fieldsets that do not follow the default naming pattern (e.g., Fieldset1234) are hidden when filtering by "Untranslated" fields.
• This issue is caused by a regex that incorrectly assumes all fieldsets adhere to a specific naming convention, which may not be true for legacy or imported structures.

Steps to Reproduce:

1. Create a web content structure with a fieldset that has a custom name (e.g., "MyCustomFieldset" instead of "Fieldset12345").
2. Create a new web content article using this structure.
3. Fill in all the fields in the default language.
4. Switch to another language for translation.
5. From the filter dropdown, select "Untranslated".

Expected Result: All untranslated fields, including those within the custom-named fieldset, remain visible.

Actual Result: The custom-named fieldset and its fields disappear from the editor view.

Environment

• Liferay DXP 2025.Q1

Resolution

• This is a known issue that has been resolved.
• The fix is included in Liferay DXP 2025.Q1.16 and later versions.
• Please open a ticket with Liferay Support to request the following fixes hotfix for your version:
  LPD-57844 & LPD-59057