Field group setup
Follow the complete setup flow for Custom Field Suite (CFS) and atshift Fields, from creating a field group to displaying it on the WordPress editing screen.
Overview
A field group contains field definitions and placement rules. Fields define what editors enter, while placement rules determine which post editing screens display the group.
Create
Naming examples: Product details, Company profile, or Event details make the group's purpose easy to recognize.
Configure fields
CFS()->get( 'field_name' ). Use letters, numbers, and underscores.Choosing a field type displays its available options. Configure validation, default values, placeholders, choices, return values, and other settings as needed.
The category field can display the standard WordPress category taxonomy or any registered hierarchical taxonomy as a Shared Taxonomy. If posts, pages, and custom post types should share one classification, register that taxonomy in a theme or another plugin first, then choose it as the category source.
These fields edit native WordPress data, including the post title, post content, post status, visibility, publish date, and move-to-trash actions, from inside a field group. Post Content can use either Textarea or Visual editor mode and saves to post_content. Role-based settings control editing permissions in the admin UI; they do not change front-end output code. These fields do not store CFS-specific post meta, so themes should use standard functions such as get_the_title(), the_content(), get_post_status(), and get_the_date().
The Shortcode field stores shortcode text, and CFS()->get( 'field_name' ) returns the rendered output in your theme. When editing roles are configured, users without permission do not see the entire field in the post editing screen. Rendering a saved value on the front end does not require that editing role again.
The gallery field supports adding, reordering, and removing multiple images. Return values can be Attachment IDs, Image URLs, Image Data, or Gallery HTML. Choose Image Data when building a custom layout or modal, because it includes image IDs, size URLs, alt text, captions, and related attachment data.
A default value supplies an initial value. A placeholder is an example or hint that disappears when a value is entered.
Order
Drag a field by its header to change its position on the post editing screen. The Add New Field Below control inserts a new field directly where you need it.
Structure
Use a loop for repeatable groups of inputs. Drag child fields inside it and configure the row label, button label, and minimum or maximum rows.
Arrange two to four related fields side by side. Choose the column count and even or left alignment. Fields stack on narrow screens.
Place child fields in a collapsible section and choose whether it opens by default.
Split a large set of inputs into tabs. The tab itself does not store a value.
Show or hide child fields according to a choice. Select Radio Button or Dropdown, define the choices, then drag child fields inside the group. Use each child's Display for choice setting to assign the choice that reveals it.
Radio buttons initially show the branch matching the default value. Dropdowns begin with “Please select...” and reveal a branch after selection. Stored values in hidden branches are retained.
Important: Loops, horizontal groups, accordions, and tabs organize the editing interface. A Conditional Group also stores its selected value. Retrieve child values using each child's field name.
Placement rules
Placement rules control which editing screens display the field group. A typical rule is Post Type equals Post or Post Type equals Page.
The group appears on every editable post screen. Unless this is intentional, add at least one condition such as Post Type.
Publish and enter
Replacing upstream CFS
The main data structure and API compatibility are preserved. Before replacing the plugin on a production site, back up the database and original plugin files and test on staging.
Add-ons that overlap with fields added by atshift Fields, such as radio buttons or checkboxes, may use different stored-value formats or label retrieval methods. Theme output may therefore require changes. Disable the relevant Add-on and verify on staging that existing values are inherited correctly and that data entry, saving, and output continue to work.