at path：
ROOT
/
wp-content
/
plugins
/
whizzy
/
core
/
README.md
run：
R
W
Run
callbacks
DIR
2025-08-15 17:54:51
R
W
Run
classes
DIR
2025-08-15 17:54:51
R
W
Run
interfaces
DIR
2025-08-15 17:54:51
R
W
Run
shortcodes
DIR
2025-08-15 17:54:51
R
W
Run
templates
DIR
2025-08-15 17:54:51
R
W
Run
tests
DIR
2025-08-15 17:54:51
R
W
Run
views
DIR
2025-08-15 17:54:51
R
W
Run
.gitattributes
230 By
2025-08-15 17:54:51
R
W
Run
Delete
Rename
.gitignore
605 By
2025-08-15 17:54:51
R
W
Run
Delete
Rename
README.md
993 By
2025-08-15 17:54:51
R
W
Run
Delete
Rename
bootstrap.php
541 By
2025-08-15 17:54:51
R
W
Run
Delete
Rename
core.php
6.24 KB
2025-08-15 17:54:51
R
W
Run
Delete
Rename
defaults.php
930 By
2025-08-15 17:54:51
R
W
Run
Delete
Rename
helper-functions.php
1.72 KB
2025-08-15 17:54:51
R
W
Run
Delete
Rename
error_log
up
📄
README.md
Save
Field Configuration Spec ======================== The following are system reserved field metadata keys: - type - name (optional) - idname (auto-generated based on name) - default (optional) - label (optional) - desc (optional) - form (internal) - cleanup (optional) - checks (optional) - rendering (optional) Field detection --------------- If an array inside the dedicated fields configuration block has the "type" key it is considered to be a field configuration regardless of where it is inside the configuration (since fields may have other fields as children that themselves have other fields, etc). Field name ---------- The key pointing to a field configuration is considered the name of the field unless a the optional key "name" is provided. If neither is available or the name key is empty the field is considered esthetic and while it will be processed by the rendering routines it won't be processed by the data handling routines (since it's not a named entity).