Sorry I didn’t really understand your point. Network wide activation isn’t supported in W3TC.
I noticed that in some places you say Network activation isn’t supported, but also here you intimate that SiteWide (same thing) is a good alternative to mu-plugins, which doesn’t take subfolders: http://wordpress.org/support/topic/305264?replies=12#post-1206659
When you install W3TC on a 3.0 MU site, it does work as network wide activation, and it caches all the sites (main blog and my sub blogs) just fine. I was thinking the plugin could do a check ‘if network’ or such and move the admin menu up to the Super Admin section.
The plugin does check, but before WP 3, which is not still not fully tested (nor released for that matter), reliability in previous releases was poor. So for now I maintain that it is not supported.
Okay π So it’s not supported. I’m fine with ‘use at your own risk’ and okay living on the edge. I’m not asking for support, per sey.
This remains a suggestion that, when you DO make it supported for 3.0, you have the admin menu up in Network settings.
That’s all π
Your request is still unreasonable however because I cannot assume that all of the settings should be applied to all blogs.
Okay then. Thank you for listening.
Of course. I have added import/export of settings to use “templates” if you will. But unless all blogs are identical in terms of theme and usage, there’s no solution unless you’re only using a subset of features.
What’s the correct setup for WPMU/Buddypress installs?
I attempted to install w3tc and activate it separately on each blog, but it ran into file collisions and claimed ‘access denied’ on some blogs, but not on others. Then I ran it as a sitewide, and it seemed to function, but you say it’s not supported.
Can you contact me through my web site so I can look at your specific cases?
I’ll write it up with details this weekend π
Following up – It all works now with the current version. So there is happiness π