Microthemer Lite – Visual Editor to Customize CSS

Changelog

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/