Bricks templates join the Templates library, and EMCP now builds and styles Uncode sites.
- 01NewProUncode. On sites running the Uncode theme, agents can build pages and Content Blocks from Uncode's own elements and its 900 Wireframes sections, and change Uncode's theme options. The WPBakery tools accept 39 Uncode elements (each checked live against Uncode 2.12.8), and edit Content Blocks. A new pair of tools,
uncode-readanduncode-write, lists Wireframes with whether each is ready to insert, prepares Uncode's placeholder images, forms and menus when a section needs them, and reads and changes theme options: values are checked by type, the theme's CSS is rebuilt and checked, and a change made in Theme Options at the same moment is never lost. Every option change and every WPBakery save can be undone from History; preparing Wireframes is the one step that cannot.uncode-writeships switched off. Needs Uncode and Uncode Core 2.12.8 or later. - 02ProFixed (Pro): WPBakery page saves on Uncode sites changed the page and then reported an error. Uncode's copy of WPBakery names the optimized-asset step differently, so the save stopped after writing the page: the element CSS was not rebuilt and the result was not checked. Saves now use whichever step this WPBakery has, and if anything fails after the first change, the page, its WPBakery settings and its recovery snapshots are put back exactly. A failed save no longer drops the oldest recovery snapshot.
- 03NewProBricks templates. Ten Bricks designs join the Templates library, next to the Elementor templates, with a Builder switch to show one or the other. Create page makes a draft page that looks like the demo: the template's global classes and variables are added to the site (classes and variables you already have are never changed), its images are copied into the Media Library, and its fonts and theme style apply to that page only. Add to library puts the layout in Bricks templates instead. Needs Bricks 2.4 or later. Each apply can be undone from History, which removes the page and whatever the apply added, unless another page still uses it.
- 04FixedElementor content added over MCP to a classic page did not show on the front end (#187).
apply-templateand the other Elementor write tools saved the elements, but Elementor marks a page as built with Elementor only when its editor opens, so a page never opened there kept rendering as a classic page. Every Elementor save now marks the page as built with Elementor, the same ascreate-page. - 05NewThe widget tools follow Elementor's Element Manager (#188). Elementor does not render a widget switched off in Elementor > Element Manager, yet the tools added one and returned its id.
list-widgetsandget-widget-schemanow mark disabled widgets,list-widgetslists every disabled element (atomic and third-party ones included), andadd-free-widget,add-pro-widgetand the atomic add tools refuse a disabled widget with an error that says where to switch it back on. - 06Fixed
sideload-imagesaved a file from a link without an extension as.jpg, so PDFs and other files were refused (#189). The file is now named from the server's Content-Disposition filename, then the URL, with the extension taken from the file's real type. The tool's description now says it takes any file type WordPress allows and streams large files that are too big forupload-media, and it gainsfilenameandtimeout(5 to 300 seconds, default 30) inputs. - 07FixedAn empty Screen Options tab covered the top of EMCP screens (user report). A plugin or theme that registers meta boxes on every admin screen made WordPress add the tab over the promo bar. EMCP screens have no screen options and their own help button, so WordPress's Screen Options and Help tabs are now off there; other admin screens keep them.
A brief becomes a real page.