About this plugin
atshift Fields is a maintained and extended Custom Field Suite-compatible plugin for WordPress sites that need structured content editing without losing existing CFS data or template compatibility. It preserves the familiar CFS API, including CFS()->get(), while adding security hardening, WordPress/PHP compatibility fixes, and practical tools for clearer admin workflows.
Version 3 makes field management much more flexible for content-heavy sites. The redesigned Field Group editor supports nested groups, drag-and-drop editing, responsive layouts, and multilingual admin labels, so large editing screens can be organized in a way that is easier to build, review, and maintain.
Tab Groups, Horizontal Groups, Accordion Groups, Conditional Groups, and Loops help divide complex input screens into focused sections, place related fields side by side, show fields only when they are relevant, and manage repeated content cleanly.
Version 3 also brings native WordPress fields into field groups, including post title, content, save and publish controls, categories, tags, featured image, and post editing screen display controls. Code View, Shortcode fields, role-aware editing controls, and Classic Meta Box Placement add more options for safer, more flexible real-world editing workflows.
For setup instructions, field value output examples, migration notes, and implementation examples, see the atshift Fields website.
Things to know
- This is a maintenance build, not an official upstream release.
- Always back up your files and database before replacing an existing CFS installation.
- Deactivate the original Custom Field Suite plugin before activating this maintenance build.
- Test on a local or staging site before using it on a production site.
- CFS returns stored values; theme templates should still escape output with WordPress escaping functions.
- Added field types are not available in the original upstream CFS 2.6.7 release.
Field types
- Text
- Textarea
- WYSIWYG
- Tab Group
- Loop (repeatable fields)
- Horizontal Group
- Accordion Group (collapsible group)
- Conditional Group
- Phone Number
- Email Address
- Hyperlink
- URL
- Number
- Select
- Checkbox
- True / False
- Radio Button
- Date
- Time
- File Upload
- Photo Gallery
- Color
- Code View
- Shortcode
- Embed Code
- Classic Meta Box Placement
- Post Title (native WordPress title)
- Post Content (native WordPress content)
- Save / Publish (native WordPress save and publish controls)
- Post Categories (Standard / Global)
- Post Tags (native WordPress tags)
- Featured Image (native WordPress featured image)
- Term
- Relationship
- User
Added features in this maintenance build
- Security hardening for known CFS 2.6.7 vulnerability classes.
- PHP 8.2+ and WordPress admin compatibility fixes.
- Checkbox and Radio Button fields.
- Phone Number, Email Address, Number, URL, and Time fields with format validation.
- Time field with hour and minute select menus.
- Photo Gallery field with sortable media selection and gallery-friendly output data.
- Native WordPress Post Title, Post Content, Save / Publish, Standard and Shared Taxonomy Post Categories, Post Tags, and Featured Image fields inside CFS field groups.
- Horizontal Group field for arranging multiple fields side by side, with evenly distributed and left-aligned layout options.
- Accordion Group field for organizing child fields into collapsible sections on post edit screens.
- Field Group editor buttons to add a new field directly below an existing field or inside a Loop, Horizontal Group, or Accordion Group.
- Color-coded structure badges and matching range backgrounds for Tabs, Loops, Horizontal Groups, and Accordion Groups.
- Improved drag-and-drop and Tab boundary handling in the Field Group editor.
- Inline validation messages and an error summary that opens the containing Tab, Loop, or Accordion Group and scrolls to the selected invalid field.
- Field type list ordering grouped by common editing workflows.
- Field Group parent / child synchronization to reduce cases where nested fields disappear from the post edit screen.
- Placement rule warnings for field groups that have no placement rules.
- Configurable placeholders for Text, Phone Number, Email Address, Hyperlink, and URL fields.
Usage
- Browse to the “Field Groups” admin menu.
- Create a Field Group containing one or more custom fields.
- Choose where the Field Group should appear, using the Placement Rules box.
- Use the CFS get method in your theme templates to display custom field values.
Example:
>
For rich text fields, use an appropriate HTML sanitizer such as wp_kses_post().
Tab Group notes
Tab Group is a layout field for splitting fields on the post edit screen into tabbed sections.
Place a Tab Group before the fields that should appear in that tab. Another Tab Group starts another tab section.
Horizontal Group notes
Horizontal Group is a layout field for placing multiple child fields side by side on the post edit screen. On narrow screens, the fields stack vertically.
Horizontal Groups are intended to contain multiple normal fields. Tabs, Loops, Accordions, Conditional Groups, and other Horizontal Groups cannot be placed inside a Horizontal Group.
Accordion Group notes
Accordion Group is a layout field for placing child fields inside a collapsible section on the post edit screen. It can be configured to open by default.
Tabs cannot be placed inside an Accordion Group.
Conditional Group notes
Conditional Group is a layout field for displaying different child fields depending on a selected radio button or dropdown choice on the post edit screen.
Child fields can be assigned to condition-specific areas in the Field Group editor. Tabs and other Conditional Groups cannot be placed inside a Conditional Group.
Classic Meta Box Placement notes
Classic Meta Box Placement is a slot field for moving classic third-party meta boxes into a chosen position inside an atshift Fields field group. It does not save CFS field values; saving, nonces, permissions, scripts, and styles remain the responsibility of the original meta box plugin.
Block Editor-only panels are not supported. Native WordPress meta boxes and internal CFS meta boxes are shown as not recommended to move.
The original meta box header is hidden after placement because the atshift Fields field label and notes provide the heading. Display width can be set to side width (320px), 50%, 75%, or 100%; narrow screens always use 100% width.
WordPress native field notes
Post Title, Post Content, Save / Publish, Post Categories, Post Tags, and Featured Image edit the native WordPress objects directly. They are not CFS-only post meta fields.
For Post Categories, child category selection can also select parent categories, and removing a parent selection removes its child selections. If all categories are removed, WordPress’ default category is restored.
User fields are available on WordPress administration screens only. They are omitted from front-end forms, ignored if submitted directly, and existing values are preserved so public forms cannot enumerate or alter WordPress accounts.
Security maintenance notes
7 codebase.
The maintenance work addresses known vulnerability classes around Loop field code execution, Term field SQL injection, CFS form title / content stored XSS, and existing post updates through CFS forms without normal edit capability checks.
Front-end User fields are blocked at rendering, validation, and saving boundaries. Save / Publish also keeps scheduled posts from becoming public when an editor without the post type’s publish capability submits a past publication date.
7 codebase. org SVN release flow. org publication is not a substitute for an independent third-party security audit.
Redistribution and license
This maintenance build is distributed under the GNU General Public License version 2 (GPLv2), the same license as the upstream plugin. You may use, copy, modify, and redistribute this package, including modified versions, under GPLv2.
When redistributing this package, keep the GPLv2 license notice, preserve the original author attribution, include the source code, and make clear that this is a maintained and extended build by @shift.
Documentation and support
- Official website
- Field group setup guide
- Field value output reference
- Compatibility API reference
- Implementation examples
- Development repository
- Original Custom Field Suite source