This does appear to be a bug because all ACF relationship type fields expect that the stored array will be an array of stings for the ID values.
The developers do not monitor this forum for bugs. Yes, I know the forum title says “Bug Reports” but this was created many, many years ago when the developer managed this forum.
You should contact the developers directly or open a ticket under your account.
You would have to build a query to get the “posts” in the “term(s)” that you want to display. https://developer.wordpress.org/reference/classes/wp_query/
Given the information provided, if I was building something like this I would not be using a repeater to list all of the shops in a mall. I would:
Have a CPT for Malls, each mall would be a different post in this post type
Have a CPT for the stores/shops/whatever you want to call it. Each store would have it’s own post.
There would be a one-to-many bidirectional relationship between the mall and the stores. A post object field on the store post to select the mall and a relationship field on the mall post to select the stores in that mall. I would use my plugin to create this bidirectional relationship because it is beyond what the ACF relationship field can do.
I would have a custom taxonomy for selecting the type of store/shop/whatever
I would have a value in the store to indicate what floor the store is on.
If the same operator can be located in multiple malls I would also have a custom post type for this with a one-to-many relationship between the operator and store post types.
Because you are using Elementor, I would be using Elementor Pro’s theme builder and/or templates to build the templates for showing pages on this site. Using the post widget using a custom query to show the archive pages of of the various post types.
Given the information I have I don’t know any reason that the shortcodes would not work in a text widget if that text widget is use on the same page as the shortcode widdget.
The problem is that WP does not have a mechanism to do what is wanted. There might be a better approach, but I don’t really understand the purpose for the different types tags or how they are used to categorize posts.
That depends, why you you using a repeater? can you eliminate the use of the repeater?
There are ways to do this in code, but you are using elementor and you have to use things that work in both elementor and ACF. I actually surprised that you can use a repeater in elementor at all.
No, you cannot use breaks here. ACF uses the built in link editor, the same on that WP uses when you insert a link into content. The text you insert for the link title will be escaped when saving to the database and html tag characters converted to html entities. This escaping happens on saving the value and not when displaying the value.
first, where are these values saved, on the current post? options? something else?
second is the the actual text you are entering for the shortcode?
[acf field='="company"]
or was the extra =' an error when you added it here?
this should be
[acf field="company"]
No, the forms on ACF do not have any mobile responsiveness. You would have to build custom CSS and override the CSS in ACF to do this. Adding custom CSS can be done the same way that adding custom JS is done. Beyond this I don’t know what would be involved in actually making it happen.
How you do this depends on how you are building. If you are building a theme yourself then you need to add a template for “taxonomy-{$taxonomy}.php”, see WP Template Hierarchy.
If you are using a page builder then you need to see the documentation for that page builder for building an archive template.
Preventing this would be complicated.
You would need to add custom javascript to ACF and use the ACF JS API select2_ajax_data filter and include the values selected in the other fields to the AJAX request and then use an acf/fields/taxonomy/query or acf/fields/taxonomy/wp_list_categories filter to alter the the terms that are returned by the AJAX request for each field.
The classic editor is still available in WP, the plugins that restore this are not adding it, they are simply disabling the new editor. The old editor is used the the “Classic Block“. This is a tinyMCE editor and this will likely never be completely removed from WP.
The only way to do that would be to have 3 different queries for posts based on the terms selected in each of the taxonomy fields.
When you create and image or gallery field you can select if they user can select from the entire media library or only images uploaded to the specific post.
Bidirectional fields don’t work on sub fields. To do this you would need to build a custom query for elementor to get the posts. And even here I don’t think you can make it work while using a sub field of a repeater.
No, there isn’t a way to use ACF fields for only specific fields.
How are you doing this transfer? Provide details.
If you are using the gutenberg editor then this is a know issue. Field groups will not automatically update based on taxonomy term selection and the post must be updated to trigger ACF to show the correct field group. The same is probably true when setting a default term for a post.
It really depends on how you are building the table, what you are using to do this and what type of fields you are trying to retrieve values for. Provide more information.
Use a bidirectional relationship on the post object field. Using a bidirectional relationship means the you would do the same thing for the mall post that you did for the shop post.
Add a field group to “attachment” using location rules.
You need to use an acf/load_field filter for the fields you want to change. In your filter you will check the current user role and set $field['add_term'] to true or false as needed.
I don’t have any code examples.
What you need to do is create an acf/save_post action. In this action you check the value of the true/false field. If it is true then you use wp_set_post_terms() to set the term.
You will also need to check to see if the value of the true/false field is false and if the term is set for the post (wp_get_post_terms()) and again use wp_set_post_terms() to remove it.
