|
1 | 1 | # Advanced Custom Fields PRO |
2 | 2 |
|
3 | | -**Advanced Custom Fields Pro** (ACF Pro) is a popular WordPress plugin that allows developers to easily create custom fields and content for their websites. **This is the fully activated pro version, which has been thoroughly checked for malware and is safe to use.** However, using cracked software may violate the original author's licensing terms and may not receive official support or updates. |
| 3 | +   |
| 4 | + |
| 5 | +**Advanced Custom Fields Pro** (ACF Pro) is a popular WordPress plugin that allows developers to create custom fields and content for their websites easily. **This is the fully activated [pro version](https://www.advancedcustomfields.com/pro/), which has been thoroughly checked for malware and is safe to use for research purposes.** |
| 6 | + |
| 7 | +**Note:** Using activated software may violate the original author's licensing terms and may not receive official support or updates. |
4 | 8 |
|
5 | 9 | **If you appreciate this service and would like to keep getting recent, malware-free updates, please consider [leaving a tip via PayPal](https://www.paypal.com/paypalme/thaikolja).** |
6 | 10 |
|
7 | 11 | ## Changelog |
8 | 12 |
|
9 | | -### v6.3.0.1 |
10 | | - |
11 | | -**Release Date:** 22nd May 2024 - PRO Only Release |
12 | | - |
13 | | -* **Fix** - A possible fatal error no longer occurs in the new site health functionality for ACF PRO users |
14 | | -* **Fix** - A possible undefined index error no longer occurs in ACF Blocks for ACF PRO users |
15 | | - |
16 | | - |
17 | | -### v6.3.0 |
18 | | - |
19 | | -**Release Date:** 22nd May 2024 |
20 | | - |
21 | | -* **New** - ACF now requires WordPress version 6.0 or newer, and PHP 7.4 or newer. |
22 | | -* **New** - ACF Blocks now support validation rules for fields. View the release notes for more information |
23 | | -* **New** - ACF Blocks now supports storing field data in the postmeta table rather than in the post content |
24 | | -* **New** - Conditional logic rules for fields now support selecting specific values for post objects, page links, taxonomies, relationships and users rather than having to enter the ID |
25 | | -* **New** - New Icon Picker field type for ACF and ACF PRO |
26 | | -* **New** - Icon selection for a custom post type menu icon |
27 | | -* **New** - Icon selection for an options page menu icon |
28 | | -* **New** - ACF now surfaces debug and status information in the WordPress Site Health area |
29 | | -* **New** - The escaped html notice can now be permanently dismissed |
30 | | -* **Enhancement** - Tab field now supports a selected attribute to specify which should be selected #by default, and support class attributes |
31 | | -* **Fix** - Block Preloading now works reliably in WordPress 6.5 or newer |
32 | | -* **Fix** - Select2 results loaded by AJAX for post object fields no longer double encode HTML entities |
33 | | -* **Fix** - Custom post types registered with ACF will now have custom field support enabled by default to better support revisions |
34 | | -* **Fix** - The first preview after publishing a post in the classic editor now displays ACF fields correctly |
35 | | -* **Fix** - ACF fields and Flexible Content layouts are now correctly positioned while dragging |
36 | | -* **Fix** - Copying the title of a field inside a Flexible Content layout no longer adds whitespace to the copied value |
37 | | -* **Fix** - Flexible Content layout names are no longer converted to lowercase when edited |
38 | | -* **Fix** - ACF Blocks with attributes without a default now correctly register |
39 | | -* **Fix** - User fields no longer trigger a 404 when loading results if the nonce generated only contains numbers |
40 | | -* **Fix** - Description fields for ACF items now support being solely numeric characters |
41 | | -* **Fix** - The field group header no longer appears above the WordPress admin menu on small screens |
42 | | -* **Fix** - The acf/json/save_file_name filter now correctly applies when deleting JSON files |
43 | | -* **i18n** - All errors raised during ACF PRO license or update checks are now translatable |
44 | | -* **Other** - The ACF Shortcode is now disabled by default for new installations of ACF as discussed in the ACF as discussed in the ACF |
| 13 | +### v6.3.4 (latest) |
| 14 | + |
| 15 | +**Release Date:** 18th July 2024 |
| 16 | + |
| 17 | +* **Security Fix** - The ACF shortcode now prevents access to fields from different private posts by default. View the [release notes](https://www.advancedcustomfields.com/blog/acf-6-3-4) for more information |
| 18 | +* **Fix** - Users without the `edit_posts` capability but with custom capabilities for editing a custom post type can now correctly load field groups loaded via conditional location rules |
| 19 | +* **Fix** - Block validation no longer validates a field’s sub-fields on page load, only on edit. This resolves inconsistent validation errors on page load or when first adding a block |
| 20 | +* **Fix** - Deactivating an ACF PRO license will now remove the license key even if the server call fails |
| 21 | +* **Fix** - Field types returning objects no longer cause PHP warnings and errors when output via `the_field`, `the_sub_field`, or the ACF shortcode, or when retrieved by a `get_` function with the escape html parameter set |
| 22 | +* **Fix** - Server-side errors during block rendering now gracefully display an error to the editor |
| 23 | + |
| 24 | +--- |
| 25 | + |
| 26 | +For changelogs of older versions, check the [official website](https://www.advancedcustomfields.com/changelog/). |
0 commit comments