Changelog do OMGF Pro

Correção

• After a theme (or plugin) stylesheet changed without WordPress' updater, e.g. when deploying with Git, SFTP or from a staging site, OMGF Pro kept serving its outdated cached copy. Cached copies are now refreshed when their source file is newer.
• After updating a theme or plugin, local and external stylesheets OMGF Pro had cached (e.g. because they import Google Fonts) were served unprocessed until OMGF's cache was emptied, because OMGF removes their cached copies on update. They're processed again now.
• Magic Fallbacks didn't add its fallbacks to fonts declared as CSS custom properties, e.g. block themes' font presets (Site Editor › Styles › Typography or theme.json).
• Magic Fallbacks (or a Fallback Font Stack) could add its fallbacks to the font-family of an @font-face statement in the same stylesheet, instead of to the declaration using it (e.g. font-family: Manrope), which broke that @font-face statement.
• Refreshing a page's Smart Optimize results (Admin Bar) also removed the Smart Optimize stylesheets it shared with other pages with the same unused fonts, so those pages loaded without their fonts while served from a page cache.
• Apply Font-Display Option Globally (and Magic Fallbacks) also rewrote text on the page mentioning font-display (or font-family), e.g. "font-display: swap" in a post, removing everything after it up to the next; or }. Inline styles are now processed inside style elements and style attributes only.

Correção

• Smart Optimize decided whether a visitor was on mobile by the window's width when storing results, but by user agent when applying them. So tablets wider than 768px and narrow desktop windows analyzed pages on every visit, tablets could get the results meant for phones, and a narrow desktop window could store a page's desktop results as mobile. Results are now stored by user agent too, like most page caches separate mobile and desktop.
• Smart Optimize no longer analyzes WooCommerce's endpoints, e.g. order received pages (/checkout/order-received/ /) or My Account's orders, and doesn't apply the results of the page they belong to (e.g. the checkout form) to them, because their contents are different.
• Smart Optimize no longer analyzes pages which shouldn't be page cached, i.e. pages defining the DONOTCACHEPAGE constant (e.g. WooCommerce's cart, checkout and account pages), and doesn't apply results to them.
• Local stylesheets loaded through a URL containing ../ (e.g. Super Speedy Search's stylesheet) couldn't be cached, because their cache path contained ../ as well.
• When the license server couldn't be reached, requesting OMGF Pro's plugin information caused a fatal error ("Attempt to assign property "plugin" on false"), e.g. in Plugin Report or during Wordfence's update check.
• License keys which can't be decrypted (e.g. after migrating a site) no longer cause a PHP warning on every page load, and license keys are no longer written to the license manager's debug log.
• Magic Fallbacks had no effect unless Smart Optimize, a Detection Setting or a manual Fallback Font Stack was enabled too, and inline styles didn't get its fallbacks unless a manual Fallback Font Stack was configured. Stylesheets processed before Magic Fallbacks was enabled (or disabled) are now processed again.
• Pages served from a page cache for longer than 12 to 24 hours couldn't be analyzed by Smart Optimize, because their (expired) nonce made WordPress reject the request. Logged-out visitors no longer get a nonce, because it's the same for everyone and doesn't protect anything. Requires OMGF v6.3.13 for the Google Fonts Checker's request.
• Unused fonts were still removed after disabling Smart Optimize (only its preloads stopped). Its results are now only applied while it's enabled, and kept for when it's enabled again.
• With plain permalinks, all pages shared the same Smart Optimize results, so fonts used on one page could be removed from another. Pages are now identified by their query vars, e.g. /?p=123 (search terms aren't stored).
• The license manager's Manage License tab on OMGF's settings screen is now translated. License manager v2.2.8.

Correção

• Smart Optimize stored its results for every URL visitors browsed to, so variations of the same page were analyzed and stored separately, e.g. AffiliateWP's referral URLs (/ref/ /), which may contain an affiliate's email address. Results are now stored for the canonical path of the page. Existing results are removed once, so pages are analyzed again.
• Smart Optimize results weren't found on sites installed in a subdirectory, or for paths containing percent-encoded characters.
• Smart Optimize no longer analyzes 404 pages for administrators either.

Correção

• Magic Fallbacks kept asking to contact support about fonts which never existed, e.g. 'Arial,Helvetica,sans-serif !important', 'var(--tve-font-family,Mulish)' and 'inherit'. Whenever the Google Fonts API returned no fonts for a font family found in a local or inline stylesheet, which is always the case for a font installed with WordPress' Font Library, OMGF Pro < v5.2.9 ran the optimization again with the entire document, instead of that font's @font-face statements. Every font-family…

Correção

• Optimize Local/External Stylesheets skipped any link element written over multiple lines (or with a line break inside its href attribute), while browsers load those just fine. The pattern used to find them couldn't match line breaks, but could run past the > which ends an element. Both are fixed, and line breaks are now stripped from the URL before it's requested, just like browsers do.
• @import statements spread over multiple lines weren't detected. CSS allows whitespace (incl. line breaks) after @import and inside url, and a backslash followed by a line break is a line continuation inside a string, but none of those were matched. A raw line break inside the URL is still ignored, because that's an unterminated string, which browsers don't load either.
• Smart Optimize (Unused Fonts) could return a blank page when an inline @import statement was fully unloaded. The pattern used to remove that statement removed everything between the first @import and the last occurrence of the stylesheet's URL, and exceeded PCRE's runtime limits on documents larger than ~100KB, in which case the entire document was replaced with nothing (accompanied by a 'preg_replace_callback: Passing null to parameter #3 ($subject)' deprecation notice). Matching is now…
• Smart Optimize (Unused Fonts) didn't remove any @font-face rules from stylesheets whose fonts are split into subsets. The subset was matched against the font file's URL using a pattern which couldn't match the hyphen separating the subset from the font-weight (e.g., source-sans-pro-normal-latin-400.woff2), so no rule ever matched. The subset is now matched against the @font-face rule's unicode-range, and only falls back to the filename for rules which don't define one.
• Smart Optimize (Unused Fonts) now removes a stylesheet's link element from the HTML entirely when all of its @font-face rules are unloaded, instead of leaving behind a request for an empty stylesheet. Generated stylesheets always start with a header comment, which meant they were never detected as empty. This also fixes the deregistration of fully unloaded Async Stylesheets.
• An unused Material Icons stylesheet wasn't removed from the HTML. Its cached URL was looked up in the wrong list, so it was never recognized, and clearing the link element's href attribute left behind a request for the page itself. Its link element is now removed entirely.

Correção

• With Magic Fallbacks enabled, the first click on a Replace checkbox checked all corresponding "Don't Load" checkboxes, but left the Replace checkbox itself unchecked.
• With Magic Fallbacks enabled, a Replace checkbox stayed disabled after unchecking the Preload checkbox(es) of the corresponding font family.
• A corrupted (non-array) Fallback Font Stack option no longer causes a fatal error ('Cannot access offset of type string on string') when opening the Optimize Fonts settings screen.
• Magic Fallback aliases were incorrectly stored as font families during Save & Optimize, causing a 'could not find a matching fallback font' notice.
• Magic Fallbacks no longer tries to find a fallback for icon fonts (e.g., Material Icons/Symbols) and no longer shows a 'could not find a matching fallback font' notice for them.
• Smart Optimize now purges the page cache on taxonomy archives, the homepage and WooCommerce product pages by switching supported caching plugins (LiteSpeed, W3 Total Cache, WP-Optimize, WP Rocket, WP Super Cache) to URL-based purging, so the detection script no longer re-runs on every page load for URLs without a single post-ID.

Correção

• Muli was renamed to Mooli. This fix provides an alias for it.