Skip to content

cwp bricks post-types

shipped 1.0.0
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.

SubcommandWhat it does
cwp bricks post-types listList the builder-enabled post types (read-only)
cwp bricks post-types enableOpen the Bricks builder for a post type
cwp bricks post-types disableStop the Bricks builder opening for a post type

What it does

Controls which post types the Bricks builder will open for — bricks_global_settings.postTypes.

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

Because it is database state it travels downward only: enabling it locally never reaches production. That is why these commands take an environment, and why doing so against a remote 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 are never round-tripped.