Missing field group options on localized backend

Hello,

we found what looks like a localization-related bug in ACF Extended when editing ACF field groups in the WordPress admin.

Environment:

• WordPress admin language: de_DE
• ACF Pro
• ACF Extended
• ACF field group editor

Issue:
Custom ACFE field types in the WordPress category, especially Post Types (acfe_post_types), are available in the “Browse Fields” modal, but they are missing from the normal field type dropdown when the backend language is German. In English admin they appear correctly.

Observed behavior:

• With admin language en_US: the WordPress section is present in the field type dropdown and Post Types can be selected normally.
• With admin language de_DE: the WordPress section is missing from the normal dropdown.
• Existing fields of type acfe_post_types can then fall back to another field type such as Range when saved, which can corrupt the field configuration.

Probable cause:
In acf-extended/includes/field-groups/field-types.php, ACFE reorders field type groups by inserting them after the hard-coded category label Advanced in get_field_types().
However, in localized ACF admin screens this label is translated, e.g. in German Advanced becomes Erweitert. Because of that, the ACFE custom groups are extracted but not reinserted correctly in the normal dropdown.

The relevant logic appears to be this kind of pattern:

• category target is hard-coded as Advanced
• but ACF localized categories use translated labels depending on admin language

Suggested fix:
Use the localized ACF category label for advanced instead of the hard-coded English string when reordering groups in the field type dropdown, or rely on the category keys rather than translated labels.

This issue seems reproducible and specifically affects non-English backend languages.

If helpful, I can also provide a minimal patch showing the adjustment.

Best regards