WordPress / WordPress/secure-custom-fields
Expose Custom Fields as a source for inline tokens
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
This project aims to prepare for the upcoming WordPress Bits as inline tokens, making SCF custom fields available as a source for them, so users can easily insert field values into rich text areas and other supported contexts.
This depends on the development of Bits and their availability in core or other canonical plugins.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked WordPress proposal about Bits as dynamic tokens and confirm where Bits are available in core or canonical plugins. Then trace how Secure Custom Fields exposes custom-field values to supported rich-text contexts. Done means SCF custom fields can be selected as a source for inline tokens once the dependency is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100