Title: Secure Custom Fields
Author: WordPress.org
Published: <strong>2024年11月21日</strong>
Last modified: 2026年11月11日

---

プラグインを検索

![](https://ps.w.org/secure-custom-fields/assets/banner-772x250.jpg?rev=3194494)

![](https://ps.w.org/secure-custom-fields/assets/icon.svg?rev=3194494)

# Secure Custom Fields

 作者: [WordPress.org](https://profiles.wordpress.org/wordpressdotorg/)

[ダウンロード](https://downloads.wordpress.org/plugin/secure-custom-fields.6.9.9.zip)

[ライブプレビュー](https://ja.wordpress.org/plugins/secure-custom-fields/?preview=1)

 * [詳細](https://ja.wordpress.org/plugins/secure-custom-fields/#description)
 * [レビュー](https://ja.wordpress.org/plugins/secure-custom-fields/#reviews)
 * [開発](https://ja.wordpress.org/plugins/secure-custom-fields/#developers)

 [サポート](https://wordpress.org/support/plugin/secure-custom-fields/)

## 説明

Secure Custom Fields (SCF) は WordPress の機能を拡張し、柔軟なコンテンツ管理ツール
に変身させます。SCF を使えば、カスタムデータを簡単かつ効率的に管理できます。

**必要に応じてカスタムフィールドを簡単に作成**
 レシピの材料を入力するフィールド
を追加する場合や、特殊なサイト向けに複雑なメタデータを設計する場合など、SCFビルダー
を使うと WordPress の編集画面にカスタムフィールドを簡単に追加できます。

**柔軟な配置**
 フィールドは、WordPress 全体（投稿、ページ、ユーザー、タクソノミー、
メディア、コメント、さらにはカスタムの設定ページなど）に適用できるので、データを
思い通りに整理できます。

**シームレスに表示**
 SCF 関数を使うと、テンプレート上でカスタムフィールドのデータ
を表示できるため、どんな開発者でもコンテンツを簡単に扱えます。

**包括的なコンテンツ管理ソリューション**
 カスタムフィールドだけでなく、新しい投稿
タイプやタクソノミーを SCF の画面から直接登録できるため、追加のプラグインやカスタム
コードを必要とせずに、より詳細なカスタマイズが可能になります。

**アクセシビリティ対応と使いやすいデザイン**
 フィールドインターフェースは WordPress
のネイティブデザインに沿っているため、コンテンツ制作者にとって使いやすく、アクセシビリティ
のよい体験を提供します。

このプラグインをインストールすると、コードエラーを避けるため、関数名や機能が一致
するプラグイン（具体的には Advanced Custom Fields、Advanced Custom Fields Pro、および
以前の Secure Custom Fields）が無効化されます。これは ACF Pro と同じ挙動です。

Secure Custom Fields についての詳細は [developer.wordpress.org/secure-custom-fields](https://developer.wordpress.org/secure-custom-fields/)
をご覧ください。

#### 機能

 * わかりやすく使いやすい設定
 * コンテンツ管理のための強力な機能
 * 30種類以上のフィールドタイプ

## スクリーンショット

[⌊カスタムフィールドのグループを追加。⌉⌊カスタムフィールドのグループを追加。⌉[

カスタムフィールドのグループを追加。

[⌊執筆中にカスタムコンテンツを簡単に追加。⌉⌊執筆中にカスタムコンテンツを簡単に追加
。⌉[

執筆中にカスタムコンテンツを簡単に追加。

[⌊新しい投稿タイプが必要ですか？簡単に追加できます！⌉⌊新しい投稿タイプが必要です
か？簡単に追加できます！⌉[

新しい投稿タイプが必要ですか？簡単に追加できます！

[⌊さまざまな種類のフィールドタイプがわかりやすい。⌉⌊さまざまな種類のフィールドタイプ
がわかりやすい。⌉[

さまざまな種類のフィールドタイプがわかりやすい。

## 評価

![](https://secure.gravatar.com/avatar/2a58af57d3cf341b6761c6d6abc90454ecf5f0c3d6e59c6d5e66fb8533df1754?
s=60&d=retro&r=g)

### 󠀁[Great Plugin](https://wordpress.org/support/topic/great-plugin-41840/)󠁿

 [georg.r](https://profiles.wordpress.org/georgr/) 2026年10月16日

Keep up the good work!

![](https://secure.gravatar.com/avatar/7154b9ae4190b953e6da5a99c771f27fd315c51563ed5fce2a4c8cf2daea1803?
s=60&d=retro&r=g)

### 󠀁[Thanks to share this as free](https://wordpress.org/support/topic/thanks-to-share-this-as-free/)󠁿

 [Joel Gaujard](https://profiles.wordpress.org/defro/) 2026年10月9日

Many thanks

![](https://secure.gravatar.com/avatar/07b353d9bd891918faf16186473556a7007a101d49d74e0c6eb20be678c55539?
s=60&d=retro&r=g)

### 󠀁[Powerfull plugin in wordpress](https://wordpress.org/support/topic/powerfull-plugin-in-wordpress/)󠁿

 [aruneteam](https://profiles.wordpress.org/aruneteam/) 2026年10月7日

Thanks to builder and wordpress.

![](https://secure.gravatar.com/avatar/543efdbc92d8e55f96c0b008e14853cfda1bd244a0806e9c51f2c64e338c5e94?
s=60&d=retro&r=g)

### 󠀁[Excellent and reliable custom fields plugin](https://wordpress.org/support/topic/excellent-and-reliable-custom-fields-plugin/)󠁿

 [wnos](https://profiles.wordpress.org/wnos/) 2026年9月28日

I’ve been using Secure Custom Fields and I’m very happy with it. The plugin is clean,
easy to work with and provides exactly the functionality I need for custom fields
without unnecessary complexity. It integrates well into my WordPress workflow and
feels lightweight and reliable. For developers and agencies building custom WordPress
websites, it is a very useful solution. Thank you to the team for maintaining and
improving the plugin. Highly recommended!

![](https://secure.gravatar.com/avatar/754daa684d960bc61a34fe8e67a101c34278506e33dff82ba7eb68a36296ec4e?
s=60&d=retro&r=g)

### 󠀁[Thank you](https://wordpress.org/support/topic/thank-you-3769/)󠁿

 [Kudos](https://profiles.wordpress.org/vhmc41/) 2026年9月18日

ACF was such a core part of extending Wordpress in a way that was accessible (ie.
being able to use a GUI). We could have written the code, but ACF meant that any
level of developer on our web dev team could jump on and start creating custom post
fields. We transitioned off ACF to SCF almost immediately after our ACF licences
expired. It's nice to have a more accessible version of ACF being maintained and
kept available. So a big thank you to the SCF team.

![](https://secure.gravatar.com/avatar/543bdc84ba9ad3ae60e723c26b23986cfc80178cb836083743ab5bf2e1f7b6cc?
s=60&d=retro&r=g)

### 󠀁[Excellent plugin](https://wordpress.org/support/topic/excellent-plugin-9916/)󠁿

 [NeMeZZZ](https://profiles.wordpress.org/nemezzz/) 2026年7月13日

Excellent plugin.

 [ 69件のレビューをすべて表示 ](https://wordpress.org/support/plugin/secure-custom-fields/reviews/)

## 貢献者と開発者

Secure Custom Fields はオープンソースソフトウェアです。以下の人々がこのプラグイン
に貢献しています。

貢献者

 *   [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/)

“Secure Custom Fields” は22ロケールに翻訳されています。 [翻訳者](https://translate.wordpress.org/projects/wp-plugins/secure-custom-fields/contributors)
のみなさん、翻訳へのご協力ありがとうございます。

[“Secure Custom Fields” をあなたの言語に翻訳しましょう。](https://translate.wordpress.org/projects/wp-plugins/secure-custom-fields)

### 開発に興味がありますか ?

[コードを閲覧](https://plugins.trac.wordpress.org/browser/secure-custom-fields/)
するか、[SVN リポジトリ](https://plugins.svn.wordpress.org/secure-custom-fields/)
をチェックするか、[開発ログ](https://plugins.trac.wordpress.org/log/secure-custom-fields/)
を [RSS](https://plugins.trac.wordpress.org/log/secure-custom-fields/?limit=100&mode=stop_on_copy&format=rss)
で購読してみてください。

## 変更履歴

#### 6.9.9

_Release Date 11th November 2026_

_セキュリティ_

 * Taxonomy fields save terms only to objects that use the taxonomy.
 * Submitted Taxonomy field values that save terms require permission to assign 
   terms in that taxonomy.
 * Saving fields on a profile update requires permission to edit the user.
 * The Gallery field renders attachment edit fields only for users who can edit 
   the attachment.
 * SCF never reads or writes the user metadata WordPress uses for roles, capabilities
   or sign-in, whatever a field is named.

_修正_

 * Block JSON-LD output honours the `enable_schema` setting, as the post output 
   already did.
 * Clone and Flexible Content fields mapped to a Schema.org property output only
   the sub fields mapped to a property, each formatted by its own field type.

#### 6.9.8

_Release Date 3rd November 2026_

_セキュリティ_

 * Saves only keep submitted values for fields rendered for the content being saved,
   or from field groups whose location rules match it. This now applies to posts,
   terms, attachments, menu items, widgets, the Customizer, WooCommerce orders, 
   options pages, comments, users and the block editor. Fields added with JavaScript
   can be allowed with the `acf/form/{context}/allowed_field_keys` filters. Registration
   forms no longer save fields from field groups set to “User Form is Add / Edit”.
 * Field, field group, post type, taxonomy and options page settings are sanitized
   when saved by users without the `unfiltered_html` capability. For those users,
   a field’s wrapper settings are limited to width, class and id. Event handler (`
   on*`) attributes in a field’s wrapper setting are never output.
 * Custom values submitted to Checkbox, Radio and Select fields can no longer change
   the field’s other settings. The new `acf/fields/allow_append_choices` filter 
   controls who can add choices, which by default is still only users with the SCF
   capability.
 * WordPress’s Custom Fields meta box, its AJAX handler and XML-RPC can no longer
   change meta that belongs to SCF fields.
 * Basic uploader nonces are tied to the content being edited.
 * The request that loads field groups while editing a post only returns field groups
   for that post.
 * Relationship, Post Object and Page Link fields don’t show the titles or statuses
   of posts the current user cannot read, and don’t save newly selected posts the
   user cannot read. Existing selections the user cannot read are shown as “(Restricted
   item)” and are kept when saving.
 * Relationship, Post Object and Page Link values rendered in blocks leave out posts
   the post’s author cannot read. New filter: `acf/fields/relational/hide_unreadable_posts`.
 * Bidirectional fields only add references to posts the current user can edit, 
   terms they can assign, and users they can edit or set as a post’s author. Saves
   made with `update_field()`, WP-CLI or cron are not checked. New filters: `acf/
   bidirectional/can_update_target` and `acf/is_trusted_save_context`.
 * Block bindings and the shortcode output only user IDs for User fields. New filter:`
   acf/bindings/allow_user_data`.

_修正_

 * Block bindings and the shortcode output nothing for values they can’t show as
   text, such as post objects, instead of causing a fatal error on PHP 8.
 * Relationship field searches keep loading results when a page of results is left
   out.
 * Saving a custom choice no longer removes backslashes from the field’s other settings.

_Deprecations_

 * `scf_post_password_required()` is deprecated in favor of `acf_post_password_required()`,
   and `scf_restrict_uploaded_field_keys()` in favor of `acf_restrict_uploaded_field_keys()`.
 * The `scf/upload/generate_previews` filter is deprecated in favor of `acf/upload/
   generate_previews`, and `scf/bidirectional/allow_target` in favor of `acf/bidirectional/
   can_update_target`.

#### 6.9.7

_Release Date 21st October 2026_

_セキュリティ_

 * Submitted relationship values only link back to objects that are valid choices
   for the field, or that the submitting user can edit. Values saved by code while
   no user is logged in, such as WP-CLI or cron imports, are not affected. Revisions
   never link back. New filter: `scf/bidirectional/allow_target`.
 * Preview images for files uploaded through front-end File fields, including PDF
   previews and audio or video cover art, are only generated for users who can upload
   to the media library. New filter: `scf/upload/generate_previews`.
 * Password-protected posts referenced by a Post Object or Relationship field are
   only expanded for users who entered the password or can edit them.
 * Field values shown through block bindings only expand referenced content and 
   user details the viewer can read, and the shortcode outputs User fields as IDs.
 * Field values of password-protected posts stay hidden in the shortcode, block 
   bindings, JSON-LD and REST API output until the password is entered.

#### 6.9.6

_Release Date 16th October 2026_

_セキュリティ_

 * Field values from a post’s latest revision are only loaded in a real preview,
   for users who can edit the post.
 * Submitted field values are always validated.
 * Comment and user saves only keep values and uploaded files for fields from field
   groups that apply to the comment or user. New filters: `acf/form/comment/allowed_field_keys`,`
   acf/form/user/allowed_field_keys`, and `acf/options_page/allowed_field_keys` 
   for the existing options page restriction.
 * Image and Gallery fields only accept image files. SVG uploads are still accepted
   when the site allows them.
 * REST responses with `acf_format=standard`, and the `_source` values in every 
   REST response, return IDs instead of full objects for referenced posts and attachments
   the requester cannot read.
 * REST OPTIONS responses only list the fields of a specific object to requesters
   who can read it.
 * User field searches require a nonce created for a User field.

_機能改善_

 * On WordPress 7.1+, blocks registered without a version default to block version
   3. The `acf/blocks/default_block_version` filter receives the registration source(`
   php` or `json`).
 * Version 3 blocks support `"renderPreview": false` to show a placeholder in the
   editor instead of rendering the template.
 * SCF admin screens list blocks still pinned to block version 2 or earlier, with
   a dismissible notice.
 * `acf_encrypt()` and `acf_decrypt()` accept an optional `$context`.

_修正_

 * Inline editable fields in version 3 blocks open on the first click.
 * Radio buttons in SCF admin screens draw a centered dot.
 * Translated block.json settings are applied correctly.
 * Including `pro/blocks-auto-inline-editing.php` directly no longer causes a fatal
   error.

#### 6.9.5

_Release Date 7th August 2026_

_セキュリティ_

 * REST updates now reject bidirectional field writes when the current user cannot
   edit an inverse target.
 * Gallery AJAX responses no longer render attachments the current user cannot read,
   and empty responses now close the attachment sidebar.
 * PDF files uploaded through File and Image fields must start with a valid PDF 
   header. Rejected files are removed from the uploads directory.
 * The internal `acf_encrypt()` and `acf_decrypt()` helpers now authenticate encrypted
   values with an HMAC and require the OpenSSL extension instead of falling back
   to unauthenticated base64 encoding. Anonymous inline `acf_form()` submissions
   now require OpenSSL on the server.

#### 6.9.4

_Release Date 3rd August 2026_

_セキュリティ_

 * Front-end `acf_form()` submissions are now limited to the save target, form settings,
   and fields that the rendered form exposed. Submissions carrying missing, altered,
   or expired form data are rejected before validation or saving.
 * The `acf/form/allowed_field_keys` filter now applies while a form renders rather
   than on submit. Keys added through it are still accepted on save, so forms extended
   at runtime keep working.

#### 6.9.3

_Release Date 28th July 2026_

_強化_

 * Restricted Local JSON writes for multisite users who are not super admins to 
   save paths inside the current site’s uploads directory.
 * Limited Options Page saves to values for fields assigned to the current page.
 * Excluded posts the current user cannot read from Post Object, Page Link, and 
   Relationship field queries.
 * Block render templates are now always resolved from the registered block path,
   and template paths using stream wrappers are rejected.
 * Reduced User field values in REST API responses to user IDs, including within
   Group, Clone, Repeater, and Flexible Content fields.

#### 6.9.2

_Release Date 21st July 2026_

_修正_

 * Fixed Google Maps field values being double-encoded when saved inside a block.
 * Inserting a Link field value in the Classic Editor no longer triggers validation
   for other required fields before the post is saved.
 * Auto Inline Editing blocks no longer return truthy placeholder strings for empty
   field values fetched from a different post inside the block render template.
 * V2 and V3 blocks no longer crash when rendering an oEmbed field whose title begins
   with `[` or `{`.
 * Field group location rules without a location value no longer cause PHP warnings
   on page load.
 * Improved the appearance of the URL, Number, and Select fields on WordPress 7.0
   +.
 * Fields now save on WooCommerce orders when using HPOS in compatibility mode.

#### 6.9.1

_リリース日 – 2026年7月2日_

_セキュリティ_

 * Capped the number of user-contributed choices that can be persisted to checkbox,
   radio, and select field definitions at 1000 by default, with a new `acf/fields/
   max_appended_choices` filter for customization.
 * The WooCommerce order fields save handler is now only registered on order edit
   screens.

_修正_

 * Fixed PHP 8.5 deprecation notices when numeric post ID values contain floats 
   that cannot be represented as integers.

#### 6.9.0

_リリース日 – 2026年6月23日_

_強化_

 * Improved input validation when duplicating field groups, post types, and taxonomies,
   including ownership and type checks on the target.
 * Restricted persistence of custom choices on checkbox, radio, and select fields
   to authorized users.
 * Constrained the field update ability input schema to known properties.
 * Sanitized flexible content layout labels and cleaned up orphaned row meta on 
   layout removal.
 * Hardened REST type field-group metadata exposure and oEmbed source formatting.
 * Normalized non-scalar block binding attribute values.
 * Required authentication and nonce verification before saving fields on WooCommerce
   orders.
 * Preserved localization wrappers in PHP exports and corrected nav menu field ID
   output.

#### 6.8.9

_リリース日 – 2026年6月15日_

_セキュリティ_

 * Hardened the escaping of wp_options LIKE queries used when loading option-page
   meta and during taxonomy term cleanup, switching to esc_like() so option-name
   prefixes are always matched as literals rather than as patterns.

_修正_

 * The URL, text, textarea, and select-style fields no longer raise PHP errors when
   a non-scalar value (such as an array) is submitted; such input is now treated
   as invalid.

#### 6.8.8

_リリース日 – 2026年6月11日_

_セキュリティ_

 * AJAX field handlers now validate that the request nonce was created for the expected
   field type, so a nonce minted for one field type can no longer be replayed against
   another field type’s AJAX handler. The gallery field was also aligned with the
   typed nonce scheme used by all other AJAX fields.
 * `acf_decrypt()` now treats malformed payloads as a decrypt failure and returns`
   false` instead of emitting PHP 8 warnings.

_機能改善_

 * `acf_inline_toolbar_editing_attrs()` now accepts a `return_array` argument that
   returns the attributes as an escaped array suitable for use with `wp_get_attachment_image()`.

_修正_

 * `acf_form()` with `'post_id' => 'new_post'` and a `fields` list of field names
   no longer fatal errors when `acf_form_head()` runs before WordPress’s main query
   is built.
 * Multiple `acf_form()` calls wrapped inside a single outer form tag with one submit
   button no longer silently drop field values, `post_title`, or `post_content` 
   from the non-last forms. A new `acf/form/meta_ttl` filter controls how long per-
   form metadata remains valid.
 * Duplicating a V3 block with identical attributes no longer displays corrupted
   preview content in the duplicate.
 * Switching between tabs containing WYSIWYG fields no longer leaves the admin menu
   pinned against a shorter page, which could lock page scroll.

#### 6.8.7

_リリース日 – 2026年6月8日_

_修正_

 * SCF’s Abilities API integration for its internal post types no longer triggers
   PHP warnings, notices, or a fatal error (500) on block editor and REST API requests
   when another active plugin builds the WordPress abilities registry earlier in
   the request; registration is skipped cleanly in that case and normal abilities
   behavior is otherwise unchanged.

#### 6.8.6

_リリース日 – 2026年5月27日_

_セキュリティ_

 * Hardened the oEmbed field’s AJAX preview handling by restricting provider discovery
   for visitors and users without content-authoring capability while preserving 
   previews from WordPress’s registered oEmbed providers.
 * Hardened front-end `acf_form()` submission processing so the `post_title` and`
   post_content` form options are respected on save, and the save pipeline only 
   accepts values for fields the rendered form exposed. A new `acf/form/allowed_field_keys`
   filter is available for sites that legitimately extend a form at runtime.

#### 6.8.5

_リリース日 – 2026年5月19日_

_機能_

Backports 6.8.1 feature work into SCF.

#### 6.8.4

_リリース日 – 2026年4月30日_

_機能_

 * Backports 6.8.0 and 6.8.0.1 feature work into SCF.
 * AI integration: SCF now integrates with the WordPress Abilities API, allowing
   external consumers, including AI tools, to manage field groups, post types, and
   taxonomies when explicitly enabled via the `enable_acf_ai` feature flag.
 * Structured data: SCF can now generate JSON-LD structured data fields when explicitly
   enabled via the `enable_schema` feature flag.
 * WP-CLI: Added `wp scf json` and backward-compatible `wp acf json` commands for
   importing, exporting, syncing, and checking the status of SCF JSON files.
 * Post types: SCF custom post types now support the WordPress 6.9+ Notes editor
   feature via a new Notes checkbox in the Supports settings.
 * JSON Schemas: Added v1 schemas for supported field types and updated field group,
   post type, and taxonomy schemas.

_機能改善_

 * Blocks V3: The Open in Expanded Editor button text can now be customized via 
   a new `acf.expandedEditorButtonText` block.json property.
 * Blocks V3: Added an `acf/blocks/default_expanded_editor_button_text` PHP filter
   to customize the default Open in Expanded Editor button text.
 * Blocks V3: The edit and Open in Expanded Editor buttons can now be hidden via
   a new `acf.expandedEditorButtons` block.json property.
 * Blocks V3: Added a `blocks/expanded_editor_overlay_class` JavaScript filter for
   customizing the Expanded Editor modal overlay class.
 * Blocks V3: The block form HTML is now preloaded alongside the preview, eliminating
   an extra AJAX call on mount.
 * Blocks V3: Expanded Editor buttons are now hidden for V3 blocks that have no 
   fields assigned.
 * SCF inline script tags now use `wp_print_inline_script_tag()` for Content Security
   Policy (CSP) compliance and nonce support.

_修正_

 * V3 blocks with WYSIWYG fields no longer enqueue TinyMCE editor assets on the 
   frontend.
 * V3 blocks with identical attributes and different InnerBlocks content no longer
   return cached output from the first block on the frontend.
 * Flexible Content fields now properly clean up nested postmeta when a parent layout
   containing nested Flexible Content fields is deleted.
 * The Expanded Editor Done button now stays disabled until the AJAX save completes,
   preventing data loss.
 * Pressing Escape while the Expanded Editor is saving will no longer close the 
   modal, preventing data loss.
 * InnerBlocks content containing backslashes or dollar signs now renders correctly.
 * Auto Inline Editing now only applies to SCF Blocks V3, resolving incorrect hover/
   focus borders appearing on V2 blocks.
 * Auto Inline Editing blocks now receive block context variables in render templates.
 * Auto Inline Editing now works with blocks using `renderCallback`.
 * Validation errors in the V3 Expanded Editor no longer cause a dead-end state.
 * Icon Picker selections in Repeater fields no longer disappear.
 * Range field number input now syncs to the slider and correctly updates V3 block
   previews.
 * Message field Name and Instructions settings are no longer shown in the field
   group editor.
 * Image field no longer crashes in WordPress 7.0 release candidates.
 * V3 blocks registered via PHP now correctly show the Open in Expanded Editor button.
 * Flexible Content disabled layouts now work correctly in Blocks V3.

#### 6.8.3

_リリース日 – 2026年4月22日_

_修正_

 * Fix command palette type error on wp-admin.
 * Plugins requiring ACF are also validated for SCF.
 * REST API calls now honor the user’s `unfiltered_html` capability.
 * Block Preview rendering now verifies the user can edit the target post.
 * Paginated Repeater fields now verify the user can edit the target post.
 * Flexible Content layout title AJAX requests now validate a security nonce.
 * Clone field AJAX endpoints now enforce SCF admin permissions on field group listings.

#### 6.8.2

_リリース日 – 2026年3月24日_

_修正_

 * AJAX Handlers: Prefix field-specific nonces to resolve an issue where third-party
   nonces could be treated as valid for AJAX calls.
 * Block Preview: Verify that user has access to post specified via block context.
 * Repeater Field: Verify that user has access to specified post.
 * REST API: Apply KSES sanitization to field content saved by users without `unfiltered_html`
   capabilities.
 * REST API: Respect `show_in_rest` setting for field groups in `/types` endpoint.

#### 6.8.1

_リリース日 – 2026年3月11日_

_Backports from 6.7.1_

 * Security – User field AJAX queries now enforce field-configured role restrictions
   and validate search permissions.
 * Security – Post Object, Relationship, and Page Link field AJAX queries now enforce
   field-configured restrictions for post status, post type, and taxonomy.
 * Site Health – Track blocks using auto inline editing.

#### 6.8.0

_リリース日 – 2025年12月30日_

_機能_

 * Abilities integration: addded field abilities for Field Groups.
 * Abilities integration: added trash/untrash abilities for internal post types.
 * All backports up to 6.7.0.2.
 * JSON Schemas: Added several fields schemas.
 * WooCommerce HPOS: Added support for custom fields on any WooCommerce Order Types.
 * Added PHPUnit tests.

_修正_

 * Hide duplicated Command Palette Commands on WP 6.9+.
 * Fix field schema validation for WP Rest API.
 * Fix checkbox toggle functionality.

#### 6.7.0

#### 6.7.1

_リリース日 – 2025年12月10日_

_機能_

 * JSON Schemas: Added Options Pages schema.

_修正_

 * Fixed too-early validation of schemas causing a fatal error.
 * Fix block validation on WordPress 6.2.

#### 6.7.0

_リリース日 – 2025年12月3日_

_機能_

 * Tested compatibility up to WordPress 6.9.
 * Abilities support. Taxonomy abilities.
 * JSON schemas. Taxonomy schema.

#### 6.6.0

_リリース日 – 2025年11月19日_

_機能_

 * Backported features up to 6.6.0.
 * Abilities API integration. Post Type abilities.
 * JSON schemas validation infrastructure.

_修正_

 * Fixed Function in network.php
 * SCF label in “More” menu.
 * Get the formatted_value from the original field value.
 * Blocks V3: Fix flexible content not working in sidebar – modal.
 * Use specific entity prefixes for key generation when duplicating entities.

#### 6.5.7

_リリース日 – 2025年8月28日_

_機能_

 * Flexible Content layouts can now be renamed in the post editor, giving content
   editors better clarity when managing layouts.
 * Flexible Content layouts can now be disabled, preventing them from rendering 
   on the frontend without needing to delete their data.
 * Flexible Content layouts can now be collapsed and expanded in bulk for faster
   content editing.
 * Editing a Flexible Content layout now highlights the layout being edited, making
   it easier to identify.
 * The Date and Date Time Picker fields can now be configured to default to the 
   current date.
 * Custom Icon Picker tabs now work correctly when used inside an ACF Block.
 * Duplicating a Field Group no longer causes a fatal error when using Russian translations.
 * ACF classes no longer use dynamic class properties, improving compatibility with
   PHP 8.2+.
 * Field group metabox collapse and expand buttons are no longer misaligned in the
   post editor.
 * HTML is now escaped from field validation errors and tooltips.
 * Added a new source parameter to the /wp/v2/types REST API endpoint that allows
   filtering post types by their origin: core (WordPress built-in), scf (for SCF
   managed types), or other for the rest of CPTs.

_セキュリティ_

– Unsafe HTML in field group labels is now correctly escaped for conditionally loaded
field groups, resolving a JS execution vulnerability in the classic editor.
 – HTML
is now escaped from field group labels when output in the ACF admin. – Bidirectional
and Conditional Logic Select2 elements no longer render HTML in field labels or 
post titles. – The acf.escHtml function now uses the third party DOMPurify library
to ensure all unsafe HTML is removed. A new esc_html_dompurify_config JS filter 
can be used to modify the default behaviour. – Post titles are now correctly escaped
whenever they are output by ACF code. Thanks to Shogo Kumamaru of LAC Co., Ltd. 
for the responsible disclosure. – An admin notice is now displayed when version 
3 of the Select2 library is used, as it has now been deprecated in favor of version
4.

#### 6.5.6

Release discarded due to SVN errors.

#### 6.5.5

_リリース日 – 2025年7月31日_

_機能_

 * Connect block attributes with custom fields via UI.
 * Remove the word ‘New’ from default `add-new*` label values.

_バグ修正_

 * Bug fix: Prevent fatal if class does not exist on Beta Features.

#### 6.5.4

_リリース日 – 2025年7月30日_

Revert from 6.5.2.

#### 6.5.2

_リリース日 – 2025年7月30日_

_機能_

 * Connect block attributes with custom fields via UI.
 * Remove the word ‘New’ from default `add-new*` label values.

#### 6.5.1

_リリース日 – 2025年7月2日_

_バグ修正_

 * Command Palette: Use `@wordpress\icons` instead of Dashicons.

#### 6.5.0

_リリース日 – 2025年6月23日_

_機能改善 & 機能追加_

 * Added Command Palette support.
 * Added editor preview to acf-field source.
 * Added an endpoint to retrieve the custom fields of a post type.
 * Added nav menu as field type.
 * Added compatibility with Woo HPOS for order fields and subscriptions. ( Ported
   from ACF )
 * Create new options when editing a fields value on Selector. ( Ported from ACF)
 * The “Escaped HTML” warning notice is now disabled by default. ( Ported from ACF)
 * Added new `acf/fields/icon_picker/{tab_name}/icons` filter ( Ported from ACF )

_バグ修正_

 * Update initialization of the acfL10n object to ensure it’s available globally.
 * SCF Blocks are now forced into preview mode when editing a synced pattern. ( 
   Ported from ACF )
 * SCF no longer causes an infinite loop in bbPress when editing replies. ( Ported
   from ACF )
 * Changing a field type no longer enables the “Allow Access to Value in Editor 
   UI” setting. ( Ported from ACF )
 * Blocks registered via acf_register_block_type() with a `parent` value of `null`
   no longer fail to register. ( Ported from ACF )
 * Fix AJAX repeater pagination. ( Ported from ACF )
 * Paginated Repeater fields no longer save duplicate values when saving to a WooCommerce
   Order with HPOS disabled ( Ported from ACF )

_テスト_

 * Added an initial batch of e2e tests.

#### 6.4.2

_リリース日 – 2025年4月14日_

 * Resolved issue with shortcode translation not parsing correctly.
 * Improve validation for an URL on field admin.

#### 6.4.1

_リリース日 – 2025年3月7日_

 * Forked from Advanced Custom Fields®
 * Various updates to coding standards.
 * Updated to rely on the WordPress.org translation packs for all strings.

#### 6.3.9

_リリース日 – 2024年10月22日_

 * Version update release

#### 6.3.6.3

_リリース日 – 2024年10月15日_

 * 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
 * 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
 * Fix – SCF Fields now correctly validate when used in the block editor and attached
   to the sidebar

#### 6.3.6.2

_リリース日 – 2024年10月12日_

 * Security – Harden fix in 6.3.6.1 to cover $_REQUEST as well.
 * Fork – Change name of plugin to Secure Custom Fields.

#### 6.3.6.1

_リリース日 – 2024年10月7日_

 * 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)

## コミュニティプラグイン

このプラグインの開発とサポートはコミュニティが行っています。 [このプラグインに貢献する](https://github.com/wordpress/secure-custom-fields/)

## メタ

 *  バージョン **6.9.9**
 *  最終更新日 **6日前**
 *  有効インストール数 **100,000+**
 *  WordPress バージョン ** 6.2またはそれ以降 **
 *  検証済み最新バージョン: **7.1.4**
 *  PHP バージョン ** 7.4またはそれ以降 **
 *  言語
 * [Arabic](https://ar.wordpress.org/plugins/secure-custom-fields/)、[Bengali (Bangladesh)](https://bn.wordpress.org/plugins/secure-custom-fields/)、
   [Chinese (China)](https://cn.wordpress.org/plugins/secure-custom-fields/)、[Chinese (Taiwan)](https://tw.wordpress.org/plugins/secure-custom-fields/)、
   [Dutch](https://nl.wordpress.org/plugins/secure-custom-fields/)、[Dutch (Belgium)](https://nl-be.wordpress.org/plugins/secure-custom-fields/)、
   [English (UK)](https://en-gb.wordpress.org/plugins/secure-custom-fields/)、[English (US)](https://wordpress.org/plugins/secure-custom-fields/)、
   [Galician](https://gl.wordpress.org/plugins/secure-custom-fields/)、[Japanese](https://ja.wordpress.org/plugins/secure-custom-fields/)、
   [Korean](https://ko.wordpress.org/plugins/secure-custom-fields/)、[Persian](https://fa.wordpress.org/plugins/secure-custom-fields/)、
   [Polish](https://pl.wordpress.org/plugins/secure-custom-fields/)、[Portuguese (Brazil)](https://br.wordpress.org/plugins/secure-custom-fields/)、
   [Russian](https://ru.wordpress.org/plugins/secure-custom-fields/)、[Serbian](https://sr.wordpress.org/plugins/secure-custom-fields/)、
   [Spanish (Chile)](https://cl.wordpress.org/plugins/secure-custom-fields/)、[Spanish (Ecuador)](https://es-ec.wordpress.org/plugins/secure-custom-fields/)、
   [Spanish (Mexico)](https://es-mx.wordpress.org/plugins/secure-custom-fields/)、
   [Spanish (Spain)](https://es.wordpress.org/plugins/secure-custom-fields/)、[Swedish](https://sv.wordpress.org/plugins/secure-custom-fields/)、
   [Turkish](https://tr.wordpress.org/plugins/secure-custom-fields/)、[Vietnamese](https://vi.wordpress.org/plugins/secure-custom-fields/).
 *  [プラグインを翻訳](https://translate.wordpress.org/projects/wp-plugins/secure-custom-fields)
 * タグ
 * [custom fields](https://ja.wordpress.org/plugins/tags/custom-fields/)[fields](https://ja.wordpress.org/plugins/tags/fields/)
   [meta](https://ja.wordpress.org/plugins/tags/meta/)[scf](https://ja.wordpress.org/plugins/tags/scf/)
 *  [詳細を表示](https://ja.wordpress.org/plugins/secure-custom-fields/advanced/)

## 評価

 5つ星中4.8つ星

 *  [  65 5-星レビュー     ](https://wordpress.org/support/plugin/secure-custom-fields/reviews/?filter=5)
 *  [  0 4-星レビュー     ](https://wordpress.org/support/plugin/secure-custom-fields/reviews/?filter=4)
 *  [  0 3-星レビュー     ](https://wordpress.org/support/plugin/secure-custom-fields/reviews/?filter=3)
 *  [  0 2-星レビュー     ](https://wordpress.org/support/plugin/secure-custom-fields/reviews/?filter=2)
 *  [  4 1-星レビュー     ](https://wordpress.org/support/plugin/secure-custom-fields/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/secure-custom-fields/reviews/#new-post)

[すべてのレビューを見る](https://wordpress.org/support/plugin/secure-custom-fields/reviews/)

## 貢献者

 *   [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/)

## サポート

過去2ヶ月以内に解決した問題:

     1 / 5

 [サポートフォーラムを表示](https://wordpress.org/support/plugin/secure-custom-fields/)