ACPT plugin review and common issues

After creating a custom post type in ACPT, flush the WordPress rewrite rules: go to Settings → Permalinks and click Save. If the post type still does not appear, verify in ACPT → Post Types → [your CPT] → Settings that “Public” and “Show in Menu” (show_ui and show_in_menu) are enabled. Also check if a WordPress user role restriction is preventing the post type menu from displaying — if the CPT has a custom capability type, ensure your Administrator role has those capabilities assigned.

Field save issues in ACPT can result from: (1) a REST API conflict — ACPT Pro uses REST API-based saving for Gutenberg compatibility; disable Gutenberg for the affected post type temporarily to test if classic meta box saving works; (2) a nonce conflict with another plugin modifying the edit post nonce; (3) the field name containing characters not valid for WordPress meta keys — use only alphanumeric characters and underscores; (4) PHP error during the save hook — enable WP_DEBUG and check the debug log for errors during post save.

Relationship fields in ACPT require the related post type to have published posts for the select box to populate with options. Verify: (1) the target post type has at least one published post; (2) the relationship field configuration points to the correct post type slug; (3) if using a bidirectional relationship, both post types must be created in ACPT or registered by another method. If the post type exists and has posts but the select is empty, check browser DevTools Network for failed AJAX requests when the relationship field is rendered in the admin.

ACPT Pro includes a Block Types feature that creates Gutenberg blocks backed by ACPT meta field groups. Go to ACPT → Block Types → Add New. Define the block name, icon, category, and description. Add meta fields that become the block’s sidebar input. Create a PHP template file that ACPT uses to render the block’s frontend output using acpt_get_block_field() to retrieve field values. Register the block template path in ACPT → Block Types → [block name] → Template. This creates a server-rendered Gutenberg block without JavaScript.

ACPT includes native Bricks Builder integration. In the Bricks Builder editor, ACPT meta fields are available as dynamic data sources through the Bricks Dynamic Data system. Select any Bricks text or image element, click the Dynamic Data icon, and select “ACF/ACPT” to choose an ACPT field as the dynamic value. For loop-based displays (showing multiple related posts or repeatable field data), use the Bricks Query Loop combined with ACPT relationship or repeater fields as the data source.

At the same $49/year single-site price, ACPT includes built-in CPT and taxonomy creation (ACF originally required CPT UI separately), a more modern admin interface, and native Bricks/Oxygen Builder support. ACF Pro has a significantly larger community, more tutorials, more third-party integrations, and a longer track record on production sites. For developers who value modern UI and prefer Bricks or Oxygen over Elementor, ACPT is a compelling ACF Pro alternative. For teams heavily invested in the ACF ecosystem or who need the largest possible community support, ACF Pro remains the safer long-term choice.

ACPT free covers custom post type creation, custom taxonomies, and basic meta fields — sufficient for most standard custom content modeling projects that do not require Gutenberg block generation or frontend forms. The free version is a genuine standalone tool rather than a restricted teaser, comparable in scope to the free tier of ACF combined with CPT UI.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.