* Improvement: Apply "font-display:" CSS property for Google Fonts when they are loaded via Web Font Loader (source: https://github.com/typekit/webfontloader)
* Plugin's "License" page: When the information is fetched, make sure the AJAX call is never cached to make sure the latest information is always shown
* Higher accuracy in detecting the "type" and "data-alt-type" attribute before determining if an inline SCRIPT tag has to be minified
* Fix: Make sure "WP Super Cache" & "W3 Total Cache" plugins are working fine when caching pages if "Smart Slider 3" plugin is enabled
* Rank Math & other SEO plugins compatibility: Prevent Asset CleanUp Pro from triggering, thus saving extra resources, whenever URIs such as /sitemap_index.xml are loaded to avoid altering the XML structure or generate 404 not found errors
* Plugins Manager: Make sure the user roles from "If the logged-in user has any of these roles:" are translated into the language chosen for the current admin to avoid any confusion (e.g. if the language chosen in the admin's profile is German, then show "Abonnent" instead of "Subscriber")
* CSS/JS Minifier: Prevent calling @is_file() when it's not the case to avoid on specific environments errors such as: "is_file(): open_basedir restriction in effect"
* Preload CSS feature: When a .css file is preloaded (Basic), the "media" attribute is preserved if it's not missing and different than "all"
* "Rank Math SEO" & "Premmerce" plugin compatibility: Prevent Asset CleanUp Pro's "Plugins Manager" rules from triggering when the permalinks are updated
* Fix / The preload and stylesheet LINK tags had the same "id" attribute which shouldn't be like that as the "id" should be unique for each HTML element
* Fix / In rare cases, the following error is printed: 'Fatal error: Uncaught ValueError: DOMDocument::loadHTML(): Argument #1 ($source) must not be empty within the method "cleanerHtmlSource" inside the "OptimizeCommon" class'
* Fix: On some environments, the following error would show up when WP CLI is used: "PHP Fatal error: Uncaught Error: Call to a member function getScriptAttributesToApplyOnCurrentPage() on null"
* Fix: When the CSS/JS is managed in the front-end, the styling for the hardcoded assets was broken when the list was sorted via location
* Fix: Specific HTML code (unique signatures belonging to Asset CleanUp Pro) that was no longer relevant after optimizing the HTML source was not completely removed as it should be (in order to leave a cleaner HTML source code and not confuse the admin)
* Hardcoded assets: When an asset was moved from HEAD to BODY or vice-versa, make sure a notice is placed there in the hardcoded row (when managing the assets) that it had its position changed just like it's done for the enqueued assets
* Improvement: Removed unused PHP code from specific files
* Hardcoded assets: They can be moved from <HEAD> to <BODY> and vice-versa just like the enqueued assets
* Hardcoded assets: Can be preloaded, loaded based on the media query, deferred/asynched just like the enqueued assets (for <SCRIPT> tags with the "src" attribute & <LINK> tags with the "href" attribute)
* Hardcoded assets' sorting: The assets are now sorted based on the option chosen in "Assets List Layout:" (e.g. if you sort them by their size, you can view the hardcoded assets from the largest one to the the smallest)
* Styling Improvement: Anything from "Settings" related to removal of something (e.g. Google Fonts) has a new style of the switcher (the styled checkbox), now showing a dark red background; This looks the same as the one from the CSS/JS manager for "Unload on this page".
* Fix: If the following option is set to "Standard" (from "Settings" -- "Plugin Usage Preferences" -- "Accessibility"), make sure that the rule applies to any form field from the plugin, including the <SELECT> one
* Fix: Error message: Uncaught TypeError: strpos(): Argument #1 ($haystack) must be of type string, array given in [...]/wpacu.php:185 / This triggered whenever the "page" query string was used as an array / e.g. /wp-admin/admin.php?page[]=value
* New Option: "Settings" -- "Plugin Usage Preferences" - "Do not load on specific pages" -- "Prevent specific features from Asset CleanUp Pro from triggering on specific pages"; This allows you to stop triggering specific plugin features on certain pages (e.g. you might want to prevent combining JavaScript files on all /product/ (WooCommerce) pages due to some broken functionality on those specific pages)
* Combined CSS/JS improvements: Whenever a file from a plugin or a theme is updated by the developer/admin, there's no need to clear the cache afterwards, as sometimes, users forget about this; the plugin automatically recognizes the change and a new combined CSS/JS is created and re-cached
* Improvement: Fallback for clearing CSS/JS cache when using the top admin bar link; it will just trigger by reloading the page if, for any reason, Asset CleanUp Pro functions fail to load there (e.g. in rare cases, plugin/theme developers prevent 3rd party assets to load on their admin pages for various reasons); this fallback is triggering on admin pages unrelated Asset CleanUp Pro's plugin pages (e.g. a settings page of a different plugin)
* "Plugins Manager" - A new option was added to both "IN FRONTEND VIEW (your visitors)" and "IN THE DASHBOARD /wp-admin/" (in case it's activated, as it's a special feature) to disregard all rules from taking effect in case there are issues with any plugin rules for debugging purposes (any rules placed there will be kept as they are; this feature will just instruct Asset CleanUp Pro to not take them into consideration)
* Cache Clearing: Whenever the caching is cleared within any plugin page through the available links (from the top admin bar and the top right side of the plugin's area) a notification about the action is shown with a preloader until the cache is cleared (the page doesn't reload as the cache clearing is made in the background)
* If "Input Fields Style:" is set to "Standard" (for people having difficulties accessing the fancy input fields) within "Settings" -- "Plugin Usage Preferences" -- "Accessibility", the setting will also apply to jQuery Chosen drop-downs, turning them into regular HTML drop-downs (with either one or multiple options to choose from)
* "Settings" -- "Plugin Usage Preferences": Re-organised the tab contents from into multiple sub-tabs for easier access and understanding the options
* Added the option to make the browser download the file only if its current media query is matched (in case the "media" attribute is different from "all")
* Improvement: The plugin is optimised to load fewer functions then before (e.g. PHP classes that aren't required on the targeted page) in order to reduce the total front-end optimization time
* "WooCommerce" plugin compatibility: Avoid using extra resources in Asset CleanUp Pro to process specific CSS files (they are loading after the latest WooCommerce plugin release) that are already minified
* Fix: In specific environments that loaded similar code to the one from Asset CleanUp Pro, errors were showing up, thus more uniqueness had to be added to avoid conflicts such as unique PHP namespaces
* "Plugins Manager": Added option to unload or load as an exception plugins if the current logged-in user has a specific role (e.g. administrator, subscriber, editor, shop manager, etc.) / read more: https://assetcleanup.com/docs/?p=1688
* "GiveWP" plugin compatibility: Prevent Asset CleanUp Pro from loading whenever the URI is like /give/donation-form?giveDonationFormInIframe=1 as the page loaded within the iFrame is already optimized and there are users that had problems when Asset CleanUp Pro was triggering its rules there
* "GiveWP" plugin compatibility: Prevent CSS/JS minification as the files are already optimized and there's no point in wasting extra resources
* Dashboard: Whenever the clear caching link is used, after the clearance, a notice is shown to the admin about this and the clearance date and time
* Fix: Make sure 'post__in' is never empty when called within a WP_Query whenever a post search is made within "CSS & JS Manager" -- "Manage CSS/JS"
* Plugin Settings: Replaced text that sometimes caused confusion (e.g. some people didn't notice the small "if" and thought their caching directory is not writable)