johnrork

Sorry, I should have mentioned it is in half-on mode. I suffered from 500 errors in full on mode.

Unfortunately supercache files don’t differentiate between ssl and non ssl urls. The protocol isn’t saved so the files are shown to every user.

Well, actually… that’s good isn’t it? I was trying to figure out if SSL was the reason why users would be fed an outdated cache file when a newer one was available.

Hi, it’s me again.

Well I’ve since launched my site and WP Super cache has been doing a decent job, even in half-on mode.

However, I’m still wondering about how it is handling my multi-network multisite install. It seems to be affecting all my sites on all networks, as they all have the comments appended to the footer, but I’ll frequently hear about updates that are still not being displayed more than 24 hours later (my expiry time is set to 300 seconds).

I can see new cached files being added to the cache directory, but for some reason they are ignored until I manually delete the old ones.

I’m thinking a couple of things could be at play here. First of all my install is made up of 30 networks with over 250 sites. Each network has its own plugin settings. Currently, I have it network activated only on the root blog on the root network, but now I’m wondering if maybe I should have it network activated on every network, or—Matt forbid—every site?

Also, I’m forcing SSL admin sessions, and it seems that Super Cache is caching the site on through both the secure and unsecure channels. Should I force the public site onto standard http with additional .htaccess rules, and will that work on WPSC?

Ultimately, I feel like I don’t really fully understand how WPSC functions well enough to work these things out in my head, and I’d like to tell people more definitively when their content will be viewable. Resources seem to be slim about configuring the plugin for 3.0, and absent completely for my unique circumstances. Can anyone shed some light on what could be going on?

Erf… Andrea I was hoping if anyone would know it would be you!

I’ve cross-posted it here.

Please someone give me some insight, this is very troubling! It happened again just this morning on a site that was working fine yesterday and hasn’t been messed with since!

Anything patently stupid about doing it this way?

<?php

$menus = get_terms( 'nav_menu', array( 'hide_empty' => true ) );

foreach ( $menus as $menu ):

?>
	<ul class="menu-class">
  		<a href="#" class="menu-title"><?php echo $menu->name; ?></a>
		<?php wp_nav_menu(array('menu' => $menu));?>
	</ul>

<?php endforeach; ?>

Sorry, I guess I a follow-up is in order!

switch_to_blog() is indeed alive and well in 3.0.

It did not do exactly what I wanted, as I planned to use menus in widget mode for ease of administration, and you can’t load a widget area via switch_to_blog().

However, loading them via wp_nav_menu() did work, and only cost the ability to easily change menu order. All in all, it was a good compromise.

Thanks for the help!

Can’t there be a way to do this programmatically in the theme? To temporarily step out of the current blog and load a menu as if it were a different blog, then back again?

Something like WPMU’s switch_to_blog() function?

I realize that the menu wouldn’t appear in admin… that’s actually the desired effect: all of the functionality, none of the control 😉

Obviously, this would require sub-sites to use a child theme; that is no problem.

Of course, after posting, the very next package I thought was worth a try is the one that worked.

php5-gd solved it, for the record.