WP Admin Speed

well; if you have a page caching plugin that is disabled for logged in users and/or if there’s significantly more/ different CSS/ JS on your logged on pages, then yes it could be slower. so yes, but it depends ??

frank

Is there a way to disable AO for logged in Users?

yep, with a couple of lines of code hooking into AO’s API, cfr. the info on “pagebuilders” in the FAQ.

Where do I put it? A file? Custom CSS?

add_filter(‘autoptimize_filter_noptimize’,’pagebuilder_noptimize’,10,0);
function pagebuilder_noptimize() {
if (is_user_logged_in()) {
return true;
} else {
return false;
}
}

you can use the code snippets plugin to add it.

I don’t mind adding it – just wondering to which PHP I add it?

if you don’t want to use code snippets, you could add it to your (child) theme’s functions.php (but one little mistake there can break your site + you loose your changes when you update your theme).

Okay – so it has to go into functions.php, not an AO file? The thing is – since my Theme (Avada)updated – it is clear that this issue is affecting performance when I am logged in. I currently have the plugin disabled and speed is great.

indeed not in an AO-file. functions.php (with the disadvantages I wrote about) or with e.g. the code snippets plugin ??

If adding this code is that problematic, I will likely just discontinuing using the plugin. It might be worth considering that considering the high level of adoption of Avada as a theme, this might be something to implement in a future update.

adding any code to functions.php is potentially problematic @fionavar. a lot of people do it, but I don’t want you to do something which actually is not “best practice”, hence the proposal to use “code snippets” which does not have those problems.

regarding catering for avada (or any other popular theme/ plugin); testing and using all plugins/ themes (esp. when commercial such as Avada) is something I simply can’t do and I don’t see a good reason for that either; AO is very flexible, with plenty of config options and even more filters which code can hook into, so almost any (and I’m being careful, I could just as well write “all”) problem can be fixed or worked around. that’s the power (but also the drawback) of using AO.

now to spill the beans; the next version of AO will probably have an option to disable AO for logged in users. but don’t tell anyone ??

have a nice weekend!
frank

Hi Frank – I promise not to tell! I know you have mentioned not wanting support/donations, but I suspect there are many of us who would happily do so. I look forward to re-activating AO ??

well, if you insist; https://github.com/futtta/autoptimize/commit/1ea4c6e742586241b378d1bdf903a03e2c2841e9

you can download the dev-version of AO from https://github.com/futtta/autoptimize/archive/master.zip, open the zip and overwrite wp-content/plugins/autoptimize with the contents of autoptimize-master in the zipfile ??

this will be in the next version of autoptimize (no idea when I’ll release yet).

frank