Gabe Livan
Forum Replies Created
-
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Custom Post Type Posts@bonumaster “we wanted to use the CSS/JS Manager for ALL THE POSTS in the VIDEOS” – how do you want to use the CSS/JS manager? Do you prefer to unload specific assets on all the “videos” post types? Or to add a load exception for a site-wide unload rule?
Correct me if I’m wrong, but I believe you need to do a bulk unload / or bulk load as an exception as it’s explained here: https://www.assetcleanup.com/docs/?p=1214
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Cache _recent_items file deletion@marketeeringroup The fact that the “/cache/asset-cleanup/_storage/_recent_items” directory has so many files suggests that the handles of the CSS/JS items as well as the content is changing dynamically (e.g. it’s not a static file like most of them are within plugins/themes). However, Asset CleanUp has been optimised to work well in these types of situations too, making me think that your website and perhaps similar ones are having a characteristic that is making “recent_items” directory to grow this way.
Yes, you can delete all items from that directory. After you do that, clear any page caching (e.g. if you are using a plugin such as WP Rocket or your hosting company has a page caching service) and everything should be fine. Note that “recent_items” will start having files again and if nothing changed recently (e.g. no plugin deleted, no changes on the number of CSS/JS files loaded), then the same pattern will likely occur: it will have lots of files, at least, it won’t be straight away.
Consider writing to me here: https://www.gabelivan.com/contact/ – I could check your website. I might find the reason behind this issue by just analysing all the assets that are loaded there. Something is just different there.
@webbycraig are you still having this problem? If the plugin is deactivated, you can re-enable it in “Test Mode” (from “Settings”, plugin’s menu) and I could by-pass it via /?wpacu_skip_test_mode and do some debugging.
@khanhnguyen2810 it’s likely that you have unloaded a file that is needed on the homepage, instead of one that is not needed. It would be useful if you can check this post for a way to determine (as close to 100% accuracy as possible) if a CSS file is needed on a page: https://www.assetcleanup.com/docs/how-to-check-if-gutenberg-blocks-css-file-is-needed-or-not/
The original page should restore without any problems whenever you reset everything in “Tools” from the plugin’s menu. Note that the original CSS/JS files from plugins/themes or external locations (e.g. a CDN) are never altered or removed by Asset CleanUp. The plugin just unloads them depending on the rules on that particular page. You do not have to reset everything to restore the original page. Just load the file back (remove the unload rule that you placed in the first place), clear your browser’s cache and any page caching (e.g. if you’re using a plugin such as WP Rocket or you have a page caching service from your hosting company), and everything should be 100% as it used to be.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Not working with php 8.1@webfabrik the following error is completely unrelated to Asset CleanUp, and you need a developer to have it fixed (or you can edit the file yourself if you feel confident about it):
fatal error: Uncaught Error: Undefined constant “php” in /home/xxx/www/wp-content/themes/xxx/footer.php
A verification has to be added to make sure the constant does exist (e.g. it might be a different issue that the code was written in such as way that it shouldn’t have been a constant there, but it just ended up to be one by mistake).
PHP 8+ has become pickier when it comes to old / non-functioning code and as a result, if you are having a fatal error, then the execution of the script will be halted and Asset CleanUp (and other plugins) will not process their functions anymore and you end up with the fetching error you ended up with such as: “Status Code Error: 500“.
So, make sure there are no PHP fatal errors (ideally, any errors) there and re-test the CSS/JS manager. It should fetch the assets successfully and print them.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] WooCommere category, cart and checkout?@gerdski you can cleanup the “cart” and “checkout” pages as they are WordPress “pages”. They are associated through their ID (database one) to WooCommerce. There’s no option to apply the rules for all “children” pages as well.
As for the product category, this is the type of WordPress page that is available to manage (the CSS/JS within it) via the Pro version of Asset CleanUp.
PS: I have to remind you that you have to be very careful when you unload CSS/JS and plugins (Pro version) from the Checkout and Cart pages. By default, these pages are excluded from any optimisation (best for the functionality of the website as plenty of beginners were mistakenly unloading the wrong things there and broke the functionality of those pages) through the following plugin option: “Settings” — “Plugin Usage Preferences” — “Do not load the plugin on certain pages”.
@sinclone This is a normal behaviour because the URL is not SEO friendly and not cached by many page caching plugins OR page caching tools used by hosting companies. Moreover, Asset CleanUp caches the combined CSS/JS based on the URI (part of the URL) that is SEO friendly. If that won’t happen, it will have to be combined on the fly on every page load and it’s not desirable.
One solution would be to make exceptions for certain pages / plugins that are having non-SEO friendly URL structures like in this instance.
Can you share with us some examples of pages from your website that are often accessed? I could inspect them and at some point, hopefully, implement a way to make exception for these page formats and have the CSS/JS combine triggering.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Unloading in oxygen builder not working@carlosvai I’ve just checked with the latest version of Oxygen – 4.4 – and things are working well. How do you actually know that rules aren’t taking effect? I’ve tried a few of your RegExes and they are working well. Even #ct_builder=true# which is a simplified version of the RegEx is working fine.
You can append /?wpacu_debug or &wpacu_debug (since the Oxygen edit page already has parameters set) to view at the bottom of the page all the plugins that were unloaded. This way, you can be 100% sure if the rule has taken effect or not. Let me know how testing is going!
@nextronic I’m frankly surprised. You might have a plugin or a tool that blocks your request whenever “wpassetcleanup_load” is used as a query string. What kind of security tools are you using? Perhaps Wordfence that was configured in a certain way? Also, what PHP version are you using? Can you share with us some information about the hosting package you are using?
@nextronic indeed, the white screen of death is showing up like there’s a PHP error there in the background. Can you install and setup the “Error Log Monitor” plugin and after you do that, trigger the same URL again to get the white page? If there’s an error there, it might be reported by “Error Log Monitor” and show up in the widgets area (Dashboard).
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Remove LIVE MODE Console Message@featuremonkey you can remove the message from the console (note that it shows only for you, the logged-in administrator) by using the following snippet (e.g. in your functions.php from the Child theme or a custom plugin where you usually put your WordPress hooks):
add_filter(‘wpacu_show_admin_console_notice’, ‘__return_false’);
PS: Be careful if you copy and paste the snippet into your editor as the single quotes might be pasted differently in your editor. Just make sure there are single quotes there that are added to the PHP file.
@nextronic there are various ways to debug this. We can start with checking the actual output of the targeted page. If you load the URL for which you want to load the assets list and append /?wpassetcleanup_load=1 is there a note at the bottom of that page that contains “BEGIN WPACU PLUGIN JSON”? Are you comfortable sharing with us the URL to your website?
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] PHP 8+ – admin ajax 500 error@drewibt many thanks for letting me know about it. I have to admit that this suggests no SCRIPTS of any kind are loaded on the pages for which you are trying to load the assets list (correct me if I’m wrong). This would happen very rarely and indeed, array_unique() is applied incorrectly in this instance.
I’ve updated the development version that shouldn’t have this problem. The bug will be added to the next tag release. Meanwhile, can you download the development version and let me know how it works. Here’s how to do it: https://www.assetcleanup.com/docs/how-to-get-the-development-version-of-asset-cleanup/
@missionxmission right after the tag release, there were a few updates that were missed and quickly added to the tag. What happened was that some people updated to the latest version right between that short interval and they ended up with this warning from Wordfence.
The update is related to notices (deprecated ones) that are harmless in a live website, but just annoying on certain environments when WP_DEBUG is turned ON and they print on the pages. The Wordfence alert shouldn’t worry you and yes, they were part of an official update, not a hack.
My apologies for this inconvenience! The plugin should work in exactly the same way for everyone having a live website.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] PHP Warning: strpos()@spsrohan can you please install the development version and let me know if you’re still getting the error? You have all the details here: https://www.assetcleanup.com/docs/how-to-get-the-development-version-of-asset-cleanup/