Skip to content

ReDock for Elementor

On a site that runs Elementor, ReDock for Elementor lets the agent list the widgets, read a page, change one element and regenerate the CSS.

  • Runs with: ReDock Desktop, on a local WordPress site that runs Elementor
  • Elementor: Elementor’s classic document format. A page saved in the newer atomic format is refused, and the refusal names the page.
  • Undo: A WordPress revision on every change

The agent reads the page as Elementor stores it, addresses a single element by its own id, changes the setting you asked for and nothing else, and checks the saved page afterwards. A stale read is refused with the fresh state rather than written over.

  • It lists the widgets the site offers and describes each one’s controls.
  • It regenerates the page’s CSS after a change, so what is served matches what was saved.
  • A page saved in Elementor’s newer atomic format is left alone, and the reason is named.

ReDock Desktop looks at the site’s plugins and installs the companion only when Elementor is active. On a site without Elementor nothing is added.

A row on a site’s Overview in ReDock, headed ReDock Elementor, saying the site runs Elementor and the ReDock Elementor companion is not installed so its Elementor pages cannot be read or pinned, with a button that installs it in one press and a link to download the zip and upload it by hand instead.

Writes go through Elementor’s own save, so the change appears in the page’s revisions and can be put back from there.

Elementor elements also carry their own persistent id, which is what a pinpoint uses to find the same element again after the page has been reworded.


Download ReDock Desktop, or open ReDock Web.