v1.11.1

Full Changelog: v1.11.0...v1.11.1

v1.11.0

Full Changelog: v1.10.1...v1.11.0

v1.10.1

Fixed

• Troubleshoot mode would sometimes say it "can't see the live page" and defer to the Mativus development team even after the user had pasted the exact HTML/classes causing the problem (e.g. a Bootstrap mb-0 class overriding an added margin). Pasted HTML, class names, inline styles, and copied DevTools output are now treated as authoritative evidence, and the assistant recognises common Bootstrap 5 utility classes on sight.
• Rebalanced when Troubleshoot mode hands off a fix vs. recommends the development team: naming a specific competing class (e.g. a utility class) now results in a confident hand-off (raise specificity or add !important) rather than an unnecessary deflection.

Added

• When there isn't enough evidence to diagnose an issue, Troubleshoot mode now guides non-developers step by step: attach a screenshot, or right-click the specific element described on the page → Inspect → Copy element/outerHTML, escalating to Copy styles if still unclear.
• After 3+ back-and-forth attempts with no confident cause identified, it now stops asking questions and recommends the Mativus development team instead of continuing to guess.

Full Changelog: v1.10.0...v1.10.1

v1.10.0

Added

• New Troubleshoot mode alongside Generate/Ask-Plan/Build, built for non-technical web designers. Instead of jumping straight to CSS (and stacking redundant overrides), it explains what's likely causing a styling problem in plain language first, and recommends contacting the Mativus development team when the cause is structural (e.g. a competing Bootstrap/utility class, inline styles, JS-driven behaviour).
• When the cause is unambiguous and safely fixable with CSS, Troubleshoot mode never writes CSS itself — it hands off a copy-paste instruction in a distinct card with a one-click "Use in Ask/Plan" button, so the existing Ask/Plan → Generate pipeline (with its breakpoint/native-settings handling) produces the actual CSS.
• Troubleshoot chat history is tracked separately from Ask/Plan history per component.

Full Changelog: v1.9.2...v1.10.0

v1.9.2

Added

• The AI CSS advisor now refuses to suggest JavaScript (scripts, event listeners, IntersectionObserver, onclick attributes, etc.) in any of its responses, since only the Custom CSS field can be edited on the site. When a request can only be achieved with JavaScript, it now says so plainly and advises contacting the Mativus development team to request the change.

Full Changelog: v1.9.1...v1.9.2

v1.9.1

Fixed

• "Could not locate the Global Custom CSS field" error when saving CSS as a global style on sites where Global Custom CSS is defined via a field group pinned to one specific post (a "Post is equal to X" ACF location rule), rather than an ACF Options Page. resolve_global_css_post_id() now detects this pattern automatically in addition to Options Pages.

Full Changelog: v1.9.0...v1.9.1

v1.9.0

Added

• "Save as global style" checkbox next to Copy/Insert on generated CSS snippets. When checked, the Insert button retargets to append the snippet into the site-wide Global Custom CSS field (Theme Settings) instead of the local component field, with a labeled source comment.
• New rjm_save_global_css AJAX endpoint; storage location is resolved at runtime (ACF Options Page detection), overridable via the rjm_css_advisor_global_css_post_id filter.

Full Changelog: v1.8.4...v1.9.0

v1.8.4

Full Changelog: v1.8.3...v1.8.4

v1.8.3

Full Changelog: v1.8.2...v1.8.3

v1.8.2

Full Changelog: v1.8.1...v1.8.2