Download for Free Advanced Custom Fields – Component Field Addon [LATEST VERSION]

Download for free Advanced Custom Fields – Component Field Addon from our website. Lastest version is updated on 14 July 19 and available. Advanced Custom Fields – Component Field Addon WordPress plugin is compatibile with all IE, Chrome, Safari and Firefox versions. Instead of paying $18 to gummi-io on Envato, you get it for free.

Advanced Custom Fields – Component Field Addon [Latest Version]

To download nulled Advanced Custom Fields – Component Field Addon, you just need to click the button “Download Files” below this text, unzip files on yor computer and upload on server, or directly upload Advanced Custom Fields – Component Field Addon ziped files to WordPress website.


Advanced Custom Fields - Component Field Addon nulled

About Advanced Custom Fields – Component Field Addon

Build it once, use it everywhere and forever. A simple acf pro add-on that allows you to treat a field group as a component and reuse it in any other field groups. Later on if you want to make changes to that component, you only need to edit once, it’ll apply to every field groups that uses the component.

When should I use this? Have you ever find your self creating the same set of fields in your project, say like, a custom lists menu, a testimonial block, sliders, or even a button?… Read More

User comments

sporkhc

Hi, our prior developer apparently used this plugin (incorrectly, he never re-used any components, so… yeah) and after we fix up some other parts of the site I’d like to convert away from this plugin.

Do you have more information on the “convert” button? All I see on your site is the release notes. What happens behind the scenes when this is clicked? So far all I get is data loss on conversion.

4 other replies

sporkhc

And, it showed me the “delete after convert” toggle, which I left unset, and after OK’ing the operation, the field still showed as type “component”. Repeating the process, I no longer had the “delete after convert” toggle, so the problem is still there. I have a bunch of these I need to convert (they were not implemented well), but I can’t lose all the data… Any way to convert without nuking the component itself?

WP: 5.2.1 PHP: 7.2 ACF: 5.8.0 Component Field: 2.0.1

sporkhc

ugh, missed the edit window. Can also duplicate on your own demo site, see here: https://i.imgur.com/13lScFz.png

gummi-io Author

The delete button will only show up in some conditions, for example, if it’s the last field to use the component group. For the issue that it’s still showing component after you converted, can you send me a sample export json of the compoentn field? might be a bug due to the wrong setup, i’ll need to debug on that.

you can send the export file to [email protected]

thanks.

brentleung

Hey A,

Long time.

I am having a weird issue with the component plugin. It is duplicating ACF groups over seven times on each page. When I deactivate the component plugin the duplication goes away.

I am attaching a video here: https://ln.sync.com/dl/a3a933e60/372nwfcf-ncg3kr5w-8cdy5puw-48cuakav

The steps I took:

1) deactivate your component plugin Version 1.0.13 2) Upgrade ACF Pro from Version 5.6.7 to the latest. 3) delete your component plugin Version 1.0.13 4) Install the latest: Version 2.0.1 5)Run re-migration

WPML and the plugin, Advanced Custom Fields Multilingual is installed on this website.

4 other replies

brentleung

Hey, sorry about the delay. I was on a deadline for something else. Will email all the info today.

If needed, I can also set you up with a staging server that you can access on WP Engine.

gummi-io Author

yeah, can you setup a staging server with the reproducable issue? It’ll be way easier to debug. You can send the access to “[email protected]

brentleung

Done. I just fired you off an email with the credentials.

yorkshiremedia

Hello, We have noticed an issue presenting on installs configured before WP 5.x, ACF Pro 5.8 and 2.01 of this plugin whilst using Gutenberg. When upgrading to the above versions, the previously visible fields no longer display, or are visible under settings/options in Gutenberg. This happens on all field types that Component fields. Duplicating the Field Group results in a visible section, but data is of course missing. Installing Classic Editor will restore the hidden fields. Creating new on the latest software poses no evident problems. Thoughts? Thanks, Joe.

5 other replies

gummi-io Author

HI,

I’ve created fields under wp 5.1 and acf 3.7.13, then upgrade to wp 5.2 and acf 5.8.0. The fields and value are still showing for me. I’ve tested with both regular fields from acf and also component field.

Can you send the access to that test environment that has the issue to “[email protected]”, and i’ll clone down the site to my local to run some debugging.

Thanks.

yorkshiremedia

I have emailed your support email, thank you.

yorkshiremedia

Thank you for replying with the fix, even though it is likely a WP bug and not directly an ACF Component issue. All sorted, very happy

pixeldotcreative

Hi, we’ve encountered an issue when adding a new field to a component which is in use across multiple layouts. I’ve added a new text field but it is not shown on the individual admin pages and the component is still listed as having 2 fields rather than 3. I have tried removing the field and redoing it with no effect. Any help greatly appreciated.

gummi-io Author

Hi there,

I’ve just tested quickly based on your description, it works for me.

Can you let me know which ACF Pro version and which ACF Component Field version you are using?

Aside that, can you also let me know if there’s any other acf addon you have on your site?

Lastly, your WP version and if you are viewing the admin pages in, “acf blocks”, “gutenberg view” or “classic view”?

If you can provide any screenshot or an acf export file and send to [email protected], that can will also help me to debug you problem as well.

Cheers

pixeldotcreative

ACF Pro : 5.8.3 ACF Component Field : 2.0.1 WP : 5.2.2

We also use: ACF Gravityforms Add-on : 1.2.1

We are viewing the pages in ACF blocks with Gutenburg disabled. Screenshots & an export file are coming over via email now.

gummi-io Author

I’ll look into it as soon as i got time

forgeandsmith

Hey There,

When running an update on the Component plugin from a previous 1.0.14 version to the latest, it results in a STK: No Field Found error: https://screencast.com/t/3jZPEdcC

Wondering if you have any insight on this issue.

gummi-io Author

Yoyoyo

Try Custom Fields -> Settings -> re-run migration. Make sure your ACF Pro is up to date too.

Also check where that ‘STK: No Field Found’ is coming from and the data exists, cause that text is not coming from the plugin.

Otherwise you gonna have to send me more info to go about it.

Cheers

WaterstoneHC

Hi there – The update/save function seems to have stopped working on all pages that are using this addon. We’re on v 1.0.13 and v 5.3 of Wordpress (but the functionality stopped working while we were on v 5.2). We’ve updated all plugins, tried deactivating and reactivating – nothing seems to work. We get an automated email that there’s a fatal error in line 398 of the file. Not finding anything online about a solution – any help is appreciated.

gummi-io Author

Hi,

I haven’t had this issue on my sites, but lemme try to setup a new install and see if i’m able to recreate the error. I’ll get back to you as soon as i had time to set it up.

Thanks.

gummi-io Author

Hi,

Just read you comment again and notice you are using v1.0.13, which actually no longer supported since end of 2018 due to significant code changed on acfpro plugin. You may want to update it to v2.x versions and try again.

proveedorestic

Hi, i have now your plugin acf component field 1.0.13 and acf pro 5.6.10 in production. my wordpress is 4.9.8 and php 7.1 i want to update both but i dont know the less risky path. my thinking was 1-update acf pro to 5.8.7 2-after testing eveything is ok 3-update acf component field to 2.0.2 2-testing eveything is ok

thanks.

i have seen you version 2.x requires minimum acf pro 5.7.x https://www.advancedcustomfields.com/changelog/ https://acf-component-field.gummi.io/
3 other replies

gummi-io Author

Yes, updating WordPress to 5.3.1 first is fine. It shouldn’t affect both acf pro and acf component.

proveedorestic

thks for your answer, i will do this way

proveedorestic

i can confirm you that going from acf component field 1.0.13 and acf pro 5.6.10 to acf component field 2.0.2 and acf pro 5.8.7 2

following your way, didnt work, no error and compnents seems toi be updated but my site appearance broke, and i didnt see my pages properly, i had to rollbvack my test.

1) take a backup of database first 2) deactivate component field, and delete 3) upgrade acf pro to latest 4) install latest component field 5) it should auto run the db update to convert v1 structure to v2 6) if not, go to admin dashboard, “Custom Fields” -> “Tools”, there should be a section where you can re-run the migration

i will check in depth with more time after upgrading wordpress to 5.3.1.

thks.

swebpucrs

how long does this license have? If I purchased an extended license, how many years can I use?

gummi-io Author

Hi,

The lisence policies are provided by code Canyon, and they are both 6 months, unless you have the “extended support” to 12 months. Note the extended support is not the same as extended lisence. You can read more about the differences here: https://codecanyon.net/licenses/standard

Cheers,

swebpucrs

Here at the university where I work, we use ACF PRO, we update everything on WP ( here we use wordpress multisite ) and now we need a plugin with component field.

If I buy this plugin, I can use it for how long time?

gummi-io Author

You can “use” it for as long as you want, but the support will expire in 6 months. This means, if after 6 months, there’s a new release, you’d need to purchase the license again to be able to download the new release.

Leave a Reply