amandafrench

Actually you’re totally right, Andrea_r — I suspected as much when I posted, but hadn’t yet checked. Mostly I thought it’d be useful for others to learn about the admin screen activation option (there are a couple other plugins that do that too.) I found the cuplrit: it was an orphaned Cimy Users Extra Fields file I had forgotten about in wp-content/mu-plugins after uninstalling Cimy Users Extra Fields from wp-content/plugins.

I’m having this problem too — for me the main trouble is that activate.php is plain blank. When users click on the activation link in their e-mail, they get (for instance) https://thatcamp.org/wp-activate.php?key555blahblahbah. For now I’ve disabled user self-registration in Network Settings (it’s not all that necessary for us anyway) and have also installed a great new plugin called “Unconfirmed,” which allows you to approve users via admin screen using the activation link the system sent them: https://www.ads-software.com/extend/plugins/unconfirmed/

Right now the users will still see nothing when they click their activation link, but with luck I can get that fixed somehow.

YAAAAYYY! Thank you so much — worked like a dream. Can I give you a foot massage or some jelly beans?

I forgot all about this, actually, but I’ve just checked and the issue isn’t there any longer. It’s all correct — says “The template files are located in /themes/thatcamp-twentyten. The stylesheet files are located in /themes/thatcamp-twentyten-1.0.” So we’re good.

Nope, I’m not having any multisite issues specifically with the Akismet plugin. I understand. It’s a feature, not a bug, even though it bugs me. As I say, I’ve figured out a reasonable workaround.

Yep, I mention that on the other thread.

Fair enough. Though I for one don’t have time to do things on a per-site basis, so I wind up never using Network Activate. I’ve been using a multisite plugin called “Exclude plugin” instead to hide some plugins from child site admins, and the rest of the plugins (except the ones that are must-use) I just leave inactive by default.

Not that I want them to be able to turn off Akismet. That’s just for testing purposes. ?? I haven’t been able to get *any* network-activated plugins to show up in administrators’ plugins list.

Ipstenu, my child site admins *can’t* choose to turn off Network Activated plugins, as far as I can tell, because they can’t see them anywhere in their plugins list. See the screenshot in my earlier post if you don’t believe me. Sounds like other people have that problem too, though I don’t know if everyone does. Can I see a screenshot of a plugin that’s “Network Activated” where the plugin *does* show up in a child admin’s Plugins list?

My settings are “User accounts may be registered” and I’ve enabled the Plugins admin menu for child site admins.

cdvrooman, I can help a little with the Akismet, at least. Here’s what you should do:

1) Get an Akismet API key for multiple sites at https://akismet.com/signup/ — unfortunately, this costs money, at least $5 per month depending on your site’s purpose.

2) Make sure Akismet is in the regular “plugins” folder and not in “mu-plugins.”

3) “Network Activate” Akismet and enter your multi-site API key. That’ll turn it on for all child sites as well as for your site.

Basically I’m almost never using mu-plugins at all, even when I want all the child sites to use the plugin.

I can’t tell whether you think it’s a problem or not, adam320! Personally I don’t like it, because I’d like to have the option of letting child site admins see the plugins. My feeling is that if I don’t want them to see the plugins, I’ll put them in the “Must-Use” mu-plugins folder.

I haven’t found it to be the case that “All children sites can see that this is installed via plugins” when using Network Activate. I know that for multisite-specific plugins such as BuddyPress, Network Activate is the *only* option, and in such cases the plugin isn’t visible to child site administrators.

But for other regular plugins, such as Akismet, when I “Network Activate,” the child admins can’t see that plugin anywhere in their Plugin admin menu — all they can see is how many plugins are Network Activated, not which ones they are.

See screenshot: https://www.flickr.com/photos/amandafrench/4977130955/ That’s a child site. The Akismet plugin is the only one activated on the network. The child admin has the (limited) config menu for Akismet, but the plugin isn’t listed either in the “All” or in “Network Activated” lists of plugins. Same has been true for lots of other plugins I’ve tried.

Aha! I found a great site with exactly the syntax I needed to define a constant and use it in the URL — I forgot to mention above that we’re using Multisite.

https://wptheming.com/2010/06/wordpress-directory-paths/

Thanks for this. I’m very close to getting it to work; my only problem is that I’m not too familiar with PHP syntax. I have this array in my child theme’s functions.php:

function my_child_theme_setup() {
           register_default_headers( array(
		'thatcamp-default' => array(
			'url' => '%s/images/headers/thatcamp-default.png',
			'thumbnail_url' => '%s/images/headers/thatcamp-default-thumbnail.png',
			/* translators: header image description */
			'description' => __( 'THATCamp Default', 'twentyten' )
		),
		'thatcamp-purple' => array(
			'url' => '%s/images/headers/thatcamp-purple.png',
			'thumbnail_url' => '%s/images/headers/thatcamp-purple.png',
			/* translators: header image description */
			'description' => __( 'THATCamp Purple', 'twentyten' )
		),

(and so on). I know that I need to replace the placeholder %s, which is currently pointing to the parent theme directory, with either bloginfo('stylesheet_directory') or get_bloginfo('stylesheet_directory') but I’m danged if I can figure out the correct syntax.

I installed this plugin on a 3.0.1 site and couldn’t get it to work; I didn’t see any new widget in Widgets.

Yep, I’m having it, too.