Forum Replies Created

Viewing 15 replies - 1 through 15 (of 677 total)
  • Plugin Support ACF Support

    (@acfsupport)

    Hi @mikeyswede,

    Thanks for writing in, and apologies for the delayed response!

    The ACF oEmbed field relies entirely on WordPress’s native oEmbed engine to fetch and display media. This means it will only work out-of-the-box with URLs from WordPress’s official list of whitelisted providers (such as Vimeo, DailyMotion, SoundCloud, etc.).

    If you are trying to embed a video from an unsupported source, the field won’t be able to render it automatically. To get other videos working, you will either need to host them on a supported platform or manually register your custom video source in your theme’s functions.php file using the standard WordPress wp_oembed_add_provider() function.

    If that doesn’t solve it, we’d love to continue investigating and troubleshooting this with you. This forum is generally used by ACF users to help each other out, so please create a ticket using our support form and our team can look into it further.

    Kind regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @mikeyswede,

    Thanks for reaching out and apologies for the delayed response!

    The issue here is that standard choice fields output plain text, so a raw URL will just display as a text string. Furthermore, standard HTML <select> dropdowns do not natively support images inside their options.

    As a quick solution, you can try using a Radio Button field instead and entering actual HTML into the choices area like this: 1 : <img src="image-url.jpg">. Alternatively, the most robust method is to just store the basic values (1, 2, 3…) in ACF, and then use your theme’s frontend PHP template to output the corresponding star images based on the selected number.

    If that doesn’t solve it, we’d love to continue investigating and troubleshooting this with you. This forum is generally used by ACF users to help each other out, so please create a ticket using our support form and our team can look into it further. If you’ve already created one, our support team is already at it!

    Kind regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @aaresrikanth,

    ACF Support Team here. This forum is generally used by ACF users to help each other out.
    However, we’d love to continue investigating and troubleshooting this issue, please can you create a ticket using our support form and we can look into it further, if already created one, our supoort team is already at it.

    Kind regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @mayflowercruisesandtours,

    Thanks for reaching out!

    ACF allows you to structure and store this complex data (like pricing and date grids), but it does not include a native frontend search engine or filtering system. While standard WordPress search can be extended to include custom fields via code, building a faceted search interface (filtering by price, date, etc.) typically requires either custom development using WP_Query or integration with a dedicated search solution.

    Could you please reach out to us directly via a Support Ticket? This will allow us to look at your specific data structure and offer more tailored advice on the best way to achieve this for your project.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @koupmi,

    Thanks for writing in.

    Because a definitive solution requires a closer look at your site, we’d love to help you investigate this further. Please can you create a ticket using our support form, and our team can provide more direct assistance.

    Kind regards,
    Pat.

    Plugin Support ACF Support

    (@acfsupport)

    Hi @maxguerra,

    Thanks for reaching out.

    ACF is primarily designed for data storage and modeling, so it does not include native features to generate frontend search filters or sidebar widgets. To use a specific custom field as a functional filter in your sidebar, you would generally need to use a dedicated filtering plugin that integrates with ACF, or write a custom widget using WP_Query and meta_query.

    Since this forum is generally for user-to-user assistance, please create a ticket using our ​support form so that we can help you implement this further.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @mabfahad,

    Thanks for the detailed report and stack trace.

    You are spot on with your analysis, this error almost always occurs when a custom function or filter passes an Array (instead of a String or Integer) as the $selector or $post_id argument to an ACF function like get_field() or get_value(). While previous PHP versions handled this loosely, PHP 8 throws a fatal error immediately when an illegal offset type is used.

    Since this forum is generally for user-to-user assistance, please create a ticket using our ​support form so that we can help you investigate and implement this further.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @morenoma,

    Thanks for reaching out.

    The most reliable way to sync ACF values into WooCommerce Order meta, whether from a Product, a User, or a custom checkout field, is to hook into the woocommerce_checkout_update_order_meta action. This hook fires immediately after an order is created, giving you access to the $order_id.

    Inside this hook, you can retrieve the source value (using get_field() on the source ID or accessing the $_POST data) and then save it to the order using update_field( 'field_name', $value, $order_id );. Saving the data explicitly to the Order ID ensures it persists as standard order meta, which makes it automatically accessible to the WooCommerce REST API, export plugins, and the admin order details screen: update_field()

    Since this forum is generally for user-to-user assistance, please create a ticket using our ​support form so that we can help you investigate and implement this further.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi Guido,

    ACF Support Team here. This forum is generally used by ACF users to help each other out.

    However, we would love to continue investigating and troubleshooting this issue, please can you create a ticket using our ​support form and we can look into it further.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @24jobs,

    Thanks for reaching out, I trust you’re keeping safe!

    For scalability and integration with FacetWP, utilizing Taxonomies is generally the superior choice over standard Field Groups for any data you intend to filter by. Taxonomies benefit from optimized database tables that offer significantly faster query performance for filtering and faceted search, whereas relying heavily on meta-based queries (Custom Fields) can become resource-intensive as your dataset grows. You can use a hybrid approach, using Taxonomies for filtering and ACF Fields for unique content display, but if you’d like us to review your specific data structure to ensure optimal performance, please create a ticket using our ​support form.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @callmejud,

    Thanks for writing in, I trust you’re keeping safe!

    This inconsistency, where terms are checked in the editor but missing from the admin column, often suggests a caching conflict or a need to recount terms, but since this forum is generally for user-to-user assistance, please create a ticket using our ​support form so that we can help you investigate further and resolve this visibility issue.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @legion_x,

    The Prefix and Suffix settings in the ACF Field configuration are primarily designed for the WordPress Admin interface to guide content editors; they aren’t automatically appended to the value on the frontend. To display them, you would typically output the unit manually in your template (e.g., echo get_field('length') . ' meters';) or use the get_field_object() function to retrieve the suffix setting dynamically.

    Since this forum is generally for user-to-user assistance, please create a ticket using our ​support form so that we can help you investigate and implement this further.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @24jobs,

    Thanks for opening this discussion! This is a fantastic question and one that many developers are navigating as the WordPress ecosystem evolves.

    Yes, ACF and Gutenberg play very well together. In fact, for many developers, combining them is the “gold standard” workflow for modern WordPress development.

    Here is how we see the landscape for 2026:

    The Hybrid Approach (ACF Blocks): You don’t have to choose between “ACF” and “Gutenberg.” With ACF PRO, you can build ACF Blocks. This allows you to create fully custom, reusable blocks using the same PHP and ACF fields you already know, without needing to learn React or complex JavaScript. This is the “hybrid” solution you mentioned; it uses Gutenberg for the visual editor experience while using ACF for data management and templating.

    Flexible Content vs. Blocks: In the past, the Flexible Content field was the primary way to build modular layouts. While it is still fully supported and widely used, ACF Blocks are often the better choice for new builds. They provide a true “What You See Is What You Get” preview in the editor, which clients usually prefer over the abstract “form-based” list of the Flexible Content field.

    Is the “Classic” way still valid?: Absolutely. If your project requires a rigid data-entry interface where the design should not be manipulated by the user, the Classic Editor + ACF combo remains a valid and supported method. However, if you want to future-proof your sites and give clients a modern editing experience, ACF Blocks is the perfect bridge to jump into Gutenberg without abandoning your existing PHP skills.

    Best regards,
    Pat

    Plugin Support ACF Support

    (@acfsupport)

    Hi @cobrains,

    Thanks for writing in, and apologies for the delayed response.

    Because a definitive solution requires a closer look at your site, we’d love to help you investigate this further. Please can you create a ticket using our support form, and our team can provide more direct assistance.

    Kind regards,

    Pat.

    Plugin Support ACF Support

    (@acfsupport)

    Hello @one3rdnerd,

    Thank you for reaching out for assistance, and apologies for the late response.

    We’d like to investigate this further. Could you please create a ticket using our ​support form to allow us to take a closer look and assist you more effectively?

    Best Wishes,
    Pat.

Viewing 15 replies - 1 through 15 (of 677 total)