95 comments found.
Hello, I’ve been using your acf component fields plugin for years without any problem. It’s even one of the central parts of my acf/gutenberg blocks system. On sites using wpml, everything’s fine, but there’s a big problem with the release of acfml v2 (which controls the translation of acf fields via wpml). I’m forced to stay with v1.x on wpml, and I’m afraid that this will eventually cause instabilities.
I past the error log at the end of the messge.
I’ve resumed support on codecanyon just for this reason, so I’m counting on you. Many thanks in advance Philippe
[20-Sep-2023 20:29:04 UTC] PHP Fatal error: Uncaught TypeError: md5(): Argument #1 ($string) must be of type string, array given in /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Package.php:97 Stack trace: #0 /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Package.php(97): md5(Array) #1 /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Package.php(76): ACFML\Strings\Package::getStringName(Array, Array) #2 /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Transformer/Translate.php(27): ACFML\Strings\Package->translate(Array, Array) #3 /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Traversable/Field.php(27): ACFML\Strings\Transformer\Translate->transform(Array, Array) #4 /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Traversable/Entity.php(31): ACFML\Strings\Traversable\Field->transform(Object(ACFML\Strings\Transformer\Translate), Array, Array) #5 /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Translator.php(81): ACFML\Strings\Traversable\Entity->traverse(Object(ACFML\Strings\Transformer\Translate)) #6 /home/philoweb/dev/wp-content/plugins/acfml/classes/Helper/Fields.php(21): ACFML\Strings\Translator->ACFML\Strings\{closure}(Array, ‘stg_classes’) #7 /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Translator.php(63): ACFML\Helper\Fields::iterate(Array, Object(Closure), Object(Closure)) #8 /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/BaseHooks.php(74): ACFML\Strings\Translator->translateField(Array) #9 /home/philoweb/dev/wp-includes/class-wp-hook.php(310): ACFML\Strings\BaseHooks->translateField(Array) #10 /home/philoweb/dev/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array) #11 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/includes/acf-field-functions.php(58): apply_filters(‘acf/load_field’, Array) #12 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/includes/acf-field-functions.php(365): acf_get_field(‘field_5fad6b561…’) #13 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-component_field/src/Field/AcfComponentField.php(594): acf_get_fields(Array) #14 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-component_field/src/Field/AcfComponentField.php(253): GummiIO\AcfComponentField\Field\AcfComponentField->fetchSubFields(Array) #15 /home/philoweb/dev/wp-includes/class-wp-hook.php(310): GummiIO\AcfComponentField\Field\AcfComponentField->load_field(Array) #16 /home/philoweb/dev/wp-includes/plugin.php(256): WP_Hook->apply_filters(Array, Array) #17 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/includes/acf-hook-functions.php(109): apply_filters_ref_array(‘acf/load_field/...’, Array) #18 /home/philoweb/dev/wp-includes/class-wp-hook.php(310): _acf_apply_hook_variations(Array) #19 /home/philoweb/dev/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array) #20 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/includes/acf-field-functions.php(58): apply_filters(‘acf/load_field’, Array) #21 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/includes/acf-meta-functions.php(309): acf_get_field(‘field_614a41944…’) #22 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-template.php(144): acf_get_meta_field(‘general_setting…’, ‘block_2dee16317…’) #23 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-template.php(26): acf_maybe_get_field(‘general_setting…’, ‘block_2dee16317…’) #24 /home/philoweb/dev/wp-content/themes/flexipow/blocks/_common/before_block.php(105): get_field(‘general_setting…’) #25 /home/philoweb/dev/wp-content/themes/flexipow/blocks/columns.php(33): include(’/home/philoweb/...’) #26 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php(675): include(’/home/philoweb/...’) #27 /home/philoweb/dev/wp-includes/class-wp-hook.php(310): acf_block_render_template(Array, ’’, false, 2, Object(WP_Block), Array) #28 /home/philoweb/dev/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(’’, Array) #29 /home/philoweb/dev/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #30 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php(649): do_action(‘acf_block_rende…’, Array, ’’, false, 2, Object(WP_Block), Array) #31 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php(566): acf_render_block(Array, ’’, false, 2, Object(WP_Block), Array) #32 /home/philoweb/dev/wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php(499): acf_rendered_block(Array, ’’, false, 2, Object(WP_Block)) #33 /home/philoweb/dev/wp-includes/class-wp-block.php(258): acf_render_block_callback(Array, ’’, Object(WP_Block)) #34 /home/philoweb/dev/wp-includes/blocks.php(1133): WP_Block->render() #35 /home/philoweb/dev/wp-includes/blocks.php(1171): render_block(Array) #36 /home/philoweb/dev/wp-includes/class-wp-hook.php(310): do_blocks(’<!—wp:acf/col…’) #37 /home/philoweb/dev/wp-includes/plugin.php(205): WP_Hook->apply_filters(’<!—wp:acf/col…’, Array) #38 /home/philoweb/dev/wp-includes/post-template.php(256): apply_filters(‘the_content’, ’<!—wp:acf/col…’) #39 /home/philoweb/dev/wp-content/themes/flexipow/page-flexipow.php(17): the_content() #40 /home/philoweb/dev/wp-includes/template-loader.php(106): include(’/home/philoweb/...’) #41 /home/philoweb/dev/wp-blog-header.php(19): require_once(’/home/philoweb/...’) #42 /home/philoweb/dev/index.php(17): require(’/home/philoweb/...’) #43 {main} thrown in /home/philoweb/dev/wp-content/plugins/acfml/classes/Strings/Package.php on line 97
Hi Phil,
Sorry I’m on vacation until the 29th. But I’ll take a look when I got a chance. In the mean time, let’s continue this via email so easier to track. Please emails at welp@gummi.io and provide either an export or screenshot on the field / block setup so it’d be easier for me to pick up from where the error occurs. thank you very much.
Hello, I have a question. In what ways is the Component Field Addon better or worse, or what is the advantage of this field compared to the Clone field?
Hi,
Component Field is create prior to the native Clone Field to have the ability to reuse field group. For basic usage, 2 field can both achieve the same thing easily.
However, the major difference is that,
1) when selecting which field to clone, component field treat the field group as options, you cannot clone only specific field within a field group.
2) component fields treats the cloned fields just the same as a repeater field, which mean, you have the ability to set min/max and have it self repeats.
3) because it’s treated as repeater field. the cloned fields are consider “sub-field”, so it’s easier to carry the code across project with the same field name when outputting.
4) components fields are hidden from the regular field group admin listing page to create a bit better user experience
Hi, we are planning to upgrade to wordpress 6.2, we are now in Advanced Custom Fields PRO 5.12.2 Advanced Custom Fields: Component Field 2.0.2 Gummi.IO
we are asking if this versions are compatibles with WP 6.2?
Apart from it, we are planning after this upgrade of wordpress, in 1 month or 2 to upgrade to latest version of ACF PRO 6.1.4
i saw in your webpage that i must go to 2.0.5, is that right? how should i do this upgrade?
Advanced Custom Fields: Component Field 2.0.5 – (New) Now compatible with ACF PRO version 6 (2022-09-21). – Added support for top level component field pagination (from repeater field). – Added support for ACF PRO version 6 new layout and UI/UX. – Added backward compatibility to continue support for ACF PRO version 5.
Thank you very much Sergio
Hi Sergio,
Yes, although no heavily tested, but version 2.0.2 should be compatible with latest Wordpress version as the versions after 2.0.2 are mainly for compatibility on the ACF Pro plugin.
If you do upgrade ACF Pro to anything after version 6, then it is suggested you to upgrade to latest Component Field. ACF PRO version 6 introduced the new tabbed layout and design refresh. That’s what the new Component Field version 2.0.5 fixed.
You are fine to upgrade wordpress to 6.2 now, and upgrade ACF PRO and Component Field together in a later date.
Aside from that, I’ll suggest also do a quick stage or local test before go into production as a safety precaution.
Thanks.
i will do this way, and tell you about. If v2.0.2 and acf pro 5 should be compatible with wp 6.2, i will do this first and check. thnk you again
i find that if i update a component that it no longer works for the blocks that it exists on, is there a workaround?
Hi,
I played around and tried to understand what you mean, but I couldn’t. Do you mind giving me some more detail on some basic setup? So I can recreate the issue and see if it’s intentional or bug, and provide you a work around. Thanks.
You can contact me with some brief steps or screenshot via welp@gummi.io
I sent an email. Thank you.
Hey Gummy.io
Great plugin! It would be awesome to include an option to be able to toggle/expand/hide a component field (to hide/show the fields within) in the next version.
Thank you!
Hi,
Thanks you for using the addon. I’m glad it helps you. Thank you for your suggestion. I’ll put your suggestion in the list and think about it.
Cheers 
Dear Gummy.io
I have just bought the plugin (7e41a112-a321-40ce-a342-1e39f985585b) and it is exactly what I was looking for. Only, there is one part of the current behavior that is giving me an issue. When I mark a ACF group as “this is a component”, the options to allocate the item to the admin pages of posts, blogs etc. (Location option with rules) is removed and existing entries are removed.
For my type of use, I require the component to still show up on pages, posts and products and the ability of use it within another ACF element. Can this function be enabled/accomplished in some way?
Kind regards, Martin
Hi Martin, thank you for purchasing my plugin. This location option is disabled (hidden) on purpose so the component group are isolated and not to be confused. However, I do think it is possible to do what you want. Give me a day or two toplay around with it. I think I maybe be able to provide you with a snippet to enable that. Thanks.
Hi Martin,
Good news. Turns out with a bit of custom action and filter, it’s able to do what you want. Here’s a gist file you can reference. https://gist.github.com/gummi-io/fe2f1e1c7c974cbe208f38ef1e8b46c0
Depends on how you want to set it up, can move the code around. Lemme know if you have any questions thanks.
This is great! Thank you so much for this solution, greatly appreciated. Although it would be even nicer to add this functionality in the official plugin instead of this workaround, I can entirely do what I was hoping to do.
Cheers, Martin
Thanks for the feedback. I’ll add it to the backlog and decide if this will be officially put into the plugin. If I do, i’ll make sure I update this comment to let you know.
Have found a bug in the latest version of the plugin it seems.
Since the latest version, any fields in a component using javascript aren’t editable. Text fields are, but fields such as Select drop-downs when used in Reusable blocks aren’t – the fields are not clickable.
It seems inline CSS has been added: ‘pointer-events: none;’ onto the select2 field which makes the field unselectable.
If you go to Manage Resuable blocks you can edit there, but on the page itself, they are not clickable.
Hi, Thank for reporting. I’ll try to recreate and check it out as soon as I have a chance.
HI,
I’m trying to recreate based on what you describe but unable to see any broken js.
Here’s what I’ve done on a new wp install 6.1.1, latest acf version 6.0.5, latest component version 2.0.5 and nothing else is installed.
Created a field group set to component field. In the field group, i have a select field with multiple selection and stylized ui selected.
Created another field group, set the location to posts. In the field group, i setup a component field which uses the field group i created above.
I’m able to select the dropdown value just fine. Other than select field, I’ve also tried post-relationship and users field since they are all using javascript. They are all fine for me.
Are you able to provide and example fields export, register block code and other plugins you have on the site that might be related for me to test?
Thanks.
Hi again,
Just read through your comment again and I think I’m able to recreate what you described. However, it is doing what it’s intended to do. You can actually be able to recreate that without the component field plugin activated.
I have the component field plugin deactivated. And use a regular repeater field, and put a UI enabled select field as sub field. Assign the field group to a acf block. Then convert that block to a re-usable block. You’ll see the same behaviour on that select field. https://share.getcloudapp.com/2Nu6RXAl
Same thing with other js fields, users and relationship. https://share.getcloudapp.com/5zu2m1J0
If I understand your question correctly, then it’d a intended ACF behaviour you’ll have to contact ACF support. It might be a bug, or it might be intentional, but is a discussion with ACF team.
But please do let me know if i misunderstand, and provide an example for me so i can look into further.
Thanks.
Thanks for the latest update. Do you know of any breaking changes this update fixes, or is it mainly layout issues?
Hi,
I haven’t rolled out the acf 6 update to all my sites yet. But as far as I can tell ones the ones I did, both acf 6 or component field add-on are just layout issue with the new UI/UX. Data-wise, i haven’t had any issue yet. Sites are still functioning correctly.
Thanks.
Excellent, thanks for the info. I too have not noticed any actual errors running ACF 6 with 2.0.2, just the UI was a bit janky. Thanks again.
When do you plan to release an update that is compatible with ACF Pro 6.0, which has been released today?
Hi,
Yes. The update is already in process. The release will be up asap when all features and backward compatibility are fully tested. Thanks.
This gets extremely slow when nesting a component in flexible content layouts. Often breaks the page with timeout limit
Hi, are you able to produce and example of your setup, server config, related plugin used and example data that you experience slowness?
I haven’t experience any slowness cause by the add-on itself. Usually it’s cause by other plugin slowing down the ajax calls, or incorrect fields setups.
Thanks.
I’m getting this error when importing a Field Group into a site where ACF Components is installed. (The imported field group has no component fields)
Notice: Undefined index: is_acf_component in /[PATH]/wordpress/wp-content/plugins/advanced-custom-fields-component_field/src/Screens/Tools.php on line 105
Hi Chris, I’ll take a look shortly.
Hi,
The bug has been fixed and waiting for approval. V2.0.3 will be release and I’ll update you as soon as i received the notification.
thanks.
Hi, the new version is now released with the undefined index error fixed.
Hi Can you tell me whether this works with multisite.
I see you say that it is maintained simply you haven’t needed to do any updates.
Can I ask whether you offer a refund policy if it doesn’t do what I need? As in, it does do what I need, it’s just a question of whether it works in my environment
Hi Chris,
Yes, the plugin will work with multisite. This addon is just like any other acf addons, it’s just adding a new field types.
If it doesn’t work as you need, you can shoot me a message first to make sure it is setup correctly or try to help you for what you need.
For refund policy it’s through codecanyon you can read it up on their refund policy.
thanks.
Hi gummi-io,
I just bought the plugin and I’m trying to make it work, but I can’t find anything in the documention about the situation that I’m trying to make.
What I would like to do is use a flexibel content as a component. So I make 1 flexibel content component that I can use through out the website. But I can’t make it work at this point. It doesn’t output anything. Do you know what I am doing wrong? Please let me know!
Kind regards, Tim Prudon
Hi Tim,
First of all, thank you very much for interesting in my plugin. Do you mind providing a bit more information for me?
1. WP version, ACF Pro version, Any ACF related addons version 2. export of the field groups that didn’t work for you and perhaps a screenshot of what you are seeing.
You can send the information to welp@gummi.io and I’ll do my best to help you.
Thanks.
Hello, Just wondering what the support plan for this product is going forward? I notice limited updates in recent months. Thanks
Hi,
The product is still very well supported. There wasn’t any update for a while cause nothing has broken or reported. It has been constantly tested with the relatively latest versions of wp and acf pro. In fact, me myself has been using it on several of my active client sites without any issue either (at least my use-case). If you encounter any issue or question, please feel free to lemme know. thanks.
Thanks for the reply. No problems on our side, just checking, keep up the good work, thanks
Hi, does this add on support graphql? I.E. will the component fields be available to the graphql schema when using wpgraphql and acf-graphql addon?
Thanks
Hi,
I’m not familiar with wp graphql. But I’d imagine it will since every function used in component field is all using the acf’s core functions. If any plugin were to extends using the acf’s actions/filter, it should work.
If it doesn’t, you could provide an example site and i’ll see what i can do to help. ]
thanks.
Nice. Just got it up and running and going through your demos and re-creating them which is a helpful, but slow process. Any chance you can send over the demo files to import?
Also, I’m currently cloning my components into a flexible layout module. For example, brining in my button components into a hero as a ‘clone’ so I can take advantage of ACF’s ability to choose which fields to use. Is there any issue with doing this to be aware of? Cheers.
Also, just noticed an error in my admin when viewing the ‘screens’ pull down on the component page in admin.
Warning: Undefined array key “acf-fg-count” in /Users/joshuahinden/Local-Sites/my-site/app/public/wp-content/plugins/advanced-custom-fields-component_field/src/Screens/EditFieldGroup.php on line 217
I’m running version of ACF, WP and ACF Extended and using Local WP with nginx 7.3.5 and mysql 8.0.16
Call Stack- Time Memory Function Location 1 16815467830.5279 379680 {main}( ) .../edit.php:0 2 16815467830.5279 12194784 require_once( ’/Users/test/Local-Sites/my-site/app/public/wp-admin/admin-header.php ) .../edit.php:396 3 16815467830.5279 12418936 WP_Screen->render_screen_meta( ) .../admin-header.php:265 4 16815467830.5279 12419016 WP_Screen->show_screen_options( ) .../class-wp-screen.php:956 5 16815467830.5279 12419016 get_column_headers( ) .../class-wp-screen.php:995 6 16815467830.5279 12419488 apply_filters( ) .../screen.php:37 7 16815467830.5279 12419896 WP_Hook->apply_filters( ) .../plugin.php:189 8 16815467830.5279 12422560 GummiIO\AcfComponentField\Screens\EditFieldGroup->adjustListColumns( ) .../class-wp-hook.php:303
Thanks
Perhaps related, I can’t seem to get component in component fields to display. I tried to recreate your banner demo and have a button component there, but the sub_fields are empty. Should that be the case? Thanks { “key”: “field_613c216bf5b5f”, “label”: “Banner Button”, “name”: “banner_button”, “type”: “component_field”, “instructions”: ””, “required”: 0, “conditional_logic”: 0, “wrapper”: { “width”: ””, “class”: ””, “id”: ”” }, “acfe_save_meta”: 0, “field_group_key”: “group_613c0c1c20890”, “repeatable”: 1, “min”: ””, “max”: 1, “layout”: “block”, “button_label”: ””, “appearances”: ””, “acfe_field_group_condition”: 0, “collapsed”: ””, “sub_fields”: [] }, {
Nevermind, I’ve aborted using this plugin. Thanks though, I still learned a lot from studying your setup. In a rush though and managed to use clones to get close to what I was after.
Hi,
Sorry for the late respond, was on vacation. Sorry to heard that the plugin didn’t fit your needs. Though, based on your description, you don’t need to use clone field along with the component field. They are the similar concept but different feature (in fact, component field is created prior to clone field). To reuse the same button, you can just select the component field, and select your button field group. There’s no clone field needed.
As for you error message, i’ll double check for you, i believed it has something to do with recent acf updates, or acf extended manipulated the table columns.
Thanks.
No worries, thanks for getting back. I learned a lot from studying your setup and so it helped me out in the end. If we run into an issue where we’d benefit from using the component specifically I’ll let you know and we can sort out the issues then.
Looks like a cool plugin, but I see it hasn’t been updated and no comments for many years. Is this still working and up-to-date? Thanks
Hi,
Yes it is still working and up-to-date with the recent wp/acf version. Hasn’t had any update because the plugin is still working just fine and no bugs have been reported.
Thanks
hi, have you checked compatibility with wordpress 5.7.2 and acf pro 5.9.7? i am planing to upgrade worpress to 5.7.2 from 5.6.2 and acf pro from 5.9.5 to 5.9.7. i use latest version component-field-addon v.2.0.2. thnks
Yes, so far i have 6 sites running on the latest version and haven’t encountered any issue yet. But that’s just my sites, if you do see any bugs, please let me know thanks.
Hi We recently purchased this plugin. I saved a component but it does not show in the list of Field Groups. When i click on “Components” (which has the proper count) from Field groups page it shows a blank page. meaning we are unable to edit a component. this makes the plugin useless. can you please let me know how to solve this problem. I’m on the latest version of WP and ACF.
hi,
when it showed a blank page, do you have error reporting turned on and see if there’s any error message? I just tested latest wp, acf pro, acf component and everything works just fine. do you have other plugin that might interfere with?
Hello, I’ve just write to you a message about a possible bug of your useful plugin (the field doesn’t show in acf extended flexible content). But, sorry, I’ve juste realize that I’ve made a mistake, your plugin is fully fonctional. Thank you !