topquarkproductions
Forum Replies Created
-
Forum: Alpha/Beta/RC
In reply to: Network Activating Plugins not working?Would it make sense to remove the “Network” plugins tab altogether for child admins? It seems a little strange to tease with the number of network plugins activated, yet not show them which ones.
Forum: Alpha/Beta/RC
In reply to: Network Activating Plugins not working?Back at ‘er….
Yes for #4, I mean normal per-site plugins. I haven’t even approached MU plugins yet (I guess the meaning behind MU depends on the context it’s being used in).
As for what plugins I’m using, it’s a clean install, just playing around with it. Right now I only have BuddyPress, Sharing is Sexy and Thesis OpenHook installed. I’m pretty sure the Thesis menu option not showing up has to do with the Thesis theme.
Forum: Alpha/Beta/RC
In reply to: Network Activating Plugins not working?I did some poking around. It turns out there’s a line in the print_plugins_table that makes it so network activated plugins are ignored unless it’s the superadmin logged in. Around line 560 of wp-admin/plugins.php is:
if ( $is_active_for_network && !is_super_admin() ) continue;So, I guess it’s by design that network activated plugins don’t show up for admin users on the child sites. I tried going back to the super_admin dashboard and un-network activating the plugins, then just simply activating them. Then they appear in the child site dashboards and the child site admin and activate them as he wishes.
Behaviour was still a little strange though. First off, the above doesn’t work for BuddyPress (you can ONLY Network activate BuddyPress). Second off, when I activated Thesis Openhook on a child site, my Thesis Openhook settings menu option under appearance doesn’t show up. Further, when I made Thesis the active theme on the child site, the Thesis menu option doesn’t show up. Now those may well be problems specific to that plugin/theme. I can look into that.
I guess this is all a case of not completely understanding Network Activation of plugins. It seems that these are the rules (listed here in case someone else finds this thread with the same questions I had):
- Network Activated plugins are available and activated on all child sites. Further:
- They don’t show up in the list of Plugins (though the number of Network Plugins does indeed show up). Perhaps it would be better if a list of Network Plugins showed up, but without the ability to activate/deactivate/edit them.
- The settings pages (if the plugin is properly setup to run in MU) _do_ appear under the settings menu
- Simply Activated plugins in the parent site appear in the list of available plugins on the child sites. The child sites have the ability to activate/deactivate them and change the settings
Sound right to you?
Forum: Alpha/Beta/RC
In reply to: Network Activating Plugins not working?It’s a fresh install of WP3-beta2.
Maybe it’s a beta issue. Good to hear I’m not crazy.
Forum: Alpha/Beta/RC
In reply to: Network Activating Plugins not working?Sorry about that. New to the forum. Didn’t mean to offend. But thanks for the reply.
I tried installing and Network Activating BuddyPress (that’s a MU compatible plugin, right?) and the same behaviour. On the child site, the number of “Network Plugins” (on the Manage Plugins page) increased, but BuddyPress doesn’t show up in the list. I would think that it should….
Forum: Alpha/Beta/RC
In reply to: Network Activating Plugins not working?Bump.
Maybe it’s a dumb question, but if it is, the answer must be simple.
Forum: Plugins
In reply to: Why does calling current_user_can() crash WP 2.9.2?RESOLVED:
If I change the code in the plugin to:
<?php
/*
Plugin Name: Asdf
Plugin URI: http://asdf.com/
Description: Asdf asdf asdf
Version: 1
Author: Top Quark Productions
*/add_action(‘admin_head’, ‘asdf’);
function asdf(){
var_dump(current_user_can(‘edit_post’));
}
?>…then everything works fine.
All fine and dandy, but seems like quite a hole to have a plugin be able to take down the whole shebang.