Advanced Custom Fields

This is an excellent addition to the plugin in 6.8 Beta 2, thankyou. We were actually in the process of creating our own JSON-LD embed for custom post types, so nice to know this is coming in a future release. I've been testing the feature locally and it's excellent. However on some of our post types, some fields contain internal/administrative data that shouldn't appear in the public JSON-LD output (e.g., CRM IDs, internal notes, admin-only flags). We found a workaround: Using the acf/schema/data filter to manually remove fields from the final JSON-LD output: add_filter('acf/schema/data', function($data) { $exclude = ['internal_id', 'internal_notes']; foreach ($data['additionalProperty'] as $key => $prop) { if (isset($prop['value']) && is_array($prop['value'])) { foreach ($exclude as $field_name) { unset($data['additionalProperty'][$key]['value'][$field_name]); } } } return $data; }); wondering if there is a plan to exclude fields from the UI?

Similar to https://github.com/hirasso/focal-point-picker , add a focal point picker for images when adding them via an image or gallery field. Output the relevant coordinates in the image array or via wp_get_attachment_image.

It is a common use case to make sure a preview of an ACF block does not appear in the editor. This may be for many reasons - e.g. complex blocks that only work in certain contexts, or simply because it results in a large output and makes it harder for admin to edit. This has been enforceable by using mode:edit and support {mode:false} - and potentially not including preview CSS in the back-end at all. When clients upgrade to WP 7 and the iframe is enforced, undesired previews will start appearing for these blocks, resulting in a huge visual (and often broken layout) change. This was already noticed before ACF v3 blocks were released, e.g. when people started noticing unwanted previews when editing block patterns. I have been resolving this when developing ACF v3 blocks by adding code like this to the top of every block: ```if ($is_preview) { ?> <div class="customblockpreview"> <p><?php echo $block['title']; ?> block</p> <p>Click pencil icon to edit.</p> </div> <?php return; }``` and just styling this to be a plain bordered box in the editor. However, I have developed many, many sites in the past with custom ACF blocks where this code won't be in place. Can you consider adding something similar by default - adding a preview-less option for v3 blocks, and then applying this by default if the deprecated mode:edit setting was applied? This will result in a much similar experience to what people are used to, vs repeated error reports upgrading to WP 7.

We have a few clients who have left WP Engine hosting and let their accounts get suspended. Everytime I log in I have a big pink box showing their status at the top of my page. We are not affiliated with those companies anymore, and should be able to remove ourselves from their accounts. We should be able to remove ourselves from any account we need to, including accounts we simply no longer work with, and especially accounts that don't have an active plan. It seems like this used to be an option.

Hi team, When I use a Repeater within a Conditional Logic field, I encounter a bug where the data is moved from the first row to the second row. These are the steps to reproduce the bug: Create a Repeater field within 3 child fields including these types - Name -> Text - Use Phone? -> True/False - Phone -> Text + Conditional Logic (this field is only displayed if the "Use Phone?" field has checked) Add 2 rows with these values - The first row: - Name: Michael - Use phone?: checked - Phone: 0123456 - The second row: - Name: Sara - Use phone?: leave blank - Phone: leave blank Save 2 rows and see the browser reload again Delete the first row and save again. Check to the checkbox of "Use Phone?" field, you will see the value of Michael's phone now belongs to the Sara Wordpress version: 6.7 ACF version: 6.7.0.2 (latest version) When I test this, I only enable the ACF plugin. PLEASE SEE MY ATTACHED VIDEO FOR MORE DETAIL

Hi, are you planning to make a MCP support ? Since it's really good to use LLM to make the first .json for a new component and that's work great, it's gonna be a huge improvement to add a mcp for your app !

If I need to add a list of CPT or repeater subfield values to a template I'll ask AI to write the loop for me. I have on occasion taken a screen shot of the fields/subfields and told it to use them. It would be great to be able to paste a plain text list of the fields/subfields (all or selected ones) instead of the a screenshot.

Ever needed to add the same social media link fields that are on the Contact page to a CPT single? Being able to check the selected fields in a field group, batch duplicate them, select the duplicates and then batch move them to the same other field group would save a lot of time.

Instead of storing field data in the post meta table, store the field values in a custom database table. This reduced performance issues and makes the data easier to query.