108 comments found.
Hi. We are now in WordPress 6.6.2 and Advanced Custom Fields PRO 6.3.9 y Advanced Custom Fields: Component Field 2.0.8 We are planning to go to Advanced Custom Fields PRO 6.7.1 (latest), and as Advanced Custom Fields: Component Field 2.0.8 has not have any Update from july 2024, we want to ask you if you know it has been tested or if you know it has any incompatibility with it. After this, in several months, we are planning to go to WordPress 6.9.3 (latest) and the question is the same we still see your requirement are WordPress 6+ y ACF Pro 6+, but as it is a component importnt for us we want to ask you
thank you Sergio
Hello Sergio,
Although the addon hasn’t been updated in a while, it’s still fully usable and working perfectly fine. I’m currently using it across several sites I manage and haven’t run into any issues so far.
If you do encounter anything, feel free to let me know — I’d be happy to look into it for you.
That’s a great point though. I’ll push a version bump and update the description so it’s clear that it’s still being actively maintained. Thanks for bringing that to my attention.
thank you very much for your answer. i will upgrade plugins and let you know. thank again for you answer
Hello, it seems it doesn’t work with graphql, i’ve tried to make it work but just return the fieldname, and no the content of the component. 
27 days ago :_(
Hi Cokeito,
Sorry didn’t get the email notification about this new comments. I’ll take a quick look at it first. I’m assuming you are using the official “WPGraphQL” addon?
Hi,
As I’m not very familiar with GraphQL or how people usually use it, I can only do a simple implementation. Based on studying the code, in the new version, I’ve registered the component field as a GraphQL field type.
Preview:
component field group: https://share.zight.com/NQuAB7y6
page field group: https://share.zight.com/NQuAB726
page values: https://share.zight.com/GGuBdEq6
graphql editor: https://share.zight.com/o0uLO7Wk
new version is submitted now, waiting for approval.
New release is now approved. 2.0.9 should include basic compatibility for graph ql
At first try works like a charm, will do some devel in the next days and comment my results, thanks in advance for the update!
Having an issue on a site using this plugin where the component all of a sudden appears on every block – even if the component is already appearing on a block (it appears twice).
I’ve removed the component altogether from ACF but it’s still appearing in the block editor as Field Group can’t be found.
So weird. A local copy doesn’t have the duplicate Component on every block, but the live one does. Have removed all files and re-uploaded but problem persists leaving me to think this is in the DB somewhere. Has this been experienced before?
Hi, are you using any acf-local json features? Sounds like you have the field groups cached so they are loaded twice. Can you check if under your active theme, there’s a “acf-json” folder and have duplicated field groups? Thanks.
Components used as repeater cannot be collapsed. For example: original Repeater field, under Presentation tab, has Collapsed select field, which enables items to be collapsed, which is useful when item has multiple fields. However, this Collapsed select field is not available when using Component field, which is marked as Repeatable. Under Presentation there is only Button label, and no Collapsed select field.
So how to collapse repeatable fields generated with your plugin?
Hello kikky1
Currently it is not supported. I’ll see what i can do in the next couple days and let you know when a new release is ready. Thanks.
Where is version 2.1.0, which was released a few days ago? Why I can’t download it from here?
Hi, there’s no version 2.1.0. The last release was about a month ago version 2.0.7. Can you let me know where do you get the version 2.1.0 notification? thanks.
v2.0.7 has bug – cannot be activated throwing just an error Something went wrong… or something similar without any additional error logs. v2.0.6 works.
HI,
Can you provide a bit more info on your php, wordpress, acf pro versions?
I’ve tested on the latest wordpress and acf pro against php 8.1, 8.2 and 8.3 and i haven’t encounter any errors.
WordPress 6.4.3 using WordPlate boilerplate PHP 8.3.3 Nginx 1.25.4 ACF Pro 6.2.7
Local development with Herd 1.5.0, macOS 14.4.1
Hi, seem like the individual plugin zip file uploaded to codecanyon has some files missing, i just re-upload for submission. Stay tune on the updated file.
Hi Kikky1,
The item has been approved, can you try download again? thanks.
Values are overridden…
If I use ACF group with same fields and same names for 2 different Options Page, I can enter different values for each options page. But when I use your plugin it just pulls same data for every options page.
How is this reusable? I need to come up with different name for each reused component and be careful not to enter same name so I can’t even use multiple rules?
EDIT: I can’t remove it so just ignore this comment, Options Page is just bad and global settings that requires unique name (for example, I am using it for archive pages to provide some more custom fields)
Hi, Yes, that’s by design on the options page.
Another way you could do is when defining the option page, pass a unique post_id. And instead of doing get_field(‘field_name, ‘options’); you can do get_field(‘field_name’, ‘unique_id’);
https://www.advancedcustomfields.com/resources/acf_add_options_page/ (see the post_id parameter). Default is “options” but you can put whatever you want there like, ‘product_archive’. And do get_field(‘field_name’, ‘product_archive’);This way you can have the same field name, but since the options page’s id is different they can have different value on each option page (assuming each option page has unique post_id)
Code: bb2204dc-dcaa-4f76-8a46-39a80aa75c3d
I see this hasn’t been updated for a while, so there is some stale code when using PHP 8.3.
Under Components table view, column Used, there is this error: “Deprecated: Creation of dynamic property GummiIO\AcfComponentField\Query::$group_key is deprecated in /.../advanced-custom-fields-component_field/src/Query.php on line 126 0”
Hi,
The updated version is now approved by CodeCanyon. The new version 2.0.7 should have the warning fixed.
Thanks.
I am sorry, but there literally is no ‘reply box’ in the original thread whatsoever.. incredibly frustrating and I am logged in with the same account that I filed the support ticket with?
I just bought the updated plugin and tried installing it this morning but the issue persists.
I am running ACF Pro 6.2.5 and ACF Component Field 2.0.6.
Disabling the component plugin removes a plethora of content from the webpage.
In that case, please contact CodeCanyon for assistance. Let’s continue the conversation via email to avoid creating a new thread with every reply, affecting other users seeking information.
Please send an email to welp@gummi.io with the new specific error bug trace from your error log after updating the component plugin.
Additionally, provide a step-by-step guide on how to reproduce the errors, including the necessary plugins, code, and export acf fields related to the issue. Based on the limited information from the original comment, it is impossible to conduct any investigation without a simplified version or sample code exhibiting the exact same issue.
Yes, disabling the component plugin will temporarily disrupt the frontend. The issue lies in the backend, and we need to determine if it persists when the plugin is deactivated. Thanks.
There is no way for me to reply to my own comment thread?
Yes I can confirm that I have both the most up to date ACF Pro and ACF – Component Field Addon.
You should be able to reply your own comment using the reply box on the original thread.
What’s your acf component field version? The latest one should be 2.0.6. I mentioned earlier that the most recent plugin doesn’t seem to have the file or method shown in your screenshot. Is it possible you’re using an outdated version?
I took a look at your Zoom video, and although I couldn’t get a full look at the setup, I didn’t spot any use of the component field in the field group you showed. Have you tried deactivating the component plugin to see if the issue still persists? Thanks!
Hello team,
Please see the loom video I have here that describes our issue, I initially reached out to ACF PRO support who had advised that I contact you instead as this is an error with your plugin and not theirs: https://www.loom.com/share/2cb1095a024e49faaa3470cc57bd942b?sid=824b91aa-782c-4c85-b721-3afacd01d7f9
See below for their response and their screenshot detailing the issue.
christopher.mucheke@wpengine.com January 28, 2024 Christopher Mucheke replied Hi Ian,Thanks for getting back to me,
From the error message you’re getting, the error is coming from the Advanced Custom Fields – Component Field plugin and not ACF, see: 
I’d recommend reaching out to the Advanced Custom Fields – Component Field plugin support who should be able to troubleshoot these issues with you, it can be very difficult for us to debug issues arising from third-party plugin integrations, while we can pinpoint the issues arising from the said plugins, we can’t debug them since we do not have access to their source code.
Hope that all helps, please let me know if anything needs clarification.
Kind Regards,
Chris
See screenshot from ACF support: https://p23.zdusercontent.com/attachment/48506/HnlybmOJF0xiOAlGkYFs31LVq?token=eyJhbGciOiJkaXIiLCJlbmMiOiJBMTI4Q0JDLUhTMjU2In0..M2yUrwIKIAYcJvnsFAp7Eg.zJs4S_eEkSRRIMrYILUMao65B4GLdMYjCkLziPG0yzcS5Mq83cHkC5dxm1867Vh1Q6HkrQOlbVHGAQ6nG43YJMF_DUXC2tfmTzjH-z5bm_Vd5pWtvBYWV91f_vFABgoT56Bqeeh9c1J3gWVBjN66b6GRENrMepUTXxM6fAqQgliL2rG_jsdsYJ2-U6qLAaT629KYSJXFrtmQdR_mG3RcoFfgrb3MQKAPz4-2Btc-miJ04oN-sbyC1uvWcwAS2d-a2h9XB1m2pKGfWSRklhfV8iawQS82n7mRgo0E3m8kZ0U.b5iOBtCroC1z44J7zkLCowHI Christ,
Just had a quick looked at your help desk screenshot. This plugin doesn’t have a file called acf-component_field-v5.php nor a method called “filter_avaliable_groups”. Can you confirm you are using the latest version on both component field and acf pro? Thanks.
Hi I’m having some issues when trying to get component fields nested within a flexible content field when using update_field from outside of the page or page editor.
use case: I created a function to save the contents of a flexible content field to a static text field (called “flex_text”) in order to “cache” the output of the flexible content field. This works perfectly inside the save_post function (see functions.php paste bin)
I’ve created a backend plugin to loop through all pages, and update their “flex_text” field. however when calling the same function (mentioned above) from the plugin, the component fields do not load.
functions.php https://pastebin.com/9neGuASp plugin.php https://pastebin.com/NirMJ4rV sample layout file https://pastebin.com/DLP4xEbPThanks
Hi,
Thanks for reporting, I’ll take a look at is as soon as i can time sometime this week. In the meanwhile, are you able to provide a sample acf field group json export as well? thanks very much.
Hi, this ended up being an issue on my end. it’s resolved. thanks
Hi,
We’ve been experiencing increasing performance issues in the admin panel on our website.
We’ve got a number of page templates that allow marketing to build completely bespoke pages by using a number of ACF fields and components. Over time, these pages become unresponsive and difficult to manage because the HTML document size starts to hit sizes that I’ve not seen on a webpage before.
I then ran a few tests, adding and removing components. This was my findings:
Adding components into the flexible field: No components but the page template all-components :348kb 1 component – hero : 15.1mb 2 components – hero TextContent : 15.2mb 3 components – hero TextContent Alert : 15.6mb — its now slow to work with and slow to update 4 components – hero TextContent Alert ComponentRow : 17.9mb —Very slow to work with and very slow to update
Removing the above components: removed hero: 17.7mb removed text content: 17.6mb removed component row: 15.5mb removed alert: 8.3mb (at this point, there’s no acf components on the page)
Looking in the head theres still a ton of ACF stuff relating to the removed content, meaning over time this will just continue to increase in size.
Example of some of the data that’s being injected. <label for=”acf-field_5f5f790899780-acfcloneindex-field_5f28475c53a10-acfcloneindex-field_645cd86e0d48e”>Hero V2</label>Hero V2 with split background colours
<input type=”hidden” name=”acffield_5f5f790899780field_5f28475c53a10[field_645cd86e0d48e]” value=”” class=”acf-repeater-hidden-input”>|
<label for=”acf-field_5f5f790899780-acfcloneindex-field_5f28475c53a10-acfcloneindex-field_645cd86e0d48e-row-0-field_645bb5b8a9ff4”>Title</label> The main title <input type=”text” id=”acf-field_5f5f790899780-acfcloneindex-field_5f28475c53a10-acfcloneindex-field_645cd86e0d48e-row-0-field_645bb5b8a9ff4” name=”acffield_5f5f790899780field_5f28475c53a10field_645cd86e0d48e[field_645bb5b8a9ff4]” placeholder=”A head start with money”> <label for=”acf-field_5f5f790899780-acfcloneindex-field_5f28475c53a10-acfcloneindex-field_645cd86e0d48e-row-0-field_645bb59ea9ff3”>Category</label>Short title to sum up the page or category <input type=”text” id=”acf-field_5f5f790899780-acfcloneindex-field_5f28475c53a10-acfcloneindex-field_645cd86e0d48e-row-0-field_645bb59ea9ff3” name=”acffield_5f5f790899780field_5f28475c53a10field_645cd86e0d48e[field_645bb59ea9ff3]” placeholder=”Rooster Card”>Disabling your plugin prevents this code being injected into the head. Please advise on a potential solution. I’d upload a copy of the dom but the file size is far too big. Regards, Will |
Hi Will,
Component field add-on is just extending the built-in repeater field and create a more user friendly interface and functionalities. it uses everything from the original ACF core. The code you paste is a standard ACF repeater field input and they are expected as it. Which means, if you switch all the component fields to the built-in repeater field or clone field, you’ll get similar result.
The fact that your field group has 17mb of pure html outputted doesn’t seem right. You might want to check if your code is doing unnecessary loop or db connections. Building and structuring you acf fields requires careful consideration too. Unfortunately, there’s nothing i can do about it as these performance aren’t coming directly from the addon itself.
Couple suggestions, 1) if you find your site loading slow, you can always upgrade or configure the server settings to allow more memory or output buffer. 2) You can also look at ACF’s built-in local json features to speed up the initial field loading speed as it’ll read from json file instead of from database.
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.
){kind=link}