ACPT – Custom post types. Simplified

Pre-activated

Version

2.1.8 Changelog

Updated

29 Oct 2026

Auto-update

Yes How it works

File scan

Clean Details

Members can request updates and report problems from here.

About this plugin

ACPT – Custom Post Types Simplified is a WordPress plugin designed for developers and site builders who need to create and manage custom post types without wrestling with complex code.

It lets you build custom fields, taxonomies, and meta boxes through an intuitive dashboard interface, saving you hours of development time. Compatible with Gutenberg and the REST API, it’s a brilliant choice for anyone building flexible, content-rich WordPress sites quickly and efficiently.

Changelog

Version 2.1.8

Latest 28 Oct 2026

14 fixed

Fixed

Fatal error when saving a post - on sites where another plugin loads a newer version of the webmozart/assert library (2.x, PHP 8.2+), saving a post with ACPT fields crashed with "Declaration of ACPTUtilsPHPAssert::string() must be compatible". ACPT no longer redeclares the library's methods, so it works with both versions (Ticket #1435).
Conflicts with other plugins' PHP libraries - ACPT's PHP libraries (Twig, phpfastcache, webmozart/assert, Symfony YAML and the others) are now bundled under ACPT's own namespace, so another plugin loading a different version of the same library can no longer break ACPT, or be broken by it.
The update was offered again after updating - right after an update, WordPress offered the same version again. ACPT now compares against the installed version, and an up-to-date ACPT shows the auto-updates toggle (Ticket #1439).
"No response from the server" on the license page - when acpt.io's answer wasn't JSON (a firewall's block page, an error page), the license page hid what the site received. It now shows the HTTP status and the page's text (Ticket #1431).
Saving a meta group with a nameless box crashed - the save failed with a server error; the box is now rejected with a message. Empty field type groups are hidden in the WooCommerce product data builder.
Required fields hidden by their conditions blocked the save - a required field hidden by its own or its box's conditions stopped the browser from submitting the form, and was still validated on the server ("Expected a non-empty value."). Hidden fields are no longer required or validated; their value is still saved (Ticket #1437).
Repeater children named "type" or "original_name" - they were saved but missing from get_acpt_field(). They are returned again (Ticket #1437).
Length limits counted bytes - Min/Max length on meta and form fields rejected accented text the browser had accepted. Limits now count characters, as the browser does (Ticket #1439).
Date & time values in the canonical format were rejected - the date check was inverted: a Date & time field saved as 2026-10-26 14:30:00 (from code, the REST API or an import) failed validation. It is now accepted, like every other date format the field can store.
Saved ACPT blocks showed as unsupported - "Your site doesn't include support for this block" appeared when the editor parsed the post before ACPT registered its blocks, and on post types registered on init (GeneratePress Elements, most plugin CPTs) the blocks and their styles weren't registered server-side. Both are fixed (Ticket #1441).
Image fields printed the alt text in dynamic block templates - {{ acpt_box_image }} printed the alt text or title, so broke. Image, File and Gallery values now print their URL and still answer .alt, .title, .id and the other attachment properties (Ticket #1436).
Bricks: query filters didn't work on CCT columns - on a post type whose fields come from a CCT, filter elements (Select, Checkbox, Range...) had no options and never narrowed the loop. They now index and filter the CCT column values (Ticket #1434).
WPML / Polylang: media fields showed the same attachment in every language - the generated wpml-config.xml didn't list the attachment ID key of Image, Gallery, File, Video, Audio and Image slider fields. It does now, with the field's own translation settings (Ticket #1432).
Test suite on WordPress 7.2 (no change for users) - two tests expected HTML exactly as WordPress 7.1 sanitized it. The tests now pass on both versions.

Earlier versions