Novamira Pro NULLED 1.9.0

• New: Blocksy specialization (requires the Blocksy theme 2.1.47 or newer, with Blocksy Companion and Companion Pro also supported): AI agents can set up the theme's global design, per-page layout, header and footer, and Companion features. A companion skill walks agents through the workflows.
• Tweak: Divi modules are now written through the dedicated Divi tools, so what an agent builds saves and renders as expected.
• Tweak: Kadence pages on a site where the block editor cannot run now come back with that as the reason, so the agent reports it instead of working around it.
• Tweak: Novamira Pro specializations can now be turned on or off with their related abilities and skills from the Novamira Features page (requires Novamira 1.12.0 or newer).
• Tweak: Uninstalling Novamira Pro now deactivates its license and cleans up after itself, handing any Context instructions over to the base Novamira plugin and removing its own settings, caches, scheduled checks, and admin notices.
• Fix: Elementor pages now open in the editor showing the content an agent has just written, instead of an older editor autosave. Writes aimed at a revision or autosave id are refused with a message naming the parent post to target.
• Fix: An Elementor write that does not persist now comes back as an error instead of a success reply, so the agent can act on it rather than carry on with a page that never changed.
• Fix: Elementor content and styles that arrive in the wrong shape are now refused with a validation error that names the offending element and the shape expected there, instead of being saved as a style that does nothing.
• Fix: Divi 5 pages composed one section at a time now open complete in the Divi builder, which previously showed only the first section even though the front end rendered them all. Pages built before this release are put back together on the next write.
• Fix: The Divi 5 tools now appear on sites that run Divi through a child theme whose parent theme folder was renamed.
• Fix: Meta Box post types can now be kept off the public site while staying editable in wp-admin, through the standard WordPress visibility settings.
• Fix: The Code Snippets tools work again on Code Snippets 3.10 (free and Pro), and the supported older versions keep working unchanged. AI agents are also told when a snippet is locked, when an edit was not applied, and which snippets a deleted Pro condition was gating.
• Minor fixes

• New: Spectra Blocks specialization (requires the Spectra Blocks plugin 0.0.8 or newer; the Spectra Blocks Pro add-on is detected when present). AI agents can check the install state and version pair, browse the block catalogue with its activation state, read the plugin settings including reCAPTCHA configuration and Global Block Styles, and inspect Popup Builder popups down to their block markup. A companion skill covers the workflows and keeps the legacy Spectra (UAGB) plugin clearly separate.
• Tweak: The Kadence, GenerateBlocks, and GeneratePress build skills now teach agents about editor-assigned block settings (per-block style IDs and layout markers). With the upcoming Novamira release the Block Editor Queue fills them in automatically at finalization; on Novamira 1.11.3 and earlier the skills instruct agents to supply them by hand, so composed blocks no longer save unstyled or with a row's columns collapsed while the queue reports success.
• Fix: The Spectra build and integration skills now walk agents through the real Block Editor Queue pipeline for composing uagb/* content, where they previously pointed at per-block editing tools that do not exist, stopping every Spectra page build at the first step. They also cover Spectra's editor-assigned block_id, so composed blocks no longer save unstyled on Novamira 1.11.3 and earlier.
• Minor fixes

​

• New: Voxel specialization (requires the Voxel theme 1.7.8.3 or newer). AI agents can build a Voxel site's content model, create and edit listings, set up the templates each post type renders through, and read its commerce and community data
• Fix: WordPress admin pages keep loading normally on sites where the license status is refreshed while the page is being built, instead of ending in a critical error.
• Minor fixes

• New: Oxygen 6 specialization (requires Oxygen 6.0 or newer): AI agents can build pages and templates, style them through the global design system, bind live content and loops, and manage form submissions. A companion skill walks agents through the workflow.
• Tweak: Feedback reports on Novamira now have a place to go: the agent points you to https://novamira.ai/feedback, where you send the report yourself after reviewing it. The agent also offers to prepare one when the same problem keeps coming back after it has genuinely tried to fix it, instead of waiting for you to ask.
• Minor fixes

* New: Weglot specialization (requires Weglot 5.0 or newer). AI agents can set up the connection, configure the original and translated languages, style the language switcher, and control which pages are translated and under which web addresses. A companion skill covers the boundaries.
* Fix: AI agents can now call the tools that take no required input, whatever MCP client they run in. Those tools previously came back with an input error unless the client sent an empty object explicitly.
* Fix: The Elementor editor keeps working inside the Novamira Visual workspace on Elementor 4.1 and newer. Novamira Visual now turns off Elementor's editor isolation policy so the workspace can drive the editor, and site owners who prefer Elementor's isolation can restore it with the novamira/visual/use_elementor_document_isolation filter.
* Fix: Bricks operations that fail now come back to AI agents as real errors instead of replies that look like success, so an agent no longer carries on after a failed color palette, global class, variable, theme style, or dynamic data operation.
* Fix: Bricks template display conditions written by AI agents are always stored in the array form Bricks reads, on every supported Bricks version: recoverable scalar values are normalized to arrays with a warning, while malformed condition containers or entries are rejected with a clear error before anything is saved (Bricks 2.4 skips malformed scalar values entirely).
* Fix: Bricks code elements written by AI agents now honor the BRICKS_LOCK_CODE_SIGNATURES constant on sites that lock code-signature generation, on every supported Bricks version: a write that needs new code signatures comes back with a clear error naming the affected code elements and how to unlock. On Bricks 2.4 this also keeps unsigned code, which would render empty, off the page.
* Fix: Breakdance pages built by AI agents now come out styled without reopening the builder, because Breakdance's CSS cache is rebuilt after every write to the page.
* Fix: Breakdance element design controls are now fully visible to AI agents, including the grouped ones (the Posts Loop list, the Div layout and background) that previously came back as a single "Error" placeholder, so those elements can be styled instead of left at their defaults.
* Fix: Breakdance elements that cannot render until they are configured, such as a form element with no form picked or a checkout element outside checkout, no longer block later edits to the same page. The element is still added and the agent is told the page will not display it until it is set up.
* Fix: Breakdance raw code elements, and raw page content written straight into WordPress on a Breakdance site, now need your explicit confirmation before an AI agent writes them.
* Fix: Beaver Builder pages written by AI agents no longer fail just because the page contains a column group nested inside a column, a normal Beaver Builder structure that reads always accepted. Column group nodes now allow a row or a column as parent.
* Fix: Mosaic Builder design-system variables can now have their value set by AI agents (color, length, font, etc.), not just their name, so recoloring or restyling no longer requires deleting and recreating variables or falling back to inline styles.
* Fix: Mosaic Builder utility classes can now be styled by AI agents per state (hover, focus, etc.) and breakpoint directly, instead of falling back to raw PHP or database edits that could put the site in a critical error.
* Fix: Mosaic Builder HTML attributes (data-*, aria-*, role, etc.) written by AI agents now carry the identifier Mosaic's own validation expects, so they survive a theme export and import instead of silently disappearing.
* Fix: Mosaic Builder component instances can now have their per-instance override edited or cleared directly by AI agents, instead of falling back to raw database writes that could corrupt the design system.

* Tweak: Fluent Forms listing and form building are cleaner for AI agents: listing notifications returns compact rows by default (expandable on request), listing submissions hides trashed entries and searches the IP and browser, and building a form now warns when a setting is passed at the wrong level or a form is left with no fields.
* Fix: If the license server was unreachable, admin pages could slow to a crawl. This no longer happens.
* Fix: Fluent Forms forms and fields built by AI agents now render reliably on the page and in the editor. Newly created forms, all field types (including Address, Name, and choice fields), field settings like placeholder, max length and number min/max/step, and the published or unpublished status now take effect instead of silently producing empty output.
* Fix: A range of Fluent Forms robustness fixes: notifications added by AI agents now send on submission without overwriting hand-made ones, per-form permission checks are enforced, confirmation redirects and email headers reject unsafe values, list filters written as text work, concurrent settings edits no longer overwrite each other, and listing or exporting large submission sets no longer risks exhausting memory.
* Minor fixes

* New: Astra specialization (requires Astra 4.13.5+, free theme plus optional Astra Pro Addon). AI agents can edit the theme settings, color palettes, Header/Footer Builder, and per-page overrides, with more areas unlocked by Astra Pro; a companion skill covers the two tiers.
* New: Avada theme specialization (requires Avada 7.15+). AI agents can edit a curated set of Fusion Theme Options and manage the Global Colors and Global Typography presets; a companion skill covers the boundaries.
* New: Avada Fusion Slider support (requires Fusion Core 5.15.5 or newer, bundled with Avada). AI agents can list the site's sliders and edit their display settings and slides.
* New: OceanWP specialization (requires OceanWP 4.1+, plus the optional Ocean Extra companion). AI agents can edit a curated set of Customizer settings and per-page layout, and with Ocean Extra mount Library templates and turn the Ocean Extra modules on or off; a companion skill covers the boundaries.
* New: Spectra specialization (requires Spectra 2.19+, free plus Spectra Pro). AI agents can browse the block library, manage Popup Builder popups end to end, and turn individual blocks on or off; a companion skill covers the workflow.
* New: Spectra One specialization (requires Spectra One 1.2.2+). AI agents can edit the Global Styles, navigation, and template parts, apply a style variation, and export the whole design as a reusable snapshot.
* Tweak: WooCommerce abilities now register only when WooCommerce is active and at the minimum version, so sites without a store no longer list the WooCommerce category or its setup check.
* Tweak: The Bricks page-building skill now covers query filters and pagination, and the setup check reports whether Bricks' query filters are enabled.
* Tweak: Divi 5 content written by AI agents can no longer carry inline style attributes, since those cannot be edited from the Visual Builder controls. The agent gets a clear error pointing to the module's native settings, and inline styles go through only with an explicit opt-in.
* Tweak: Bricks native dark mode can now be set up by AI agents (requires Bricks 2.2 or newer): palette colors accept a dark variant, and reading the palette reports whether the site is ready for Bricks' toggle-mode element.
* Tweak: Meta Box value writes by AI agents can now be scoped to a field group, so a field that does not belong to the group is declined up front instead of being saved as a stray custom field.
* Fix: Elementor pages that AI agents build now import cleanly on any Elementor site, so a page saved as a template moves between sites without errors.
* Fix: GeneratePress Elements now let AI agents read and set their display, exclude, and user conditions, completing the path to building an Element end to end.
* Fix: The Bricks page-building skill now teaches the correct query-loop grid pattern (the loop goes on the card, not the grid container), where Bricks previously rendered one grid per post.
* Fix: Bricks trees written by AI agents now keep parent and children references consistent in every case, and a write repairs any inconsistent link already stored on the page and says so in a warning.
* Fix: Meta Box field groups saved by AI agents no longer fail on Meta Box 2.6.0 and newer when a field carries datalist suggestions.
* Fix: Meta Box field-group reads by AI agents now return the values for every field in the group, where they previously came back empty.
* Fix: Meta Box post types and taxonomies created or edited by AI agents now get working permalinks right away, with no need to re-save the WordPress Permalinks screen.
* Fix: Breakdance Pro licenses are now recognized by AI agents, so a Pro site works with the Pro feature set instead of the free one.
* Fix: Breakdance elements now expose their Settings tab options to AI agents (custom CSS classes, display conditions, draft state), so those can be read and edited like any other element option.
* Fix: Breakdance template abilities now accept the post id in the same form the element abilities use, so AI agents no longer hit input errors when moving between templates and elements.
* Minor fixes

* New: Bricksforge specialization (requires Bricksforge 3.1.8 or newer). AI agents can set up and manage the Bricksforge add-on for Bricks. They turn Bricksforge tools and custom elements on or off (Pro Forms, Popups, Maintenance Mode, Mega Menu, and more), and build Pro Forms through the Bricks page tools, with the field, choice, multi-step, condition, and layout details handled for them. They create and manage Bricksforge popups (opened on page load, click, or scroll, with a Bricks template as the content), and manage the Email Designer templates that restyle WordPress and WooCommerce emails: which emails each template replaces, its subject, whether it is active, and its theme. A companion skill teaches the form recipe and the Bricksforge specifics, and points agents to a live browser workspace for the visual parts (email layout, animations).
* Fix: Responsive style overrides (tablet and phone) that AI agents set on Divi 5 modules now take effect on the page. When an agent provides a breakpoint override, it is stored in the nested shape Divi 5 reads, whether the agent writes it as a nested object or as a single dotted path, so mobile and tablet spacing, sizing, and typography land as intended. This applies when editing a module, adding a module, and setting a page's content, and the agent is told the native nested shape so its next write matches what the builder stores.
* Minor fixes

* New: Novamira Visual support for Elementor and Bricks. Novamira Visual is the new live browser workspace in the free Novamira plugin where you watch your AI agent work on your site in real time. Inside it, AI agents can now build and edit Elementor and Bricks pages right in the open editor, so you watch the work happen. This is an early, experimental integration, separate from the standard Elementor and Bricks specializations, so the output is different. For development and staging sites. We would love your feedback in the community group: https://www.facebook.com/groups/novamira
* Minor fixes