MrPeteH

(NOTE: as a workaround, I have patched the JS into that WP page by hand…)

No need to be defensive, Meitar. I understand about labors of love vs earning… having built a few myself over the years! What you have done is MUCH appreciated. THANK YOU again!

The only differences w/ my solution:
* It is plug-and-play, with every script and style already in place, and just needs to be enabled/disabled. Common elements that cause slowdown are already disabled.
* It is documented w/ respect to which ones accomplish what purpose for the most part.
* It is more complete, including all of the scripts and styles — BTW “vfs-fonts” is missing from the docs list. ?? )

I am just trying to help, not make trouble ??

A gentle suggestion (I’d do it if I had ability to edit but you own the plugin ?? )

a) Add an anchor to “REGISTERED SCRIPT AND STYLESHEET HANDLES”
b) Change that link to point to the anchor.

p

My deepest apologies to everyone! I have not been paying attention to developments as I ought (due to Real Life challenges).

I will squeeze out some time to bring this fully up to date ASAP.

(Sorry for the delayed response! Most people ask questions in our blog…)

Your “start” time includes everything up until the plugins are fully loaded. So that means plugin load time could easily be the culprit.

347ms before plugins start to load is a bit long but perhaps not so bad on your server. It all depends…

However: 762ms for Posts selection is rather a lot. Do you have a ton of posts by any chance? If so, you may need to do some careful optimization, as Chaos Inc suggested ??

To examine this in more detail requires some WP code changes that can’t be done automagically by WP Tuner. For further hints, look at the wptuner page, in the “other notes” area. I’ll try to link: here

I apologize for not responding here! Most people ask for help at my blog ??

Usually this problem indicates a very unusual installation. What the message means is that somehow, even though WP Tuner is “injected” right into your wp-config.php file, something else has loaded up the WP database code even earlier.

That’s supposed to be impossible. But hey… you may have a plugin or hack that does something strange.

Come on over to my blog if you’re still having trouble. I would be happy to diagnose this in detail.

Blessings,
Pete

BTW, current_user_can('level_10') works fine.

tenetcommunity,
I just googled… this is a known issue in an early version of WPAU — WordPress Automatic Upgrade plugin. To fix it:

1. Temporarily disable the WPAU plugin
2. Upgrade all plugins automatically including WPAU
3. Turn WPAU back on. (the upgraded WPAU will not have the conflict.)

If that helps, you can mark this problem resolved.

Blessings,
MrPete

What’s really interesting is the version of WordPress reported: I’ve never heard of version 2.73 ??

tenetcommunity,
Have you resolved this issue? It does not appear to be related to the plugin you were downloading.

FWIW, you can get a bit more diagnostic info on RAM (and CPU) use with my new WP Tuner plugin.

OK, I’ve begun a new thread.

(oh… since you control this thread, would you be willing to mark the topic as “resolved”? It’s over on the right hand side.)

Great! let’s start a new thread for tips. I have an idea or two…

Thanks for reporting this, MentalMagma! Three other users had a problem as well.

I’m embarrassed to admit that all my test systems are (were) PHP5 — I never checked PHP4! That’s now been taken care of.

Please try version 0.9 which has now been uploaded. I think you’ll find your problem solved. If not, please report at my blog (the plugin’s home page.)