Advanced Custom Fields - Component Field Addon

Build once, use anytime, anywhere. A simple acf pro add-on that allows you to treat a field group as a component and reuse it in any other field group.If you want to make changes to the component in the future, you only need to edit it once, and it will be applied to each field group that uses the component.

When should I use it?

Have you ever found yourself creating the same set of fields in your project, such as custom list menus, recommendation blocks, sliders, and even buttons?Well, this plugin may be exactly what you need. Essentially, this plugin will allow you to create the "same field set" only once, and you can reuse it as many times as you want.

Requirement

WordPress 4+
ACF PRO 5.7+

Note: This plugin is only compatible with ACF pro version due to their structure setup differences.

Examples and live demos

Feel free to visithttps://acf-component-field.gummi.io/View example usage and live demos.

Changelog

2.0.2
- Fix the bug that sometimes the component field group will be deleted when converting to transponder field.
- Fix WPML error that the field group cache is triggered too early.
- Fix the error that the local acf-json folder contains the location setting of the component field group.

2.0.1
- Add import compatibility when exporting json files using v1.
- Add management tools to run the migration manually (Custom Fields -> Tools).
- Added 2.0.1 migration to try to fix component fields that were damaged when upgrading to component field v2 in the wrong order

2.0.0
- Complete rewrite for better performance, new hot features, and small UX changes.
- Due to javascript changes, the minimum requirement for ACF pro is now 5.7+.Before the end of 2018, component field version 1 will still support questions and help, but will no longer receive new updates.
- Core change: V2 no longer uses custom post status acf-component to process component fields. Instead, it uses meta values.(When you upgrade to 2.0, the plugin will run a script to solve this problem for you)
- Core change: The field group attribute "field_group_id" has been renamed to "field_group_key". (When you upgrade to 2.0, the plugin will run a script to solve this problem for you)
- New feature: You can now convert an existing transponder field into a component field (a new component field group will be created and the subfields of the transponder field will be moved into it)
- New feature: You can now convert component fields to transponder fields, and you can choose to automatically delete component fields after conversion.(The current component field will be changed to repeater, and the gorup field of the component field will be copied as a subfield of repeater)
- UX enhancement: You can now set the default component field settings on the component field group. (Such as button label, minimum value, maximum value, layout)
- UX enhancement: In the list, when you are in the component tab, it now displays the number of times the component has been used.This is useful if your site has a lot of old components and you are not sure whether to save to delete.
- UX enhancement: After copying the component field group, it will now redirect you to the component tab instead of the active tab.
- Performance enhancement: With the new JS in ACF pro 5.7, some hacky js codes in component fields have been removed. Now the backend runs much smoother.
- Code enhancement: The plugin code has been completely rewritten for better performance and less hacky. The file/folder structure has also been reorganized to improve readability.

1.0.14
- Fix the import/export error of the new "management tool" framework of acf pro 5.6.5.

1.0.13
- Fix the field class constructor of ACF 5.6.0 version.

1.0.12
- Fix the error that the component adding row event is not registered correctly when adding the field group metabox through ajax.

1.0.11
- The "This is a component" checkbox in the component field will now remain selected when copying.
- Fix wpml language duplication not selecting the correct component group. After the language is copied, it will "try" to find a matching translation component field.
- Add /lang/acf-component_field-default. Pot stall

1.0.10
- Add optional alternative styles for nested components.Screenshot

1.0.9
- Fix the php warning error when importing regular acf json files.

1.0.8
- Fix the copy and paste error that would cause warning errors if wp_debug is turned on.

1.0.7
- Added a plug-in activation hook to fix the problem that component fields are not restored after the plug-in is updated.

1.0.6
- Fix the error that acf_get_field_groups() did not correctly check the synchronization of the local json cache after updating the component fields.
- Fix the bug that the single sync/batch sync from the local json cache is not set to the correct state.

1.0.5
- Add the function of reading the local field generated by "acf_add_local_field_group()" to the "Select Field Group" drop-down list.
- Fixed the bug that the sub-fields could not be rendered if the component fields were exported to the local php export.

1.0.4
- Thanks to Thomas, the German translation was added. Added index. php to prevent directory listing.

1.0.3
- Updated plugin metadata to point to live demo

1.0.2
- Fix backend javascript when nesting component fields

1.0.1
- Fix the front-end value parsing problem.

1.0.0
- Initial release.