--- title: ACF 6.8.6 | daily.dev description: Advanced Custom Fields (ACF) version 6.8.6 is now available. This release is a bug-fix update addressing seven issues: Google Maps field values being... canonical: https://daily.dev/posts/acf-6-8-6-gn9zh0dnt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: ACF 6.8.6 | daily.dev og:description: Advanced Custom Fields (ACF) version 6.8.6 is now available. This release is a bug-fix update addressing seven issues: Google Maps field values being... og:url: https://daily.dev/posts/acf-6-8-6-gn9zh0dnt og:image: https://api.daily.dev/og/posts/gN9zH0dnt.png og:image:alt: ACF 6.8.6 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # ACF 6.8.6 **[ACF](https://daily.dev/sources/acf)** · 1 min read · 10 upvotes · 0 comments ## Summary Advanced Custom Fields (ACF) version 6.8.6 is now available. This release is a bug-fix update addressing seven issues: Google Maps field values being double-encoded in ACF blocks, Link field insertion triggering premature validation in the Classic Editor, Auto Inline Editing blocks returning incorrect placeholder strings for empty fields from other posts, ACF Blocks crashing when rendering oEmbed fields with titles starting with '[' or '{', PHP warnings from field group location rules without a value, visual appearance fixes for URL/Number/Select fields on WordPress 7.0+, and ACF fields failing to save on WooCommerce orders when using HPOS in compatibility mode. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Does ACF 6.8.6 fix the WooCommerce HPOS compatibility mode issue with saving custom fields on orders? Yes, ACF 6.8.6 fixes a bug where ACF fields did not save on WooCommerce orders when using High-Performance Order Storage (HPOS) in compatibility mode. This was one of several fixes in the release, alongside corrections to Google Maps field encoding, Link field validation in the Classic Editor, and an oEmbed field crash in ACF Blocks V2 and V3. _Teams running WooCommerce with HPOS can track ACF patch notes like this on daily.dev before upgrading._ ### Why do my ACF oEmbed fields crash ACF Blocks when the title starts with a curly brace or bracket? This was a bug in ACF Blocks (V2 and V3) prior to version 6.8.6, where rendering an oEmbed field whose title began with [ or { caused a crash. The issue is fixed in ACF 6.8.6, so upgrading to that version resolves the crash without requiring a workaround in the block render template. _daily.dev helps developers debugging plugin crashes surface fixes like this ACF Blocks patch quickly._ ### Does upgrading to WordPress 7.0 change how ACF's URL, Number, and Select fields look? Yes, ACF 6.8.6 improves the appearance of the URL, Number, and Select fields specifically on WordPress 7.0 and later, addressing visual issues introduced by that WordPress version. This fix ships alongside several other bug corrections in the same ACF release. _Plugin maintainers tracking WordPress 7.0 compatibility fixes can follow releases like this via daily.dev._ ## Similar posts on daily.dev - [ACF 6.8.4](https://daily.dev/posts/acf-6-8-4-1x216pqj3) · ACF · 4 upvotes · 0 comments - [ACF 6.8.5 Security Release](https://daily.dev/posts/acf-6-8-5-security-release-5smwnw8lp) · ACF · 3 upvotes · 2 comments - [ACF 6.8.8](https://daily.dev/posts/acf-6-8-8-buyci7n4v) · ACF · 3 upvotes · 0 comments - [ACF 6.6.1](https://daily.dev/posts/acf-6-6-1-oq783mdab) · ACF · 23 upvotes · 0 comments - [ACF 6.6.2](https://daily.dev/posts/acf-6-6-2-3qmpbxiak) · ACF · 10 upvotes · 0 comments --- Tags: [#php](https://daily.dev/tags/php), [#wordpress](https://daily.dev/tags/wordpress), [#woocommerce](https://daily.dev/tags/woocommerce) [View this post on daily.dev](https://daily.dev/posts/acf-6-8-6-gn9zh0dnt) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"ACF 6.8.6","url":"https://daily.dev/posts/acf-6-8-6-gn9zh0dnt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/acf-6-8-6-gn9zh0dnt"},"datePublished":"2026-07-14T21:01:04.946Z","dateModified":"2026-09-14T08:14:39.959Z","description":"Advanced Custom Fields (ACF) version 6.8.6 is now available. This release is a bug-fix update addressing seven issues: Google Maps field values being...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/48dddd9dc98754e817d0dfb1f6f232c6?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/48dddd9dc98754e817d0dfb1f6f232c6?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ACF","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ACF","logo":"https://media.daily.dev/image/upload/s---s882O9i--/f_auto/v1741896667/logos/acf","url":"https://daily.dev/sources/acf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/acf-6-8-6-gn9zh0dnt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":10},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"php,wordpress,woocommerce","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ACF","item":"https://daily.dev/sources/acf"},{"@type":"ListItem","position":3,"name":"ACF 6.8.6"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/acf-6-8-6-gn9zh0dnt#faq","mainEntity":[{"@type":"Question","name":"Does ACF 6.8.6 fix the WooCommerce HPOS compatibility mode issue with saving custom fields on orders?","acceptedAnswer":{"@type":"Answer","text":"Yes, ACF 6.8.6 fixes a bug where ACF fields did not save on WooCommerce orders when using High-Performance Order Storage (HPOS) in compatibility mode. This was one of several fixes in the release, alongside corrections to Google Maps field encoding, Link field validation in the Classic Editor, and an oEmbed field crash in ACF Blocks V2 and V3. Teams running WooCommerce with HPOS can track ACF patch notes like this on daily.dev before upgrading."}},{"@type":"Question","name":"Why do my ACF oEmbed fields crash ACF Blocks when the title starts with a curly brace or bracket?","acceptedAnswer":{"@type":"Answer","text":"This was a bug in ACF Blocks (V2 and V3) prior to version 6.8.6, where rendering an oEmbed field whose title began with [ or { caused a crash. The issue is fixed in ACF 6.8.6, so upgrading to that version resolves the crash without requiring a workaround in the block render template. daily.dev helps developers debugging plugin crashes surface fixes like this ACF Blocks patch quickly."}},{"@type":"Question","name":"Does upgrading to WordPress 7.0 change how ACF's URL, Number, and Select fields look?","acceptedAnswer":{"@type":"Answer","text":"Yes, ACF 6.8.6 improves the appearance of the URL, Number, and Select fields specifically on WordPress 7.0 and later, addressing visual issues introduced by that WordPress version. This fix ships alongside several other bug corrections in the same ACF release. Plugin maintainers tracking WordPress 7.0 compatibility fixes can follow releases like this via daily.dev."}}]} ```