cwp bricks post-types

cwp bricks post-types [flags]

cwp bricks post-types groups the commands below and takes no action of its own; run it alone and it prints its help.

Flag	What it does	Default
--with-agent	with —dry-run on a host with no shell: install and remove the PHP agent so the plan is real	off

Subcommand	What it does
cwp bricks post-types list	List the builder-enabled post types (read-only)
cwp bricks post-types enable	Open the Bricks builder for a post type
cwp bricks post-types disable	Stop the Bricks builder opening for a post type

What it does

cwp bricks post-types controls which post types the Bricks builder will open for: bricks_global_settings.postTypes.

This setting is the reason registering a custom post type is not enough. Deploy the site plugin and confirm the post type exists on both sides. The builder still will not open for it until it is in this list, and nothing anywhere says why. cwp doctor reports the gap per environment and points here.

It is database state, so it travels downward only: enabling it locally never reaches production. So these commands take an environment. Against a remote that is an upward write with the usual guards.

What it does not do

It does not register post types. Those belong in your site plugin, in code. This setting only decides whether Bricks will edit one that already exists.

It writes no other Bricks setting. The ability merges by key, so customCss and the rest of that option never round-trip.