Reorder or remove sections on an Avada or WPBakery page

ContentAdvanced~15 min

Before you start

Plugin version 1.12.0 or newer with Avada or WPBakery Page Builder active, using the tools for the builder that owns the page. The move and remove tools start off, plus the page read for that builder; Remove is a destructive write, so switch it on only for the run. The agent needs edit access to the page. Removing an element needs revisions on and the site keeping more than one per post, or the remove is refused before anything is saved.

The launch banner from spring is still at the top of the home page, and the FAQ you want people to see sits below three other sections. On a builder page, fixing that usually means dragging blocks around in the visual editor and hoping nothing gets nested in the wrong column.

This prompt does it as a short list of single moves and removals, each one confirmed and each one leaving a restore point.

The prompt
I want to tidy the [home] page (id [5]). Take out the [spring launch banner]
section, and move the [FAQ] section so it sits directly [after] the
[testimonials] section.
Tell me which builder owns the page, then read it with the page content tool
and include_structure. List the top-level sections in order with their index,
tag and a few words of their text, so we can name them precisely.
Make no change until I approve the plan. Then do one change per call: first
the move, then the removal, each with the index, tag and fingerprint from the
outline and the page fingerprint from the last read or write. Read the outline
again after each change, because indexes shift. If a removal is refused
because there would be no way back, stop and tell me why. At the end, list
every restore_revision_id in order.

Why this is safe to run

The plan is built from a read, so you approve moves and removals named by index and by a few words of their content, and the agent cannot act on a guess. Every write checks the page fingerprint and the element’s own fingerprint, so a page that changed in the meantime is refused with nothing saved.

Each builder’s nesting rules apply to a move: a container takes rows, a row takes columns, and a move into the element itself or one of its own children is refused. A removal takes the element and everything inside it and leaves every other byte of the page as it was. On WPBakery the fingerprint covers the whole element, so a section that gained content since the read is refused, and the page’s generated CSS is rebuilt after each change.

Remove is the riskier of the two, so the plugin makes it prove there is a way back first. Each write returns restore_revision_id, and Restore revision brings the page back to before that change. These edits are not in the Changes tab. All the tools here start off, are checked against the user you bound the agent to, and land in the Activity Log.

Already connected? Ask your agent for the “reorder or remove sections” recipe, describe the order you want, and it runs the same one-change-at-a-time flow on your own site.

How it works

  1. Read the page outline and list the top-level sections in order.
  2. Agree on each move or removal, naming the element and, for a move, its new neighbour.
  3. Make one change per call with the page fingerprint from the last read or write.
  4. Read the outline again before the next change, since positions shift.
  5. Report every restore_revision_id so any step can be rolled back.

Questions

Can it remove the last section on a page?
No. Avada refuses removing the page's last top-level container, and WPBakery the page's last row or section. Both refuse a change that would leave a row with no column.
Why does a remove need revisions?
Because a revision is the only way back. Both remove tools refuse before saving anything when no revision could bring the element back: revisions off, a site that keeps only one revision per post, or a content type that keeps none, such as an Avada form or off canvas panel, or a WPBakery Grid Builder template.
Does a move rewrite the section?
No. The element's stored text moves byte for byte with everything inside it. A move to the place it already has saves nothing and reports moved false.