Hello, I use ACF Extended plugin (Advanced Custom Fields: Extended – WordPress plugin | WordPress.org) to implement Options Pages and more specific custom type fileds, but when i try to display them in any element, they don’t display, not even in the list of ACF fields.
Even when i manually enter them, they don’t display in the front end.
Do you know how i can implement them to my site ?
1 Like
Currently ACF support in Bricks is limited. I am including a link that might help clarify the current dynamic data types currently supported by Bricks.
Most if not all advanced data types are NOT supported yet.
Standard WordPress data
By default, you may use the following dynamic data tags.
Post fields
The following fields are related to the posts or custom post types.
{post_title} – Returns the post title
{post_id} – Returns the post ID
{post_url} – Returns the post URL
{post_date} – Returns post published date
{post_modified} – Returns post modified date
{post_time} – Returns post publish time
{post_comments_count} – Returns number of comments
{post_content} – Returns post content (Gutenberg editor)
{post_excerpt} – Returns the post excerpt
{read_more} – Renders an anchor tag (link) to the post with the label “Read more”
{featured_image} – Renders an image tag with the featured image
These fields support dynamic data filters, like the following:
{post_title:link} – Renders the post title as a link to the post
{post_title:link:3} – Same as before but the title is limited to 3 words
{post_excerpt:55} – Limit post excerpt to 55 words. Using the “:” followed by a number limits the output to that number of words
{featured_image:medium_large} – Renders an image tag with the featured image of size medium_large (defaults to thumbnail size)
{featured_image:large:link} – Renders an image tag with the featured image of size large wrapped by an anchor tag to the post
Taxonomies
The following dynamic data tags render lists of the taxonomy terms assigned to a post.
{post_terms_category}
{post_terms_post_tag}
{post_terms_my_taxonomy_slug}
Terms
The following dynamic data tags render data related to taxonomy terms.
{term_id} – Renders the term ID
{term_name} – Renders the term name
{term_url} – Renders the term archive link
{term_description} – Renders the term description
{term_meta:my_term_meta_key} – Renders the “my_term_meta_key” meta value
Author Fields
{author_name} – Returns the post author name
{author_bio} – Returns the post author biographical info
{author_email} – Returns the post author email
{author_website} – Returns the post author website
{author_avatar} – Returns the post author avatar as an image tag (text) or an image url (link)
These fields support dynamic data filters, like the following:
{author_bio:20} – Post author biographical info limited to 20 words
{author_email:link} – Post author email rendered as a link
{author_website:link} – Post author website rendered as a link
{author_avatar:200} – Post author avatar image tag limited to the width/height of 200px
Current Date fields
You can render the current date through dynamic data.
{current_date} – Returns the current date with the format defined at WordPress > Settings > General > Date Format
You may specify a different date format using the PHP date format, for example:
{current_date:Y}
{current_date:Ymd}
{current_date:Y-m-d}
{current_date:Y.m.d}
{current_date:Y/m/d}
{current_date:Y m d}
{current_date:g:i A}
Site & Archive fields
{site_title} – Returns site title as defined in the WordPress settings > General > Site Title
{site_tagline} – Returns site tagline as defined in the WordPress settings > General > Tagline
{archive_title} – Returns archive title
{archive_title:context} – Add context to the archive title
{archive_description} – Returns archive description (author, post type or term)
Since Bricks 1.3.5, it is possible to get dynamic data from the URL parameters like so:
{url_parameter:my_key} – Returns the value of the my_key parameter in the url (The domain name mydomain.pt is for sale)
User profile fields
{wp_user_id} – Returns logged in user ID
{wp_user_login} – Returns logged in user username
{wp_user_email} – Returns logged in user email address
{wp_user_url} – Returns logged in user website
{wp_user_nicename} – Returns logged in user nicename
{wp_user_description} – Returns logged in user biographical info
{wp_user_first_name} – Returns logged in user first name
{wp_user_last_name} – Returns logged in user last name
{wp_user_display_name} – Returns logged in user display name
{wp_user_picture} – Returns logged in user avatar image tag or url
{wp_user_meta:my_user_meta_key} – Returns logged in user “my_user_meta_key” meta value
This is the standard WP data.
I am talking about ACF Extended data types.
If Bricks supports shortcodes in the inputs you use, you can build your own shortcodes for ACFE and use them here.
I don’t know how to do that and i wish NOT to learn it.
Can someone verify with me if ACF Extended is supported or not?
If not i have to find another way to implement what i want to do.
Hi Yannis,
Which ACF Extended fields are you having problems with? With all or specific fields?
Best regards,
timmse
I haven’t tried them all, but “phone number” is one.
Ah ok,
if it’s an ACF Extended field, it’s currently not supported. We support most of the regular ACF, Pods, Metabox… fields. Would you be so kind to add ACF Extended support as an idea to the board?
Best regards,
timmse
Already submitted it few hours ago 
1 Like
I tried to tell you, they only support very basic fields. There are numerous request for full dynamic data support but it is not a priority yet, sadly as other features have been more upvoted. 90 percent of my sites and my work is with dynamic data, so believe me I follow this topic closely. This products support for truly dynamic site and dynamic content is far from being ready.