Title: atshift Fields (Maintenance for Custom Field Suite)
Author: @shift
Published: <strong>2026-07-09</strong>
Last modified: 2026-09-28

---

Szukaj wtyczek

![](https://ps.w.org/atshift-fields-maintenance-for-custom-field-suite/assets/banner-
772x250.png?rev=3606786)

![](https://ps.w.org/atshift-fields-maintenance-for-custom-field-suite/assets/icon-
256x256.png?rev=3601453)

# atshift Fields (Maintenance for Custom Field Suite)

 Autor: [@shift](https://profiles.wordpress.org/atshift/)

[Pobierz](https://downloads.wordpress.org/plugin/atshift-fields-maintenance-for-custom-field-suite.3.0.7.1.zip)

 * [Szczegóły](https://pl.wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/#description)
 * [Recenzje](https://pl.wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/#reviews)
 *  [Instalacja](https://pl.wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/#installation)
 * [Rozwój](https://pl.wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/#developers)

 [Wsparcie](https://wordpress.org/support/plugin/atshift-fields-maintenance-for-custom-field-suite/)

## Opis

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](https://plugins.at-shift.net/en/fields/).

#### 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:

    ```
    <?php echo esc_html( CFS()->get( 'my_text_field' ) ); ?>
    ```

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

This package includes local security and compatibility hardening on top of the upstream
2.6.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.

The changes were verified locally against the built-in CFS field types, added field
types, and an upgrade path from the original 2.6.7 codebase. This package has also
been adjusted for the WordPress.org plugin directory and published through the official
WordPress.org SVN release flow. WordPress.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](https://plugins.at-shift.net/en/fields/)
 * [Field group setup guide](https://plugins.at-shift.net/en/fields/guide/)
 * [Field value output reference](https://plugins.at-shift.net/en/fields/output/)
 * [Compatibility API reference](https://plugins.at-shift.net/en/fields/api/)
 * [Implementation examples](https://plugins.at-shift.net/en/fields/examples/)
 * [Development repository](https://github.com/at-shift/at-shift-cfs)
 * [Original Custom Field Suite source](https://github.com/mgibbs189/custom-field-suite)

## Zrzuty ekranu

[⌊Field Group editor with the field type selector and native WordPress field types.⌉⌊
Field Group editor with the field type selector and native WordPress field types
.⌉[

Field Group editor with the field type selector and native WordPress field types.

[⌊Nested field groups using tabs, accordions, conditional groups, loops, and horizontal
groups.⌉⌊Nested field groups using tabs, accordions, conditional groups, loops, 
and horizontal groups.⌉[

Nested field groups using tabs, accordions, conditional groups, loops, and horizontal
groups.

[⌊Dedicated field group inputs displayed on the WordPress page editing screen.⌉⌊
Dedicated field group inputs displayed on the WordPress page editing screen.⌉[

Dedicated field group inputs displayed on the WordPress page editing screen.

[⌊Placement rules for post types, post formats, user roles, posts, taxonomy terms,
and page templates.⌉⌊Placement rules for post types, post formats, user roles, posts,
taxonomy terms, and page templates.⌉[

Placement rules for post types, post formats, user roles, posts, taxonomy terms,
and page templates.

[⌊Extra display settings for edit-screen layout, native section visibility, and 
role-based hiding behavior.⌉⌊Extra display settings for edit-screen layout, native
section visibility, and role-based hiding behavior.⌉[

Extra display settings for edit-screen layout, native section visibility, and role-
based hiding behavior.

## Instalacja

 1. Back up your files and database before replacing an existing Custom Field Suite
    installation.
 2. Deactivate the original Custom Field Suite plugin before activating this maintenance
    build.
 3. Install and activate atshift Fields from the WordPress plugin directory, or upload
    the plugin folder to `/wp-content/plugins/`.
 4. Open the atshift Fields / Field Groups admin screen.
 5. Create a Field Group, add fields, and set Placement Rules for the edit screens 
    where it should appear.
 6. Use `CFS()->get()` in your theme templates to display saved field values.

For detailed guides and examples, see the [atshift Fields website](https://plugins.at-shift.net/en/fields/).

## Najczęściej zadawane pytania

### Is this the official successor to Custom Field Suite?

No. atshift Fields is an independent, unofficial compatible maintenance and extension
build distributed under GPLv2.

### Can I replace the original Custom Field Suite with atshift Fields?

In many cases, yes. The plugin preserves the main data structures and API compatibility,
but always back up your site and test on staging before replacement.

### Does atshift Fields preserve the original Custom Field Suite API?

Yes. It preserves the main APIs used by existing themes, including `CFS()->get()`,`
get_field_info()`, `get_reverse_related()`, `save()`, `find_fields()`, and `form()`.

### Where can I find documentation?

See the [atshift Fields website](https://plugins.at-shift.net/en/fields/) for setup
guides, output examples, API notes, and implementation examples.

## Recenzje

Wtyczka nie ma jeszcze żadnej recenzji.

## Kontrybutorzy i deweloperzy

„atshift Fields (Maintenance for Custom Field Suite)” jest oprogramowaniem open 
source. Poniższe osoby miały wkład w rozwój wtyczki.

Zaangażowani

 *   [ @shift ](https://profiles.wordpress.org/atshift/)
 *   [ Matt Gibbs ](https://profiles.wordpress.org/mgibbs189/)

Wtyczka „atshift Fields (Maintenance for Custom Field Suite)” została przetłumaczona
na 2 języki. Podziękuj [tłumaczom](https://translate.wordpress.org/projects/wp-plugins/atshift-fields-maintenance-for-custom-field-suite/contributors)
za ich wkład.

[Przetłumacz wtyczkę “atshift Fields (Maintenance for Custom Field Suite)” na swój język.](https://translate.wordpress.org/projects/wp-plugins/atshift-fields-maintenance-for-custom-field-suite)

### Interesuje cię rozwój wtyczki?

[Przeglądaj kod](https://plugins.trac.wordpress.org/browser/atshift-fields-maintenance-for-custom-field-suite/),
sprawdź [repozytorium SVN](https://plugins.svn.wordpress.org/atshift-fields-maintenance-for-custom-field-suite/)
lub czytaj [dziennik rozwoju](https://plugins.trac.wordpress.org/log/atshift-fields-maintenance-for-custom-field-suite/)
przez [RSS](https://plugins.trac.wordpress.org/log/atshift-fields-maintenance-for-custom-field-suite/?limit=100&mode=stop_on_copy&format=rss).

## Rejestr zmian

#### 3.0.7.1

 * Fixed `CFS()->save()` selecting a field inside a layout group instead of a same-
   named direct field in another group, while preserving the previous lookup order
   when only layout fields share a name.

#### 3.0.7

 * Fixed API and revision saves so fields nested in Horizontal, Accordion, and Conditional
   groups are saved correctly, including layout groups inside Loop rows.
 * Ignored unknown API field names safely instead of emitting PHP warnings.

#### 3.0.6.3

 * Made User fields unavailable in front-end forms and protected existing values
   from forged public submissions.
 * Prevented users without publishing capability from making scheduled posts public
   by changing the publication date.

#### 3.0.6.2

 * Fixed the native Post Content visual editor so links and other HTML remain valid
   markup after a post is saved instead of being displayed as escaped text.

#### 3.0.6.1

 * Added Indonesian (`id_ID`) translation files, with all strings independently 
   reviewed for accuracy, context, and consistent WordPress terminology.

#### 3.0.6

 * Fixed the native Post Content visual editor so Visual/Code tab switching, editor
   toolbars, and media controls initialize correctly without inserting TinyMCE bookmark
   markup into content.
 * Fixed a conflict between native Post Content and WYSIWYG fields that could interrupt
   editor initialization when both fields appear on the same screen.

#### 3.0.5.3

 * Reviewed standalone operation and integrations between atshift projects with 
   Codex Security Check, fixing potential defects and security issues and applying
   additional hardening.
 * Made other minor fixes.

#### 3.0.5.2

 * Standardized the plugin metadata links shown on the Plugins screen.

#### 3.0.5.1

 * Fixed confirmation dialog cancellation so Loop row and Field Group field add/
   delete actions are not performed when cancelled.
 * Confirmed compatibility with WordPress 7.1 RC3.

#### 3.0.5

 * Added confirmation prompts before adding Loop rows or Field Group fields, and
   before deleting fields in the Field Group editor.
 * Added Translate and Output Reference links to the Plugins screen, and updated
   the author link to the atshift Fields documentation site.

#### 3.0.4.3

 * Added a Settings shortcut to the Plugins screen action links.

#### 3.0.4.2

 * Added a Close button to each Loop row action area.

#### 3.0.4.1

 * Fixed Save / Publish field submission so actions follow the native WordPress 
   save flow, preventing unintended draft saves and unnecessary leave-page warnings.
 * Fixed required Post Categories validation so the WordPress default category alone
   does not satisfy the requirement.

#### 3.0.4

 * Added a dedicated Embed Code field for iframe-based embeds such as maps, so sites
   that previously used text fields or textareas for embed code can migrate safely
   under the strengthened sanitization.

#### 3.0.3.1

 * Fixed Save / Publish field updates so published, scheduled, or private posts 
   are not unintentionally moved to Pending Review when edited by users without 
   publish capability.
 * Fixed native Post Title field updates so existing slugs are preserved unless 
   explicitly changed by WordPress.

#### 3.0.3

 * Improved layout refresh for WYSIWYG and auto-resizing textarea fields when Accordion,
   Conditional, or Loop sections become visible.

#### 3.0.2.8

 * Fixed WYSIWYG field output so escaped paragraph HTML is normalized before `CFS()-
   >get()` formatting.
 * Normalized escaped rich text HTML before saving WYSIWYG and native Post Content
   field values.

#### 3.0.2.7

 * Fixed WYSIWYG editor content display so paragraph HTML opens normally in the 
   visual editor instead of appearing as escaped tags.
 * Improved WYSIWYG editor font styling on admin edit screens.

#### 3.0.2.6

 * Improved field heading styling so labels stand out more clearly while following
   the user’s admin color scheme.
 * Improved Loop row spacing, color-scheme-aware row styling, and safer row action
   controls.
 * Improved Loop row heading behavior and added guidance for dynamic row labels.
 * Improved required-field error feedback so users can more easily find and resolve
   validation errors.
 * Added an Extra display setting for hiding Global Categories.
 * Removed the default value setting from the Shortcode field.
 * Fixed a WYSIWYG initialization warning that could interrupt later field scripts.

#### 3.0.2.5

 * Improved field placement when dragging fields into lower Tab Groups.
 * Improved where the bottom „Add New Field” button places fields when Tab Groups
   are present.
 * Fixed field addition issues when multiple Loop fields exist on the same field
   group.
 * Improved mobile spacing for nested category items.
 * Added a warning for empty Tab Group labels.
 * Adjusted several edit-screen colors to follow the user’s admin color scheme.
 * Improved Textarea height adjustment for saved long content.
 * Added missing translations.

#### 3.0.2.4

 * Added warnings and safeguards for some sites with many fields where field values
   or placement rules may fail to save.
 * Added an option to add categories from the Post Categories (Standard / Global)
   field.
 * Other minor fixes.

#### 3.0.2.3

 * Improved native title settings, frontend visual editor fonts, Extras display 
   settings, and Tab Group editing UI.

#### 3.0.2.2

 * Refined the Save / Publish field status display so selected status changes are
   applied only when saving.
 * Improved Save / Publish field labels for publish and schedule actions.
 * Added preview button support for draft and pending posts in the Save / Publish
   field.
 * Prevented autosave requests from applying Save / Publish field status changes.
 * Restored WordPress-standard left alignment for the trash link in the Save / Publish
   field.
 * Fixed password field placement in the Save / Publish visibility controls.
 * Updated bundled translation files.

#### 3.0.2.1

 * Added an option to require a condition selection in Conditional Group fields.
 * Added a required-field indicator for Accordion Group headings when required child
   fields are included.
 * Added Post Categories options to hide the category search box and selected-only
   filter.
 * Fixed a conflict between default category handling and parent/child auto-selection
   in Post Categories fields.
 * Refined the Save / Publish field layout and visual presentation.
 * Updated bundled translation files.

#### 3.0.2

 * Added Classic Meta Box Placement for placing classic third-party meta boxes inside
   atshift Fields field groups.

#### 3.0.1.1

 * Bundled translation files in the WordPress.org release package.

#### 3.0.1

 * Added a Shortcode field that returns rendered shortcode output through `CFS()-
   >get()`.
 * Added role-based shortcode editing controls. Users without permission do not 
   see the field, and existing shortcode values are preserved when they save other
   fields.
 * Added an Extra Display Setting to force the classic post edit Screen Options 
   layout to 1 column.
 * Added Side / Main Extra Display Settings for hiding unnecessary native editor
   sections with section-level role targeting.

#### 3.0.0

 * Redesigned the Field Group editor UI, including group hierarchy, spacing, drag-
   and-drop behavior, and responsive layouts.
 * Clarified nested structures for Tab, Accordion, Loop, Horizontal, and Conditional
   groups.
 * Added condition-specific drop areas for Conditional Groups so dragged fields 
   can be assigned to each condition more easily.
 * Added automatic field-name handling for group fields and native WordPress fields
   to reduce unnecessary manual input.
 * Improved native WordPress field support for Post Title, Post Content, Save / 
   Publish, Post Categories, Post Tags, and Featured Image.
 * Refined Save / Publish status, visibility, publish date, draft, publish, and 
   update behavior.
 * Improved display and selection behavior for Post Categories (Standard / Global)
   and Post Tags.
 * Improved admin previews and handling for Photo Gallery, File Upload, and image
   fields.
 * Updated the atshift Fields Tool UI with clearer Export / Import / Reset guidance
   and translations.
 * Improved placement rules, extras, tooltips, Select2/Selectize displays, and admin
   UI details.
 * Refined required-field and group-structure warnings so issues are easier to understand.
 * Improved metabox compatibility and display stability in both Block Editor and
   Classic Editor environments.
 * Cleaned up internal PHP/CSS/JavaScript while preserving compatibility with the
   original Custom Field Suite API and saved data.
 * Strengthened admin save and AJAX handling, including nonce and capability checks.
 * Updated multilingual translations for new fields, settings, warnings, and tool
   screens.

## Meta

 *  Wersja **3.0.7.1**
 *  Ostatnia aktualizacja **2 tygodnie temu**
 *  Włączone instalacje **30+**
 *  Wersja WordPressa ** 5.0 lub nowszej **
 *  Testowano do **7.1.3**
 *  Języki
 * [English (UK)](https://en-gb.wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/),
   [English (US)](https://wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/),
   i [Russian](https://ru.wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/).
 *  [Przetłumacz na swój język](https://translate.wordpress.org/projects/wp-plugins/atshift-fields-maintenance-for-custom-field-suite)
 * Tagi
 * [custom fields](https://pl.wordpress.org/plugins/tags/custom-fields/)[fields](https://pl.wordpress.org/plugins/tags/fields/)
   [postmeta](https://pl.wordpress.org/plugins/tags/postmeta/)[relationship](https://pl.wordpress.org/plugins/tags/relationship/)
   [repeater](https://pl.wordpress.org/plugins/tags/repeater/)
 *  [Widok zaawansowany](https://pl.wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/advanced/)

## Oceny

Nie przesłano jeszcze żadnych recenzji.

[Twoja opinia](https://wordpress.org/support/plugin/atshift-fields-maintenance-for-custom-field-suite/reviews/#new-post)

[Zobacz wszystkierecenzje.](https://wordpress.org/support/plugin/atshift-fields-maintenance-for-custom-field-suite/reviews/)

## Zaangażowani

 *   [ @shift ](https://profiles.wordpress.org/atshift/)
 *   [ Matt Gibbs ](https://profiles.wordpress.org/mgibbs189/)

## Wsparcie

Masz coś do dodania? Potrzebujesz pomocy?

 [Zobacz forum wsparcia](https://wordpress.org/support/plugin/atshift-fields-maintenance-for-custom-field-suite/)