Add official field documentation (Checkbox, Button Group, Clone, Color Picker, Image, Date Picker)#359
Add official field documentation (Checkbox, Button Group, Clone, Color Picker, Image, Date Picker)#359racmanuel wants to merge 10 commits intoWordPress:trunkfrom
Conversation
Expanded the features section to provide a comprehensive overview of Secure Custom Fields, including core features, content management, field types, developer tools, performance, security, compatibility, and extensibility.
Updated the Checkbox field documentation to enhance clarity and detail, including examples and best practices for use cases in a movie website context.
Expanded documentation for the Button Group field in SCF, detailing its features, usage, and best practices for both editors and developers. Included examples and code snippets for better understanding.
Updated the Checkbox field documentation to clarify usage, examples, and best practices. Improved language for better understanding and consistency.
Expanded documentation on the Clone field, including usage, key features, best practices, and examples for both editors and developers. Enhanced clarity and detail for better understanding of functionality.
Expanded documentation for the Color Picker field, detailing its features, usage, and best practices for both editors and developers. Added examples and clarified return formats.
Expanded the documentation for the Image field to include additional features, usage instructions, and best practices for both editors and developers.
Expanded documentation for the Date Picker field, detailing its features, usage, settings, best practices, and examples for both editors and developers.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Updated the instructions for loading the Secure Custom Fields plugin to include a guarded bootstrap method. This method prevents loading SCF twice if it's already active or installed as a standalone plugin.
racmanuel
left a comment
racmanuel
left a comment
There was a problem hiding this comment.
💡 Why is this extra bootstrap code needed?
When SCF is installed via Composer and bundled inside your plugin or theme, there is a chance that the same site also has Secure Custom Fields installed as a regular WordPress plugin.
If both copies are loaded at the same time, PHP will try to redeclare the same classes and functions, causing fatal errors.
This guarded bootstrap checks first if SCF is already loaded or active as an external plugin. Only if no existing instance is found, it loads the bundled version from
vendor/.In short: it guarantees that SCF is loaded exactly once, preventing conflicts while still allowing developers or site owners to use their own global SCF installation if they prefer.
1 participant
This pull request adds comprehensive, production-ready documentation for several core field types in Secure Custom Fields (SCF).
The goal of this work is to provide clear, consistent, and authoritative documentation that meets WordPress.org standards and supports both non-technical users and developers.
Included documentation
Documentation scope
Each documentation page:
Purpose
This pull request contains documentation only and does not introduce any functional or behavioral changes to the plugin.