WP Asset CleanUp Pro 1.2.5.9 NULLED

1.2.3.3 - 1 July 2023
* "Overview" area: Added notifications about deleted posts, post types, taxonomies and users, making the admin aware that some rules might not be relevant anymore (e.g. the admin uninstalled WooCommerce, but unload rules about "product" post types or a specific product page remained in the database)
* Stopped using the "error" class (e.g. on HTML DIV elements) and renamed it to "wpacu-error" as some plugins/themes sometimes interfere with it (e.g. not showing the error at all, thus confusing the admin)
* Keep the same strict standard for the values within the following HTML attributes: "id", "for" to prevent any errors by avoiding any interferences with other plugins
* Fix: Some rules were not fully exported & imported (e.g. the rules from "termmeta" and "usermeta" tables)
* PHP 8.2.7 compatibility

1.2.3.1 - 2 March 2023
* Improvement: When using plugins such as "Learndash", the post types weren't detected in the permalinks structure when plugin unload rules had to be applied
* Fix / PHP Warning: Undefined array key "script_src_or_inline_and_noscript_inline_tags" in [...]/templates/meta-box-loaded-assets/_assets-hardcoded-list.php / Sometimes, if there are no STYLES OR SCRIPTS to be detected on a specific page (it rarely happens), the list of assets will not be fetched in PHP 8+
* Fix: Plugin unload & load exception rules weren't working on specific environments within "Plugins Manager"

1.2.3.0 - 6 February 2022
* Improvement: Make sure the plugin unload rules by page type are always triggering in any WordPress setup, disregarding the post status (if the page is only for administrators, the rule will take effect)
* WPML Fix: Prevent Asset CleanUp Pro from triggering whenever /?wpml-app=ate-widget is loaded (in some environments, the content returned was empty and the automatic translation area was not loading)
* PHP 8+ Fix / Sometimes when "Manage in the Front-end view" is enabled, the following error shows up when managing assets: Uncaught Error: json_decode(): Argument #1 ($json) must be of type string, array given in [...]/classes/Main.php
* PHP 8+ Fix / The following notice triggers when WP_DEBUG is enabled - Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in [...]/classes/OptimiseAssets/OptimizeCommon.php

1.2.2.9 - 18 December 2022
* Sometimes, when "Preview Changes" is used (e.g. when DIVI theme is enabled) from an edit page area, the preview doesn't trigger because of a JS error from script(.min).js
* Fix: Prevent undefined errors from the newly added "tag_output" object within the hardcoded assets list

1.2.2.8 - 4 December 2022
* Added NOSCRIPT tags (usually added after SCRIPT tags) to the hardcoded list of assets (e.g. if you unload a tracking script on a page, you can also unload its NOSCRIPT tag as well, if any was added)
* Elementor Templates: Hide "Manage CSS & JS" whenever hovering over a template title as managing the assets is meant for public pages (not templates added to pages)
* Fix: Hardcoded assets / When an inline SCRIPT was detected, it was erroneously detected as a SCRIPT with the "src" attribute, if the inline content contained the "src" string (e.g. )
* Fix: If a plugin's option from "options" table had an empty value (e.g. edited manually by a developer for debugging purposes), the plugin was using add_option() to update it instead of update_option() which is the right function to use in this situation

1.2.2.7 - 22 November 2022
* Preload CSS/JS: If a tag (LINK/SCRIPT) is wrapped by Internet Explorer comments, make sure the wrapping is preserved when the asset is preloaded, otherwise, the preloading would occur in all browsers when its meant to be loaded only by Internet Explorer
* CSS/JS manager via "Manage in the front-end view": Make sure to notify the admin about hardcoded assets wrapped by Internet Explorer comments
* Hardcoded assets improvement: Use fewer resources when the unloading is triggered
* Fix: In rare cases when an option value remained empty in the database (e.g. edited directly through phpMyAdmin), add_option() was used instead of update_option()

1.2.2.6 - 17 November 2022
* Improvement: Whenever you mark a hardcoded tag as unloaded, it will stay unloaded (the rule will be kept in place) as long as its content or the relative source value will stay the same (e.g. if you unload will be considered the same as )
* Improvement: Better detection of the tags (including the hardcoded ones) when the source of a tag (e.g. "src" or "href") is not wrapped around quotes or even has spaces added after or before the equal sign / e.g. <script src=/path/to/file.js></script> OR <link rel=stylesheet href = /path/to/file.css>
* New Option: Added the load exception (if any unload rule is applied) based on the post type for hardcoded assets (e.g. 'On all WooCommerce "Product" pages')
* Whenever XML-RPC is completely disabled in 'Settings' -- 'Disable XML-RPC', make sure the following option is automatically turned ON: 'Settings" --- 'HTML Source CleanUp' -- 'Remove "Really Simple Discovery (RSD)" link tag?'
* Fix: 'SweetAlert 2' files were missing when 'SCRIPT_DEBUG' was turned OFF (most cases) which sometimes prevented the modal to show with specific information regarding the plugin rules that were used
* Fix: The size of an asset loaded locally was not shown when the path to the file was relative and starting with the URI of the WordPress site URL / Example: The WordPress site URL was "https://yoursite.com/blog" and the tag was "<script src='/blog/wp-content/path/to/file.js'></script>"
* Fix: "Deprecated: strpos(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in "/wp-content/plugins/wp-asset-clean-up-pro/classes/OptimiseAssets/(OptimizeCss.php and OptimizeJs.php)"
* Fix: Exclude from optimisation JS files that contain "/*@cc_on" and "@*/" as they are meant to be loaded by Internet Explorer and not stripped if they only contain commented code

1.2.2.5 - 6 November 2022
* "CSS/JS Manager": If a handle has inline code associated with it, mention the size (e.g. bytes, KB) of that inlined LINK or SCRIPT (just like it's mentioned for the LINK tags with the "href" attribute and SCRIPT tags with the "src" attribute)
* Higher accuracy in detecting (for optimization) the LINK tags that are loading CSS/JS files
* Improvement: In case a WordPress installation has a subdirectory (e.g. www.mysite.com/blog), make sure any assets that have relative URIs (e.g. /blog/wp-content/style.css) are all optimized properly

Download WP Asset CleanUp Pro v1.2.2.4 NULLED
1.2.2.4 - 30 October 2022
* Improvement: If an asset is an unloaded through the CSS/JS manager and a preload (via LINK tag) was already set through another plugin (e.g. "Pre* Party Resource Hints") or within the theme, for instance in functions.php, make sure to strip the preloading as it's useless if the actual asset is not loaded in the first place
* "Plugins Manager" improvement: Compatibility with "Premmerce Permalink Manager for WooCommerce" plugin (if the URL of the product is changed, make sure the rules based on the "product" post type are still applied)
* If "SCRIPT_DEBUG" is set to "true", load the non-minified versions of the plugin's assets / read more: https://wordpress.org/support/article/debugging-in-wordpress/#script_debug
* Fix: Make sure none of the plugin's assets are included within any combined CSS/JS files (if the options are enabled in "Settings")
* Fix: Make sure to offer fallback to "wp_json_file_decode" in case the WordPress version is below 5.9.0 (as compatibility with older WP versions is promised)