=== Microthemer Lite - Visual Editor to Customize CSS ===

Contributors: bastywebb, joseluiscruz, ahrale
Donate link: http://themeover.com/microthemer/
Tags: css, customize, visual editor, google fonts, responsive
Requires at least: 6.0
Tested up to: 6.9
Requires PHP: 5.6
Stable tag: trunk
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

A visual editor to customize the CSS styling of anything on your site - from Google fonts to responsive layouts.

== Description ==

A light-weight yet powerful visual editor to customize the CSS styling of any aspect of your site, from Google fonts to responsive layouts. Microthemer caters for both coders and non-coders, and plays really well with page builders like Elementor, Beaver Builder, and Oxygen.


= Feature list =

1. Style anything
1. Use with any theme or plugin
1. Point & click visual styling
1. Code editor (CSS, Sass, JS)
1. Sync code editor with the UI
1. Customisable breakpoints
1. HTML and CSS inspection
1. 150+ CSS properties
1. Dark or light theme
1. Custom toolbar layouts
1. Work with any CSS unit
1. Color picker with palettes
1. Slider, mousewheel, keyboard adjustments
1. In-program CSS reference
1. History
1. Draft mode
1. Global or page-specific styling
1. Import & export
1. Light-weight
1. Minify CSS code
1. Keyboard shortcuts
1. Deep integration with Elementor, Beaver Builder, Oxygen
1. Multisite support
1. Uninstall MT, but keep your edits
1. **[Pro]** CSS grid (drag & drop)
1. **[Pro]** Flexbox
1. **[Pro]** Stock SVG mask images
1. **[Pro]** Transform
1. **[Pro]** Animation
1. **[Pro]** Transition


= Lite VS Pro =
This lite version limits you styling 15 things, and doesn't include the features marked [Pro] in the list above. To unlock the full program, you can <a href="https://themeover.com/">purchase a license</a> (monthly, annual, or lifetime).

= Useful links =

- <a href="https://themeover.com/">Website</a>
- <a href="https://themeover.com/introducing-microthemer-7/">Video docs</a>
- <a href="https://livedemo.themeover.com/setting-up-demo-site/?create_demo">Live demo</a>
- <a href="https://themeover.com/forum/">Support forum</a>
- <a href="https://www.facebook.com/groups/microthemer">Facebook group</a>

= Author note  =

Hello everyone, my name is Sebastian. I've designed Microthemer for developers as well as beginners. My aim is to level up beginners by exposing the CSS code Microthemer generates when using the visual controls. This is of course helpful for developers who may wish to make manual edits. Some developers use Microthemer as an in-browser CSS or Sass editor, and just lean on the interface for element selection or more advanced properties like filters, grid, and animation.

I've been happily developing Microthemer and supporting users of varying technical experience in my forum for many years now. I'm always ready to answer questions about the software and help out with CSS hurdles. Please don't hesitate to get in touch!


== Installation ==

1. Click the 'Plugins' menu option in WordPress.
2. Search for 'Microthemer'.
3. Install and activate the plugin.
4. Go to the 'Microthemer' menu option.
5. Start customizing the appearance of your site.

== Changelog ==

= 7.5.2.9 (Dec 5th, 2025) =

# Enhancement (Microthemer & Amender)
* New switch to prioritise AI assistant speed vs thinking time.
* Improved AI reliability - less formatting errors resulting in "AI error" message.

= 7.5.2.8 (Nov 28th, 2025) =

# Bugs fixed (Amender)
* The code editor was uneditable when copying a selector or folder.
* The message to signal a snippet is synced did not immediately show when copying a selector.

= 7.5.2.8 (Nov 19th, 2025) =

# Enhancements (Amender)
* Amender beta status upgraded to production ready.
* Improved database query performance.

# Bugs fixed (Microthemer & Amender)
* PHP warning due to missing sprite image.

= 7.5.2.5 (Oct 30th, 2025) =

# Change (Microthemer & Amender)
* Reorganised some PHP class methods.

= 7.5.2.4 (Oct 18th, 2025) =

# Bugs fixed (Amender & Microthemer)
* Possible error notification could display unnecessarily "action_after_repaint: no valid window context".

= 7.5.2.3 (Oct 18th, 2025) =

# Bugs fixed (Amender)
* Amender changes not being saved due to a possible PHP error creating the database table "WordPress database error. Specified key was too long; max key length is 1000 bytes for query CREATE TABLE wp_micro_content".
* On PHP 8.4, activated Amender produced a "Plugin produced unexpected output" warning due to some deprecation warnings from the plugin updater script.

= 7.5.2.2 (Oct 18th, 2025) =

# Bugs fixed (Microthemer)
* Microthemer was mislabelled "Amender" in the WordPress menu, due to the wrong PHP constant being set for the plugin name.

= 7.5.2.1 (Oct 17th, 2025) =

# Enhancement (Amender)
* The "Re-target current selector" option also updates Amender "add: css" if the single selector is being edited.

# Bugs fixed (Amender)
* The HTML inspection pane stripped preceding space from classes dynamically inserted by Amender.
* The preference for enabling Microthemer as an addon for Amender was misaligned.
* The popup for installing Microthemer as an addon for Amender persisted when displaying the npm installer popup.
* The snippet usage count did not immediately update when reusing a snippet.
* Creating a new snippet did not reset the usage count header.
* All valid (non-deprecated) HTML attributes can be used in the aspect field e.g. tabindex, autocomplete, etc.
* Snippet name field was not cleared when using the clear icon for all fields.

= 7.5.2.0 (Oct 13th, 2025) =

# Bugs fixed (Amender)
* When setting a selector for moving elements, the action / aspect values were not auto-set, so the move did not happen.
* Move relative syntax did not work for all examples e.g. next().

= 7.5.1.9 (Oct 7th, 2025) =

# Change
* When default text is clicked and becomes blue (indicating it has been customised), it is saved. This is for interface consistency and snippet naming reasons.

# Bugs fixed (Amender)
* Errors in user JavaScript functions were not displayed at the top right of the interface.
* Clearing all fields did not clear the TinyMCE editor.
* Loading an existing snippet did not live update the page when choosing "Edit synced snippet".

= 7.5.1.8 (Oct 3rd, 2025) =

# Bugs fixed (Amender)
* The review time in milliseconds was an underestimate due to a calculation error. Typical server-side HTML edits are done in 2-10 milliseconds (still extremely fast, but more than the sub-millisecond time reported previously).

= 7.5.1.6 (Sept 30th, 2025) =

# Enhancements (Microthemer & Amender)
* AI example prompts.
* Option to disable the AI assistant panel.
* New 'outview' event which fires when an element that was in view scrolls out of view.
* Provided some sensible defaults for the AI assistant to use when creating GSAP animations.
* Synced snippet usage is tracked and can be searched.

# Enhancements (Amender)
* Customize the default Amender change tabs.

# Bugs fixed (Amender)
* No prompt to install a dependency was presented if the AI assistant created a GSAP / Three.js effect.

= 7.5.1.5 (Sept 4th, 2025) =

# Bugs fixed (Microthemer & Amender)
* Clicking a folder search item did not always collapse the folders pane to make the editing fields visible.

# Bugs fixed (Amender)
* The rich text editor was not being cleared when using the new option to "Create new snippet (without overwriting current)".
* Switching between html, innerHTML, and text aspects did not always copy the content to the new snippet type correctly.
* Page content did not live update when deleting a snippet that was active on the current page.
* Page content did not live update when disabling / un-disabling folders or selectors.

= 7.5.1.4 (Sept 1st, 2025) =

# Change (Amender)
* The delete snippet icon has moved to the snippet search menu, for each snippet item listed.
* Instead of the delete icon, there is a start new snippet icon (without overwriting the current snippet).

# Enhancement (Amender)
* The state of expanded vs collapsed snippet options persists across page refresh.
* A notification displays when editing a synced snippet, with an option to detach it.

# Bugs fixed (Amender)
* Stale Amender snippets could linger in the wp_micro_content database table when publishing settings.
* Empty snippets could accumulate without being cleaned.

= 7.5.1.3 (August 25th, 2025) =

# Bugs fixed (Amender)
* Removing a parentWrapper discarded siblings of the selected element.

= 7.5.1.2 (August 24th, 2025) =

# Bugs fixed (Microthemer & Amender)
* JS error when duplicating a folder or selector.

= 7.5.1.1 (August 20th, 2025) =

# Bugs fixed (Microthemer & Amender)
* When updating folder logic for a folder with no styles or settings, the save button would endlessly spin.

= 7.5.1.0 (August 15th, 2025) =

# Enhancement (Amender)
* Added a shortcut to enable Microthemer as an addon for Amender.

= 7.5.0.9 (August 15th, 2025) =

# Bugs fixed (Amender)
* Background videos could default to low resolution with certain files.

= 7.5.0.8 (August 14th, 2025) =

# Enhancement (Amender)
* Responsive videos are also supported now, reducing file size on mobile but maintaining clarity on high resolution screens.
* Static Cloudflare CDN urls are used for stock images and video for maximum performance.

= 7.5.0.7 (August 6th, 2025) =

# Enhancement (Amender)
* The AI assistant can now use stock images and videos to insert or replace media responsively using "srcset". This includes adding background videos to sections.

# Bugs fixed (Microthemer)
* Possible PHP error on versions older than PHP 8: "unexpected '=>' (T_DOUBLE_ARROW)" in class-json-modernised.php on line 45.

= 7.5.0.6 (July 31st, 2025) =

# Bugs fixed (Microthemer & Amender)
* JavaScript error using the AI assistant if Sass support was enabled via the preferences.

= 7.5.0.5 (July 28th, 2025) =

# Bugs fixed (Microthemer)
* PHP Fatal error upon install: Uncaught Error: Undefined constant "TVR_CONTENT_EDITOR".

= 7.5.0.4 (July 27th, 2025) =

# Bugs fixed (Amender)
* Undo did not work for remove parent/childWrapper.
* Lazy load did not work on WP multisite.

= 7.5.0.2 (July 25th, 2025) =

# Enhancement (Amender)
* WordPress dashboard plugin updates enabled for Amender.

= 7.5.0.1 (July 25th, 2025) =

# Bugs fixed (Microthemer & Amender)
* The plugin for loading assets when deactivating the editor was not working. It has now been renamed "Microloader", going back to a previous system. It works for Amender content changes as well as CSS.

# Bugs fixed (Amender)
* Amender did not run global changes if no conditional changes were also present.
* The Publish button remained inactive even after an Amender license was supplied.
* The red unlock icon persisted after Amender activation.

= 7.5.0.0 (July 24th, 2025) =

# Enhancement
* Amender (beta): content editing addon or standalone plugin with support for GSAP, THREE.js, Alpine.js and Chart.js.

= 7.4.1.8 (June 16th, 2025) =

# Bugs Fixed
* IP address was not shown when certain firewall issues prevented activation.

= 7.4.1.7 (June 16th, 2025) =

# Bugs Fixed
* Possible PHP error.

= 7.4.1.6 (June 16th, 2025) =

# Bugs Fixed
* Existing computed CSS values were not shown over the input fields in the previous release.

= 7.4.1.5 (June 15th, 2025) =

# Bugs Fixed
* PHP code for loading assets manually failed because a file was not copied to /wp-content/micro-themes.

= 7.4.1.4 (May 8th, 2025) =

# Bugs Fixed
* AI code editor was not resizing the text area dynamically when drag-adjusting the column width.
* Removed some code that may have been triggering a false positive malware warning in CPGuard. CPGuard was deleting a core Microthemer file, which caused a fatal error in the admin area. CPGuard have recognised the false positive and updated their scanner rules too.

= 7.4.1.3 (May 5th, 2025) =

# Bugs Fixed
* Uncaught TypeError: e.replace is not a function.

= 7.4.1.2 (May 5th, 2025) =

# Bugs Fixed
* There was a trailing comma in PHP code that could cause an issue for older PHP versions.

= 7.4.1.0 (May 2nd, 2025) =

# Change
* AI model options removed - that was left visible by mistake. They are just for testing models during my development of MT.

# Bugs Fixed
* The AI message was repeated in the chat if resending after a connection error.

= 7.4.0.9 (April 30th, 2025) =

# Enhancements
* Instant undo falls back to a server revision if not available in the browser cache.
* Faster AI responses for users outside the US.

# Bugs Fixed
* Box-shadow and text-shadow were not syncing between the code editor and visual controls.
* AI retry could sometimes re-apply changes to the previously selected element.
* Media query tabs were not dynamically added if the AI created a new breakpoint.

= 7.4.0.8 (April 24th, 2025) =

# Enhancements
* AI can detect pseudo elements ::before and ::after.

= 7.4.0.8 (April 24th, 2025) =

# Enhancements
* AI can detect pseudo elements ::before and ::after.

= 7.4.0.7 (April 23rd, 2025) =

# Enhancements
* Better AI support for responsive styling.

= 7.4.0.6 (April 22nd, 2025) =

# Enhancements
* AI assistant now available in the main release.
* More room for chat / sketchpad with new chat icon at top right.

= 7.4.0.4 beta (April 18th, 2025) =

# Enhancements
- Improvements to the reliability and simplicity of CSS selectors the AI assistant generates.

# Bugs fixed
- Saving settings could get stuck on very fast servers due to a timing bug.

= 7.4.0.3 beta (April 10th, 2025) =

# Change
- Regular auto-save system applies to AI edits too, with easy undo.

# Enhancements
* Significantly more capable AI model.
* AI model can probe the web page more effectively.
* AI model can utilize Microthemer stock animations.
* Instant undo / redo buttons added to the top right of the interface.
* Undo icon next to each AI reply for easily jumping back one or more steps.
* AI conversation and code sketchpad persist across page refresh and can be retrieved from history.

= 7.4.0.2 beta (Dec 11th, 2024) =

# Enhancements
* The AI can help debug styles not working due to CSS rule conflicts.
* "New Task" button added below the chat to clear the history and start a new task.
* Auto-scroll to the top of the AI's message.

= 7.4.0.1 beta (Dec 5th, 2024) =

# Enhancements
* Improved the AI assistant's awareness of previous messages in the conversation.

= 7.4.0.0 beta (Dec 3rd, 2024) =

# Enhancements
* New AI assistant panel can help with styling and debugging.
* Media library insert popup now has a size menu next to the "Insert Image" button.

= 7.3.2.8 (Feb 26th, 2024) =

# Bugs fixed
* The color picker value was getting lost if manually typing a color value name, hex, or rgb.
* When using variable colors, the top part of the color input was white instead of the variable color.
* Reordering a draft selector before saving it triggered an error.

= 7.3.2.7 (Jan 17th, 2024) =

# Bugs fixed
* The previous update caused an error with "or" conditions in the folder logic, causing folders to not load.

= 7.3.2.6 (Jan 14th, 2024) =

# Bugs fixed
* Logical folder conditions could return the wrong result if the word "and" was in the page title text used for human reference.
* Fixed an issue with a legacy JSON decoder which could cause issues saving settings.
* Microthemer could create multiple folders for the same page if the page title changed.
* Selecting a different folder from the top toolbar during targeting was overwritten if the "Auto folder" checkbox was enabled.

= 7.3.2.6 (Jan 13th, 2024) =

# Bugs fixed
* Logical folder conditions could return the wrong result if the word "and" was in the page title text used for human reference.
* Fixed an issue with a legacy JSON decoder which could cause issues saving settings.

= 7.3.2.5 (Jan 9th, 2024) =

# Bugs fixed
* When point and click editing of the admin interface was enabled, a JS error could be triggered when saving a Post or Page.
* An error loading Microthemer folders could occur if making a typo and setting a number as a CSS property e.g. 3: red;

= 7.3.2.4 (Dec 9th, 2024) =

# Bugs fixed
* The order CSS styles are loaded on the page could be different when editing with Microthemer compared to the regular frontend. This meant selectors could have an effect in Microthemer but not the frontend.

# Enhancement
* Microthemer displays a "Drag here" box on empty folders to help drag selectors between folders.
* The font-size for the code editor can be customised via the preferences.

= 7.3.2.3 (Nov 25th, 2024) =

# Bugs fixed
* The preference option "Support admin area point and click editing" did not work on block editor admin pages.
* Fixed an issue with folders names having a _2 suffix even when the name didn't clash with an existing folder.
* A text translations warning could flash up briefly when loading the Microthemer interface.
* More Gutenberg integration fixes for WordPress 6.7.

= 7.3.2.2 (Nov 19th, 2024) =

# Bugs fixed
* Rolled back some previous code that was changed in the last update, as it caused styles to not load under certain circumstances.
* Gutenberg integration issues with WordPress 6.7. There may be more fixes to follow here.

= 7.3.2.0 (Nov 19th, 2024) =

# Bugs fixed
* Rolled back some previous code that was changed in the last update, as it caused styles to not load under certain circumstances.

= 7.3.1.9 (Nov 18th, 2024) =

# Bugs fixed
* The page navigation menu could occasionally do nothing when selecting a new page to visit.
* Compatibility issue with the legacy site Customizer whereby Customizer options were overly spaced apart.
* Fixed issue with MT targeting turning off when switching to Gutenberg block editor (even when "Support admin area style loading" is enabled).
* Element selection was still happening in the block editor even with "Support admin area style loading" disabled.
* Styles for the homepage did not always render in the Full Site Editor, if the home page was being displayed as a fallback screen.

= 7.3.1.8 (Oct 15th, 2024) =

# Bugs fixed
* Compatibility issue with swiper.js in Woo Essential plugin that made the mousewheel scroll very slow.

= 7.3.1.7 (Sept 9th, 2024) =

# Bugs fixed
* Compatibility issue with WowStore plugin, which changes the classes on all blocks when saving. Microthemer now ignores these "temporary" classes when generating CSS selectors.

= 7.3.1.6 (July 30th, 2024) =

# Bugs fixed
* SVG path elements with children could throw off Microthemer's HTML inspection pane DOM indexing, making it difficult to select elements via the HTML pane.
* Possible PHP error: "Uncaught TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given" in Common.php:382.

= 7.3.1.5 (July 24th, 2024) =

# Enhancement
* Microthemer adds an empty selector ".wp-block {}" at the top of a stylesheet to ensure that Microthemer files can be loaded in the Gutenberg editor iframe. It's a quirk of the block editor that certain selectors must be present for them to be allowable. However, this extra style rule is not necessary for users not making use of the recent Gutenberg integration, and so will not be added if you turn off the "Support admin area style loading" preference via Settings > General > Preferences > WORDPRESS ADMIN.

= 7.3.1.4 (July 17th, 2024) =

# Bugs fixed
* Issues with the Gutenberg integration and the latest version of WordPress (6.6).

= 7.3.1.3 (July 16th, 2024) =

# Enhancement
* Auto-save is now configurable via Settings > General > Auto-save. It is still enabled by default.

# Bugs fixed
* CSS grid highlighting could be incorrect when using subgrid with multiple levels of nesting if different gap values were defined on subgrids.

= 7.3.1.2 (June 18th, 2024) =

# Enhancement
* "Create new" Post/Page option has been added to the "Search site" menu.

# Bugs fixed
* The Google Fonts browser, Manage design packs, and in-program CSS reference didn't work in Firefox.
* When customizing a Brizy preview page with Microthemer, which uses a special URL that is only valid for a short time, this could generate a "403 forbidden" warning when returning to Microthemer at a later date. To fix this, Microthemer no longer tries to load the last viewed page if it has a "preview_nonce" URL parameter.
* Issues with "Auto-folder" assignment when styling a new Gutenberg Post/Page before it has been saved or published.

= 7.3.1.1 (June 18th, 2024) =

# Change
* Global CSS does not load on block editor pages if the blocks are not embedded inside an iframe. Otherwise, the CSS can bleed into the top level WordPress toolbars and panels. Global CSS will still load in the Full Site Editor (FSE) however, which always uses an iframe.

# Bugs fixed
* Microthemer's global stylesheet could render in the footer if a value for "Stylesheet loading order" was set in the Preferences.
* Another issue "Stylesheet loading order" being set was that conditional folders always loaded when using the MT interface (when they should have been disabled on certain pages). This is because JavaScript variables were being set before the CSS asset loading had been determined.
* Microthemer could generate invalid folder logic when styling certain pages inside the Full Site Editor. This resulted in the style appearing for a split second and then disappearing.

= 7.3.1.0 (June 17th, 2024) =

# Bugs fixed
* Global CSS was loading on Edit Post / Page admin screens even if the "Support admin area style loading" preference was set to "No".

= 7.3.0.9 (June 17th, 2024) =

# Bugs fixed
* Possible PHP error: "mt_rand() expects parameter 2 to be integer, float given".
* In some places, the preferences text was too long to display neatly on laptop size screens.

# Enhancement
* Grid gaps are highlighted more explicitly, when CSS grid highlighting is enabled.

= 7.3.0.8 (June 11th, 2024) =

# Bugs fixed
* Possible PHP notice: "Undefined" in Logic.php on line 366.

= 7.3.0.7 (June 9th, 2024) =

# Bugs fixed
* On rare occasions, random data storage keys for responsive styles could be converted to "Infinity", which made it impossible to add responsive styling.

= 7.3.0.6 (June 8th, 2024) =

# Bugs fixed
* The subgrid setting for grid-template-columns/rows could be lost in the previous update.
* Grid items were not properly constrained by ancestor grid tracks when using subgrid.
* Switching selectors to one that has the single grid item view could display the wrong grid fields.
* Providing row/column line names reduced the maximum number of tracks to less than 24 in the grid controls.
* Padding was not properly adjusted for when highlighting grid items.

# Enhancement
* A purple dashed line shows implicit grid lines and "subgrid" (if relevant) in the grid control area.

= 7.3.0.5 beta (May 22nd, 2024) =

# Change
* Gutenberg block editor classes are whitelisted now, rather than admin only classes being blacklisted. This should greatly reduce the chance of styling working in the editor but not on the frontend.

# Enhancement
* CSS grid subgrid property value added to grid-template-columns and grid-template-rows.
* Gutenberg integration extended to KadenceBlocks.

# Bugs Fixed
* Miscellaneous issues with Gutenberg integration when the blocks were not loaded in an iframe.
* Unique classes were not added to all Gutenberg blocks e.g. blockquotes.
* Microthemer element overlay highlighting did not scroll with the page under certain circumstances.
* Option to view the block editor outside of Microthemer added to Exit options.

= 7.3.0.4 beta (May 13th, 2024) =

# Enhancement
* Microthemer's responsive controls now sync with Generate Blocks' responsive controls.

= 7.3.0.3 beta (May 8th, 2024) =

# Bugs Fixed
* The Gutenberg integration did work if the block editor was embedded directly into the page, rather than as an iframe. Direct embedding is a legacy method that is implemented when blocks using the old API are present: https://make.wordpress.org/core/2023/07/18/miscellaneous-editor-changes-in-wordpress-6-3/.

= 7.3.0.2 beta (May 3rd, 2024) =

# Enhancement
* The element breadcrumbs reflect the class or id used in the current selector.

# Bugs Fixed
* Possible internal server error when importing CSS from a stylesheet into Microthemer.

= 7.3.0.1 beta (April 23rd, 2024) =

# Bugs Fixed
* Microthemer did not live update CSS style loading when the page template was changed in the editor.
* When first clicking on the page content in the Site Editor, the body element was selected in the process.
* Unique classes added to blocks unable to accept them.
* Editor only classes could be suggested when selecting blocks.

= 7.3.0.0 beta (March 25th, 2024) =

# Change
* Sync browser tabs is enabled by default on new Microthemer installations.
* Admin asset loading is enabled by default on new Microthemer installations.
* Global styles also load in the block editor (if admin asset loading is enabled).
* When Microthemer creates new page specific folders, they also load in the block editor (if admin asset loading is enabled).

# Enhancement
* Deep integration with Gutenberg and the Full Site Editor (FSE). Add content with Gutenberg and style it with Microthemer at the same time, from a single browser tab.
* Consistent styling between the block editor and the site frontend.
* Apply responsive styling to Gutenberg blocks. Microthemer tabs sync with the mobile and tablet preview options in the block editor.
* When selecting block editor elements with Microthemer, the custom class input field is automatically scrolled into view. This makes it easier to add custom or utility classes provided by frameworks like Tailwind, CoreFramework, or ACSS.
* When loading the Gutenberg editor inside Microthemer, unique classes in the format "mctr-e5i34p" will be added to elements you select (and ancestor elements) to help target blocks precisely and in a way that is consistent between the frontend and block editor. To ensure the HTML markup stays clean, these classes are automatically removed if you do not target them with Microthemer. But if you do reference these classes, Microthemer will auto-save the Gutenberg content to ensure they don't get lost if you forget to save manually.
* There is a related option in MT's preferences to add unique classes to ALL Gutenberg blocks - even when editing outside Microthemer. It's disabled by default, but you may wish to enable this if you use Microthemer's full code editor with targeting disabled. Or, you prefer styling rendered Gutenberg blocks on the frontend but want to take advantage of block-specific CSS classes (akin to what page builders output).
* When styling block theme templates, template parts, patterns, or navigation using the Full Site Editor MT will generate folder logic to ensure that the styles display wherever the content displays. For example, to ensure that MT's CSS styling for a reusable pricing table pattern is loaded whenever that block is added to a post or page, it will generate folder logic that looks something like this: \Microthemer\has_template("wp_pattern", 4654, "Pattern - Pricing"). This will even work if the pricing table is part of another pattern that is added to the page.
* To ensure Microthemer can check for template/part/pattern/navigation usage reliably and quickly, it maintains a small cache file that can be efficiently checked on the frontend without having to parse blocks on the fly. This means Microthemer can keep CSS asset loading to an absolute minimum without incurring expensive overheads.
* The "\Microthemer\user_has_role()" logic function for folder loading now accepts a user id as the first parameter, as an alternative to specifying a role name.

# Bugs Fixed
* "editor.session is not defined" JavaScript error that could sometimes display when first loading Microthemer.
* CSS styling conflict with WP To Buffer Pro plugin where Microthemer select menus had a light background even if in dark theme mode.
* CSS grid gap properties were not output using shorthand even if both row and column values were provided.

# For full changelogs visit: https://themeover.com/microthemer-changelog-7-x/