Template conditions

wordpress_get_template_conditions and wordpress_set_template_conditions read and change where a site template shows: which pages get this header, this footer, this archive layout. They need plugin 9.3.1 or later.

They work on the builders below. On any other builder both tools answer supported: false, name what is missing, and do nothing. That answer says nothing about the site's templates.

Elementor Pro, Brizy Pro, GeneratePress Premium, Kadence Pro, Thrive Theme Builder, Blocksy Pro and SeedProd Pro answer that they are not supported yet.

wordpress_get_template_conditions

Each template comes back with:

The builder itself decides who wins. The check runs on sample pages taken from the template's conditions, not on every page of the site, and the answer says so in conflicts_note.

wordpress_set_template_conditions

This changes the live site at once, so ask the person first.

Flags must be real booleans. A list that leaves out an existing exclusion is refused with would_drop_exclusions, so pages kept out of a template stay out unless the person agrees. Sending back a read unchanged writes nothing. A template takes at most 100 conditions, and one condition at most 500 ids or terms.

Sending the same call twice runs it twice, so changing a template back and forth takes effect each time. To make a retry safe after a timeout, send the same _respira_call_id.

Each successful write and undo adds a row to the site's Activity log with the template id.

The write is refused on the Observe and Content site profiles, and on read-only, Builder and Content, SEO and publishing keys, over REST and over the native endpoint. A full access key on an Everything site can use it.

Neutral entries

Every entry has a kind and can have exclude: true.

terms is a list like [{"taxonomy": "category", "term_id": 4}]. On term_archive, {"taxonomy": "post_tag", "all_terms": true} means every term of that taxonomy.

Some builders have no blog condition; Bricks is one, so there use ids with the posts page's id. Anything a builder cannot express is refused by name and nothing is written.

Example

Show this header on every page except two:

{
  "name": "wordpress_set_template_conditions",
  "arguments": {
    "template_id": 591,
    "confirm_live_edit": true,
    "conditions": [
      { "kind": "post_type", "post_types": ["page"] },
      { "kind": "ids", "ids": [583, 582], "exclude": true }
    ]
  }
}

The answer carries snapshot_uuid, the template as it now stands, and render_check.

What render_check means

Respira requests real pages after the write and looks for the template in them.

A page cache in front of the site can keep serving the old header or footer until it is purged. Use wordpress_purge_cache if visitors still see the old one.

An open builder tab can overwrite this

On Bricks, the builder sends every template setting each time someone saves, so a builder tab that was already open still holds the old conditions and writes them back on its next save. Bricks does not mark a template as open, so Respira cannot detect that tab. Tell the person to close any open tab of this template, or to reload it before saving. The answer repeats this in stale_tab_warning.

Undo

Call wordpress_restore_snapshot with the snapshot_uuid from the answer. It puts the conditions back as they were, byte for byte, and changes no other setting on the template.

Conditions from other plugins

A condition Respira has no word for stays where it is. It shows up in unmapped, and a write leaves it untouched unless you name it in remove_unmapped. That includes Bricks' All archives, which can be kept but not created through this tool.

A row saved in a shape Bricks cannot read also lands in unmapped, with the reason. On Bricks 2.3.4 a postType saved as a string takes down every post and page, so if you see that reason, tell the person and remove the row.

Limits

• The builders and versions in the table above.
• Conflicts are checked on sample pages, not every page.
• A Bricks template password and Breakdance or Oxygen custom PHP never leave through a read, and Respira does not write template settings through a page or post meta field.
• Not tested with WPML.
• A read-only key made before 9.3.1 keeps the tool list it was made with, so it needs replacing to read conditions. A full access key is not affected.