Gabe Livan
Forum Replies Created
-
@dogwomble thank you for reporting a potential bug! It might be an isolated case. Can you please update to the latest version of Asset CleanUp? Let me know if the error persists (after you’re done with the update).
@wordpressagentur It seems that this topic was marked as “resolved”, so I assume you’re not having this problem anymore. I will consider this topic closed. Let me know if you will still have the same problem.
@wordpressagentur thank you for reporting a potential bug! I’ve checked the Menu.php file and there’s no reference at all to AssetsPagesManager. How did you perform the update? I’m in fact surprised of it as I’ve installed the Lite version on a few websites and it works fine (after countless tests in the past weeks).
Can you actually download the ZIP file from WordPress.og, unzip it and search for “AssetsPagesManager” in /classes/Menu.php? I’m looking forward to your reply. It would be odd if you will find anything, as I’ve just done that and there’s no such reference.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Need to update your plugin for Elementor@voidofinspiration sorry to hear that! What are the actual errors? Can you copy and paste them here? I need to know as much as possible about this conflict. Is the problem in the Dashboard or in the front-end? Or both?
Forum: Reviews
In reply to: [Asset CleanUp: Page Speed Booster] Ломает сайт и всё платное@satsis – the plugin might have been incompatible with your website for various reasons. The Lite features are useful, and anyone who wants more can upgrade. This plugin has been used for free by many people with success. The fact it just didn’t work for you doesn’t mean that “all the useful features are available only in the Pro version” as you stated (I used Google to translate this as you didn’t write the comment in English.
PS: It would help if you would update the rating to a higher one as I strongly believe that you were in a hurry when you left this review and didn’t asses the plugin correctly.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] HTTP Request Score has not improved ?The feature you mentioned is from the “Plugins Manager” which is an area available for Pro users. This allows you to unload whole plugins (including any DB queries and PHP functions they trigger), not just their CSS/JS files. If you want to unload CSS/JS files from the “Premium Addons for Elementor” plugin, you can do that using the Lite version too by going to the CSS/JS manager, locating the file you want to unload, and applying the rule (e.g., “unload on this page”, “unload on all pages belonging to a specific post type”, etc.).
There’s a chance the CSS might be affected if you unloaded something that shouldn’t be unloaded. Try to load back all the CSS files then unload them again one by one. If you notice a change that shouldn’t happen, then the last file you unloaded, should be kept loaded. Sometimes, you need to go through trial and error in order to apply all the necessary rules on a page in order to make it lighter and get a higher PageSpeed score.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Wrong language on admin interface@ccarter1180 as I haven’t received any reply from you and no one else reported this issue, I’ll mark this topic as “resolved”. Feel free to reply or start a new topic if this issue persists and I will gladly assist you.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] HTTP Request Score has not improved ?@mave27 thanks for the update! I did check quickly your website, and it looks like on the homepage (at least there, consider reviewing other pages too), there’s a large CSS that could be unloaded. It’s “premium-addons“. Try to unload it and then test the homepage properly. In my tests – https://www.foodguide.co.ke/?wpacu_unload_css=premium-addons – it looks like the homepage looks the same as with the CSS loaded.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Wrong language on admin interface@ccarter1180 I’ve tested this myself and the preferred language of the administrator user is respected. Are you sure this is only happening within the Asset CleanUp Pro pages? I have to admit that some of the text is not translatable, meaning that the necessary functions in WordPress to make it like that, weren’t applied on 100% of the text. Can you give me some examples? Some longer texts that aren’t translated and I could check them out for you.
Forum: Plugins
In reply to: [Asset CleanUp: Page Speed Booster] Loaded files not showing in list@giuse thank you for clarifying this! Just a reminder to anyone reading this: If there are no CSS/JS assets to load (external or inline tags), then Asset CleanUp will not show them. Perhaps this should be added to the documentation, as I used to believe it was obvious. I guess it’s not since other people also asked me why specific plugins that have no assets loaded on the front-end are not showing up in the CSS/JS manager list.
@alexg9 I’ve checked, and I’m getting the same errors. As I said in my previous message, you must stop deferring jQuery. Also, when I append /?wpacu_no_load to the URL, it looks like Asset CleanUp is still loading, suggesting the page caching system does not consider query strings.
Only specific query strings such as “utm_source” and other irrelevant ones for the page caching should be ignored.
You are probably viewing the page as a logged-in user and the source code could be different for you. Make sure to properly test it in Incognito too (or through a different browser when you are not logged-in) right after you activate/deactivate Asset CleanUp. You might get the same problems as the loaded page is likely cache one.
@alexg9 It could be an incompatibility between Asset CleanUp and Flyingpress there. I need to check the HTML source code when Asset CleanUp is not loading (e.g., via /?wpacu_no_load) and when it does load and compare the differences.
As that page is private, I can’t do. I want to test it as a visitor as for you different CSS/JS files might load there.
Also, the video you mentioned is not loading, as I’m getting a notification that the transfer expired. It looks like you’ve set the expiration to happen very early or the people behind the platform set this this way.
UPDATE: It looks like GiveWP uses iFrames to load its forms as they must have their reason due to the styling used (they don’t want it messed up, at least that’s what I suspect). So, anyone having problems loading Asset CleanUp and GiveWP on the same page: GiveWP loads its form (in this case) here: https://baastbook.com/give/donation-form?giveDonationFormInIframe=1 – This page is separated from the main page and in both pages only site-wide rules will apply. Using a per-page unload rule on the main page will not reflect on the iFrame one.
To make sure the iFrame URL won’t be altered in any way by Asset CleanUp, go to “Settings” — “Plugin Usage Preferences” — “Do not load the plugin on certain pages” and add to the textarea: giveDonationFormInIframe=1 (if you already have other exclusions there, make sure to keep each one in one line, one below the other). Asset CleanUp will go through each line, and if the values match the one from the URI, it will not load.
@smithdeltabiz I’ve replied to you privately, but I’ll post a reply here so anyone with the same problem will know what they could do about it.
You’re getting that error because you or whoever deals with unloading the assets have unloaded things that should have been kept loaded. That’s why it’s essential whenever you unload something to test the page, especially when you are in the beginning and need clarification on what’s required. The moment I load the page as https://baastbook.com/give-to-baastbook-main-landing/?wpacu_no_js_unload&wpacu_no_css_unload – which prevents any CSS/JS unloading, it will load fine. It will load if I only load it as https://baastbook.com/give-to-baastbook-main-landing/?wpacu_no_js_unload, but the layout is broken.
So, on that page, remove all the unload rules and unload them again once you notice the culprit. It would be best if you didn’t unload things from GiveWP, ideally, unless you are 100% sure they are not needed on that page.
@alexg9, the issue you’re having is not related to Asset CleanUp. If I load the URL like https://www.educaenvivo.com/todos-los-recursos/que-es-ronda-infantil/?wpacu_no_load (which doesn’t trigger Asset CleanUp for debugging purposes), you will notice that the same problem occurs as you have errors in the browser’s console.
The reason behind it is that you have deferred jQuery (most likely, you are using another optimization plugin that has done this, if you check the SCRIPT tag that loads jQuery, you will notice that it has the “defer” attribute).
The problem is that another jQuery-related code is triggering BEFORE jQuery (since it’s deferred), and errors such as the following are showing up: “Uncaught ReferenceError: jQuery is not defined“.
So, do not defer jQuery, unless you are positive that all the jQuery related code loading in a page are also deferred.
I’ve attached a print screen with the errors here: https://ibb.co/cwcSRKw