Asset CleanUp Pro Performance WordPress Plugin 1.2.6.7

* Optimize JS: If a JS file is loading based on the media query set (e.g. only on mobile view), make sure that any associated inline JS that is printed "after" the main JS file, is triggered only after the main JS file is loading (if the media query matches), and never immediatelly to avoid JS "undefined" errors in the console and even broken functionality
* Optimize JS: When the WordPress core file "wp-i18n" is unloaded, the SCRIPT tag is replaced with another tag (much ligther) keeping "setLocaleData" and other functions active to avoid JS errors being shown in the console (ideal for websites with just one language)
* Optimize JS: When a JS asset is unloaded and the option 'Ignore dependency rule and keep the "children" loaded' is used, make sure the inline JS associated with the asset is also cleared to avoid any JS errors in the console or even broken page functionality
* Improvement: Detect an attribute found in a tag without using RegEx (for faster PHP processing)
* Fix: When using the "Direct" assets retrieval method, any unloaded plugins for the homepage, would not show up as unloaded in the CSS/JS manager, confusing the admin that the rules might not be applied
* Fix: Avoid errors such as the following (in case plugin functions are called too early by external code): 'Asset CleanUp's object cache is not valid (from method "WpAssetCleanUp\ObjectCache::wpacu_cache_get").'

* New Feature For The Admin: "Settings" -- "Plugin Usage Preferences" -- "Announcements" / The admin would be notified within the Dashboard (if he/she prefers) of critical updates, new features, usage tips, special offers / read more: A Guide to Plugin Announcements: Stay Updated and In Control - Asset CleanUp Pro: Documentation
* Make sure plugin generated STYLE/SCRIPT inline tags (e.g. from features such as "Inline CSS/JS") have the "type" attribute (unless the theme supports HTML5) / read more: Why the type Attribute Is Added to <style> and <script> Tags - Asset CleanUp Pro: Documentation
* New Option in "Settings" -- "Plugin Usage Preferences" - "Plugins Manager" - "IN FRONTEND VIEW (your visitors)": "Additional Query Strings to Ignore for Homepage Detection" (new option to add extra query strings to be ignored for early homepage detection) / read more: Early Homepage Detection: Optimization and Best Practices - Asset CleanUp Pro: Documentation
* Added "Plugins Manager" tab to "Settings" -- "Plugin Usage Preferences": Configure settings related to the plugins loaded in both the front-end and the /wp-admin/ area; Tthe same settings were already added in the "Plugins Manager" main area; URI: /wp-admin/admin.php?page=wpassetcleanup_plugins_manager
* Moved "CSS/JS Cache" tab into the "CSS/JS Manager" one and grouped options within the 'CSS/JS Manager' (for better readability)
* Fix / Notice: "Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the 'wp-asset-clean-up' domain was triggered too early."

* Improvement: Plugin Updater / When using /?wpacu_force_plugin_updater in the Dashboard (e.g. in the "Plugins" page), the cache related to the latest detected version is cleared (e.g. in case the admin has problems updating the plugin, the query string can be used, before re-trying the plugin update)
* Improvement: "Plugins Manager" - Added the "currency" query string to the list of common strings that are ignored when an early detection is made for the homepage (e.g. www.yoursite.com/?currency=EUR is considered the homepage)
* Fix: "Plugins Manager" - "IN FRONTEND VIEW (your visitors)" / "Enable all the rules below" option / Make sure it always updates on click as there were issues with it in the previous release
* Fix: "Plugins Manager" - Sometimes, while being in the "IN FRONTEND VIEW (your visitors)" tab, errors were showing for the " IN THE DASHBOARD /wp-admin/", thus, confusing the admin