=== Advanced Custom Fields (ACF) === Contributors: deliciousbrains, wpengine, elliotcondon, mattshaw, lgladdy, antpb, andrewbotz, dalewilliams, polevaultweb Tags: acf, fields, custom fields, meta, repeater Requires at least: 5.8 Tested up to: 6.5 Requires PHP: 7.0 Stable tag: 6.2.9 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Advanced Custom Fields (ACF) helps you easily customize WordPress with powerful, professional and intuitive fields. Proudly powering over 2 million websites, Advanced Custom Fields is the plugin WordPress developers love. == Description == Advanced Custom Fields (ACF) turns WordPress sites into a fully-fledged content management system by giving you all the tools to do more with your data. Use the ACF plugin to take full control of your WordPress edit screens, custom field data, and more. **Add fields on demand.** The ACF field builder allows you to quickly and easily add fields to WP edit screens with only the click of a few buttons! Whether it's something simple like adding an “author” field to a book review post, or something more complex like the structured data needs of an ecommerce site or marketplace, ACF makes adding fields to your content model easy. **Add them anywhere.** Fields can be added all over WordPress including posts, pages, users, taxonomy terms, media, comments and even custom options pages! It couldn't be simpler to bring structure to the WordPress content creation experience. **Show them everywhere.** Load and display your custom field values in any theme template file with our hassle-free, developer friendly functions! Whether you need to display a single value or generate content based on a more complex query, the out-of-the-box functions of ACF make templating a dream for developers of all levels of experience. **Any Content, Fast.** Turning WordPress into a true content management system is not just about custom fields. Creating new custom post types and taxonomies is an essential part of building custom WordPress sites. Registering post types and taxonomies is now possible right in the ACF UI, speeding up the content modeling workflow without the need to touch code or use another plugin. **Simply beautiful and intentionally accessible.** For content creators and those tasked with data entry, the field user experience is as intuitive as they could desire while fitting neatly into the native WordPress experience. Accessibility standards are regularly reviewed and applied, ensuring ACF is able to empower as close to anyone as possible. **Documentation and developer guides.** Over 10 plus years of vibrant community contribution alongside an ongoing commitment to clear documentation means that you'll be able to find the guidance you need to build what you want. = Features = * Simple & Intuitive * Powerful Functions * Over 30 Field Types * Extensive Documentation * Millions of Users = Links = * [Website](https://www.advancedcustomfields.com/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Website) * [Documentation](https://www.advancedcustomfields.com/resources/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Website) * [Support](https://support.advancedcustomfields.com) * [ACF PRO](https://www.advancedcustomfields.com/pro/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Pro%20Upgrade) = PRO = The Advanced Custom Fields plugin is also available in a professional version which includes more fields, more functionality, and more flexibility. The ACF PRO plugin features: * The [Repeater Field](https://www.advancedcustomfields.com/resources/repeater/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Pro%20Upgrade) allows you to create a set of sub fields which can be repeated again, and again, and again. * [ACF Blocks](https://www.advancedcustomfields.com/resources/blocks/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Pro%20Upgrade), a powerful PHP-based framework for developing custom block types for the WordPress Block Editor (aka Gutenberg). * Define, create, and manage content with the [Flexible Content Field](https://www.advancedcustomfields.com/resources/flexible-content/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Pro%20Upgrade), which provides for multiple layout and sub field options. * Use the [Options Page](https://www.advancedcustomfields.com/resources/options-page/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Pro%20Upgrade) feature to add custom admin pages to edit ACF fields. * Build fully customisable image galleries with the [Gallery Field](https://www.advancedcustomfields.com/resources/gallery/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Pro%20Upgrade). * Unlock a more efficient workflow for managing field settings by reusing existing fields and field groups on demand with the [Clone Field](https://www.advancedcustomfields.com/resources/clone/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Pro%20Upgrade). [Upgrade to ACF PRO](https://www.advancedcustomfields.com/pro/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Pro%20Upgrade) == Installation == From your WordPress dashboard 1. **Visit** Plugins > Add New 2. **Search** for "Advanced Custom Fields" or “ACF” 3. **Install and Activate** Advanced Custom Fields from your Plugins page 4. **Click** on the new menu item "ACF" and create your first custom field group, or register a custom post type or taxonomy. 5. **Read** the documentation to [get started](https://www.advancedcustomfields.com/resources/getting-started-with-acf/?utm_source=wordpress.org&utm_medium=free%20plugin%20listing&utm_campaign=ACF%20Website) == Frequently Asked Questions == = What kind of support do you provide? = **Support Forums.** Our ACF Community Forums provide a great resource for searching and finding previously answered and asked support questions. You may create a new thread on these forums, however, it is not guaranteed that you will receive an answer from our support team. This is more of an area for ACF developers to talk to one another, post ideas, plugins and provide basic help. [View the Support Forum](https://support.advancedcustomfields.com/) == Screenshots == 1. Simple & Intuitive 2. Made for Developers 3. All About Fields 4. Registering Custom Post Types 5. Registering Taxonomies == Changelog == = 6.2.9 = *Release Date 8th April 2024* * Enhancement - The Select2 escapeMarkup function can now be overridden when initializing a custom Select2 * Fix - “Hide on Screen” settings are now correctly applied when using conditionally loaded field groups * Fix - Field names are no longer converted to lowercase when editing the name * Fix - Field group titles will no longer convert HTML entities into their encoded form = 6.2.8 = *Release Date 2nd April 2024* * New - Support for the Block Bindings API in WordPress 6.5 with a new `acf/field` source. For more information on how to use this, please read [the release blog post](https://www.advancedcustomfields.com/blog/acf-6-2-8) * New - Support for performance improvements for translations in WordPress 6.5 * Enhancement - A new JS filter, `select2_escape_markup` now allows fields to customize select2's HTML escaping behavior * Fix - Options pages can no longer set to have a parent of themselves * Fix - ACF PRO license activations on multisite subsite installs will now use the correct site URL * Fix - ACF PRO installed on multisite installs will no longer try to check for updates resulting in 404 errors when the updates page is not visible * Fix - ACF JSON no longer produces warnings on Windows servers when no ACF JSON folder is found * Fix - Field and layout names can now contain valid non-ASCII characters * Other - ACF PRO now requires a valid license to be activated in order to use PRO features. [Learn more](https://www.advancedcustomfields.com/resources/license-activations/) = 6.2.7 = *Release Date 27th February 2024* * Security Fix - `the_field` now escapes potentially unsafe HTML as notified since ACF 6.2.5. For full information, please read [the release blog post](https://www.advancedcustomfields.com/blog/acf-6-2-7-security-release/) * Security Fix - Field and Layout names are now enforced to alphanumeric characters, resolving a potential XSS issue * Security Fix - The default render template for select2 fields no longer allows HTML to be rendered resolving a potential XSS issue * Security Enhancement - A `acf/shortcode/prevent_access` filter is now available to limit what data the ACF shortcode is allowed to access * Security Enhancement - i18n translated strings are now escaped on output * Enhancement - ACF now universally uses WordPress file system functions rather than native PHP functions = 6.2.6.1 = *Release Date 7th February 2024* * Fix - Fatal JS error no longer occurs when editing fields in the classic editor when Yoast or other plugins which load block editor components are installed * Fix - Using `$escape_html` on get functions for array returning field types no longer produces an Array to string conversion error = 6.2.6 = *Release Date 6th February 2024* * Enhancement - The `get_field()` and other `get_` functions now support an `escape_html` parameter which return an HTML safe field value * Enhancement - The URL field will be now escaped with `esc_url` rather than `wp_kses_post` when returning an HTML safe value * Fix - ACF fields will now correctly save into the WordPress created revision resolving issues with previews of drafts on WordPress 6.4 or newer * Fix - Multisite subsites will now correctly be activated by the main site where the ACF PRO license allows, hiding the updates page on those subsites * Fix - Field types in which the `required` property would have no effect (such as the tab, or accordion) will no longer show the option * Fix - Duplicating a field group now maintains the current page of field groups being displayed * Fix - Fields in ACF Blocks in edit mode in hybrid themes will now use ACF's styling, rather than some attributes being overridden by the theme * Fix - Text in some admin notices will no longer overlap the dismiss button * Fix - The word `link` is now prohibited from being used as a CPT name to avoid a WordPress core conflict * Fix - Flexible content layouts can no longer be duplicated over their maximum count limit * Fix - All ACF notifications shown outside of ACF's admin screens are now prefixed with the plugin name * Fix - ACF no longer checks if a polyfill is needed for