Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new ACF settings to select extended qTranslate types #1300

Merged
merged 1 commit into from
Mar 25, 2023

Conversation

herrvigg
Copy link
Collaborator

Eventually the extended types may be removed completely.
This new feature allows to choose which extended types can be picked.
The default value becomes false for all extended types.

This only impacts the list of types available in the group edit.
The extended types are still loaded and translated as usual. It is up to the admin to clean up pending types.

image

Eventually the extended types may be removed completely.
This new feature allows to choose which extended types can be picked.
The default value becomes false for all extended types.

This only impacts the list of types available in the group edit.
The extended types are still loaded and translated as usual.
It is up to the admin to clean up pending types.
@herrvigg herrvigg added the module: ACF Integration with ACF label Mar 25, 2023
@herrvigg herrvigg merged commit 5ec0ad2 into master Mar 25, 2023
@herrvigg herrvigg deleted the acf-settings-extended branch March 25, 2023 15:17
@herrvigg herrvigg added the enhancement New feature or request label Mar 25, 2023
herrvigg added a commit that referenced this pull request Mar 30, 2023
Follow-up of #1186 and #1300.
Since the standard ACF fields are better supported, those should be
preferred over the qTranslate extended fields.

In particular: text, textarea, wysiwyg are covered by the ACF standard
fields, while others only exist as qTranslate extended fields.

Deprecate softly these "duplicated" extended fields in their labels.
herrvigg added a commit that referenced this pull request Mar 30, 2023
Follow-up of #1186 and #1300.
Since the standard ACF fields are better supported, those should be
preferred over the qTranslate extended fields.

In particular: text, textarea, wysiwyg are covered by the ACF standard
fields, while others only exist as qTranslate extended fields.

Deprecate softly these "duplicated" extended fields in their labels.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request module: ACF Integration with ACF
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant