Manage Ultimate Addons for Elementor with AI

What we learned testing it

Behavior the ability descriptions do not mention.

• UAE's abilities are off by default. Turn them on in wp-admin under UAE > Settings > AI Tools: Enable Abilities registers them, and Enable Edit Abilities (on by default) adds the ones that change things. With only the first on, the AI can read but not build.
• When two published templates of the same type match a page, UAE shows the newest one, not the most specific. To give one page its own header, also exclude that page from your site header.
• A copy made with uae/templates-duplicate keeps the original's display rules and starts as a draft. Change its rules before you publish it, or it takes over every page the original covers.
• uae/display-rules-update replaces each field you send (include, exclude, user roles) and keeps the ones you leave out. To add one exclusion, read the template first and send the whole list.
• Some setting keys in UAE's own build examples do nothing: the search icon color is toggle_color, the site title color heading_color, the copyright text color title_color. A wrong key saves without an error, so the AI checks uae/builder-get-schema for every widget.
• uae/builder-build replaces everything on the post it builds. Use it on new templates or copies, and builder-update-widget or builder-insert-widget on a live one. Undo keeps one level.
• Deleting a template or page and removing a widget ask for your approval in the browser through WPVibe first, unless you turned approvals off for the site. Turning all widgets off (widgets-bulk-toggle) or turning off unused ones does not ask: turning them all off removed the menus from a live header in testing, and unused means unused in published content, so widgets that only drafts use are turned off too.
• Site Logo shows a placeholder image when the site has no logo set; use Site Title instead, or set a logo first.
• uae/settings-update can change uae_usage_optin, UAE's opt-in to share usage data with its maker. Leave it to the site owner.
• By UAE's source, turning the Scroll to Top extension on does not show the button by itself: it also needs Enable Scroll To Top in Elementor's Site Settings, and it shows only on pages built with Elementor.
• A before-footer template needs a UAE footer too: on a theme UAE does not support natively, a before-footer on its own replaced the theme's footer on every page it covered in testing.
• With UAE's default theme support (Option 1) on a theme it does not support natively, UAE prints its own top of the page in place of your theme's header.php, so anything the theme writes there directly, such as classes on the <body> tag, is dropped. On our test theme that took away the pages' font and background until the header went back to draft. The header recipe checks for it; UAE > Settings > Theme Support also offers Option 2, which hides the theme's header and footer with CSS instead; we have not tested it.
• Tested on a classic theme UAE does not list as supported, with the default compatibility method. uae/theme-get-info lists the themes it supports natively. Block themes were not tested; UAE's default method relies on the classic header and footer hooks.