Managing NON-ACF fields with ACF?

  • Resolved solarbotics

    (@solarbotics)


    4 years, 7 months ago

    I’m loving how ACF pulls the necessary fields together on the backend for easy management. It works GREAT with WP All Import, and I’d like to streamline how the two work.

    I frequently update a multitude of variables between 4 or 5 plugins, and was wondering if there was a way to use ACF Pro to “manage” these variables through the backend of WPAI in the ACF section.

    WPAI is great in letting me dig into available fieldnames, but I’d ideally like them pulled together in the ACF section so it’s quicker and easier for me to manage the imports.

    eg: I have a few fields from 2 shipping plugins:
    _regular_currency_prices
    _wf_canadapost_costoms_title
    _wf_canadapost_hs_code
    _wf_canadapost_manufacture_country
    _wf_ups_hst
    _ph_ups_manufacture_country

    Instead of hunting them down each time I need a new template, I’d like to have them in the ACF section where I can properly name and text-entry box them.

    Is this possible?

Viewing 1 replies (of 1 total)
  • Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    ACF can handle any native custom field out of the box. You just need to create a new field with the exact same name as the targeted custom field.

    For example, with Woocommerce, you can re-create the “Regular Price” custom field and use it with ACF (it will update the correct custom field, and display the correct value out of the box).

    In this example, I created a field named _regular_price (as it is the name of the Woocommerce custom field): https://imgur.com/a/9IY0kgv

    Note: As you can see in the example, ACF will create an additional custom field named __regular_price upon save, in order to keep the field key reference.

    Have a nice day!

    Regards.

Viewing 1 replies (of 1 total)
  • The topic ‘Managing NON-ACF fields with ACF?’ is closed to new replies.