secure-custom-fields
Last commit date
assets
1 year ago
includes
1 year ago
lang
1 year ago
pro
1 year ago
vendor
1 year ago
SECURITY.md
1 year ago
acf.php
1 year ago
composer.json
1 year ago
index.php
1 year ago
license.txt
1 year ago
readme.txt
11 months ago
secure-custom-fields.php
11 months ago
readme.txt
145 lines
| 1 | === Secure Custom Fields === |
| 2 | Contributors: wordpressdotorg |
| 3 | Tags: fields, custom fields, meta, scf |
| 4 | Requires at least: 6.0 |
| 5 | Tested up to: 6.8 |
| 6 | Requires PHP: 7.4 |
| 7 | Stable tag: 6.5.4 |
| 8 | License: GPLv2 or later |
| 9 | License URI: https://www.gnu.org/licenses/gpl-2.0.html |
| 10 | |
| 11 | Secure Custom Fields boosts content management with custom fields and options. It deactivates Advanced Custom Fields to prevent duplicate code errors. |
| 12 | |
| 13 | == Description == |
| 14 | |
| 15 | Secure Custom Fields (SCF) extends WordPress’s capabilities, transforming it into a flexible content management tool. With SCF, managing custom data becomes straightforward and efficient. |
| 16 | |
| 17 | **Easily create fields on demand.** |
| 18 | The SCF builder makes it easy to add fields to WordPress edit screens, whether you’re adding a new “ingredients” field to a recipe or designing complex metadata for a specialized site. |
| 19 | |
| 20 | **Flexibility in placement.** |
| 21 | Fields can be applied throughout WordPress—posts, pages, users, taxonomy terms, media, comments, and even custom options pages—organizing your data how you want. |
| 22 | |
| 23 | **Display seamlessly.** |
| 24 | Using SCF functions, you can display custom field data in your templates, making content integration easy for all levels of developers. |
| 25 | |
| 26 | **A comprehensive content management solution.** |
| 27 | Beyond custom fields, SCF allows you to register new post types and taxonomies directly from the SCF interface, providing more control without needing additional plugins or custom code. |
| 28 | |
| 29 | **Accessible and user-friendly design.** |
| 30 | The field interface aligns with WordPress’s native design, creating an experience that’s both accessible and easy for content creators to use. |
| 31 | |
| 32 | Installing this plugin will deactivate plugins with matching function names/functionality, specifically Advanced Custom Fields, Advanced Custom Fields Pro, and the legacy Secure Custom Fields plugins, to avoid code errors (this is the same behavior as ACF Pro). |
| 33 | |
| 34 | Read more about Secure Custom Fields at [developer.wordpress.org/secure-custom-fields](https://developer.wordpress.org/secure-custom-fields/). |
| 35 | |
| 36 | = Features = |
| 37 | * Clear and easy-to-use setup |
| 38 | * Robust functions for content management |
| 39 | * Over 30 Field Types |
| 40 | |
| 41 | == Screenshots == |
| 42 | |
| 43 | 1. Add groups of custom fields. |
| 44 | 2. Easy to add custom content while writing. |
| 45 | 3. Need a new post type? Just add it! |
| 46 | 4. Navigate the various field types with ease. |
| 47 | |
| 48 | = Acknowledgement = |
| 49 | |
| 50 | This plugin builds upon and is a fork of the previous work done by the contributors of Advanced Custom Fields. Please see the plugin's license.txt for the full license and acknowledgements. |
| 51 | |
| 52 | |
| 53 | == Changelog == |
| 54 | |
| 55 | = 6.5.4 = |
| 56 | *Release Date 30 Jul 2025* |
| 57 | |
| 58 | Revert from 6.5.2. |
| 59 | |
| 60 | |
| 61 | = 6.5.2 = |
| 62 | *Release Date 31 Jul 2025* |
| 63 | |
| 64 | *Features* |
| 65 | |
| 66 | - Connect block attributes with custom fields via UI. |
| 67 | |
| 68 | |
| 69 | = 6.5.1 = |
| 70 | *Release Date 2 Jul 2025* |
| 71 | |
| 72 | *Bug Fixes* |
| 73 | |
| 74 | - Command Palette: Use `@wordpress\icons` instead of Dashicons. |
| 75 | |
| 76 | |
| 77 | = 6.5.0 = |
| 78 | *Release Date 23 Jun 2025* |
| 79 | |
| 80 | *Enhancements & Features* |
| 81 | |
| 82 | - Added Command Palette support. |
| 83 | - Added editor preview to acf-field source. |
| 84 | - Added an endpoint to retrieve the custom fields of a post type. |
| 85 | - Added nav menu as field type. |
| 86 | - Added compatibility with Woo HPOS for order fields and subscriptions. ( Ported from ACF ) |
| 87 | - Create new options when editing a fields value on Selector. ( Ported from ACF ) |
| 88 | - The “Escaped HTML” warning notice is now disabled by default. ( Ported from ACF ) |
| 89 | - Added new `acf/fields/icon_picker/{tab_name}/icons` filter ( Ported from ACF ) |
| 90 | |
| 91 | *Bug Fixes* |
| 92 | |
| 93 | - Update initialization of the acfL10n object to ensure it's available globally. |
| 94 | - SCF Blocks are now forced into preview mode when editing a synced pattern. ( Ported from ACF ) |
| 95 | - SCF no longer causes an infinite loop in bbPress when editing replies. ( Ported from ACF ) |
| 96 | - Changing a field type no longer enables the “Allow Access to Value in Editor UI” setting. ( Ported from ACF ) |
| 97 | - Blocks registered via acf_register_block_type() with a `parent` value of `null` no longer fail to register. ( Ported from ACF ) |
| 98 | - Fix AJAX repeater pagination. ( Ported from ACF ) |
| 99 | - Paginated Repeater fields no longer save duplicate values when saving to a WooCommerce Order with HPOS disabled ( Ported from ACF ) |
| 100 | |
| 101 | *Testing* |
| 102 | |
| 103 | - Added an initial batch of e2e tests. |
| 104 | |
| 105 | = 6.4.2 = |
| 106 | *Release Date 14 Apr 2025* |
| 107 | |
| 108 | * Resolved issue with shortcode translation not parsing correctly. |
| 109 | * Improve validation for an URL on field admin. |
| 110 | |
| 111 | = 6.4.1 = |
| 112 | *Release Date 7 Mar 2025* |
| 113 | |
| 114 | * Forked from Advanced Custom Fields® |
| 115 | * Various updates to coding standards. |
| 116 | * Updated to rely on the WordPress.org translation packs for all strings. |
| 117 | |
| 118 | = 6.3.9 = |
| 119 | *Release Date 22nd October 2024* |
| 120 | |
| 121 | * Version update release |
| 122 | |
| 123 | = 6.3.6.3 = |
| 124 | *Release Date 15th October 2024* |
| 125 | |
| 126 | * Security - Editing a Field in the Field Group editor can no longer execute a stored XSS vulnerability. Thanks to Duc Luong Tran (janlele91) from Viettel Cyber Security for the responsible disclosure |
| 127 | * Security - Post Type and Taxonomy metabox callbacks no longer have access to any superglobal values, hardening the original fix from 6.3.6.2 even further |
| 128 | * Fix - SCF Fields now correctly validate when used in the block editor and attached to the sidebar |
| 129 | |
| 130 | = 6.3.6.2 = |
| 131 | *Release Date 12th October 2024* |
| 132 | |
| 133 | * Security - Harden fix in 6.3.6.1 to cover $_REQUEST as well. |
| 134 | * Fork - Change name of plugin to Secure Custom Fields. |
| 135 | |
| 136 | = 6.3.6.1 = |
| 137 | *Release Date 7th October 2024* |
| 138 | |
| 139 | * Security - SCF defined Post Type and Taxonomy metabox callbacks no longer have access to $_POST data. (Thanks to the Automattic Security Team for the disclosure) |
| 140 | |
| 141 | == Upgrade Notice == |
| 142 | |
| 143 | = 6.4.2 = |
| 144 | Security: improves validation of an URL in an admin field. |
| 145 |