nicollb

I’m seeing the same thing on my multi-site network: main site works as expected; subdirectory site (I have only one set up so far) only uses the CDN for the theme files.

Is this something I have configured incorrectly?

my offsite address is specialstuffxxx.cloudfront.com/en for the subdirectory site
—-

Nevermind. Mine is working. I had forgotten to add files to the list of directories; after adding that, I cleared/deleted the cache and now it works.

I don’t know if it actually works, but there is a parameter for the shortcode title=”” —
so, in theory you would use the shortcode this way:
[woothemes_features title=”My New Title”] and that should do it.

I did just that — I consulted with Woo and we came up with the same result: I will use JetPack for custom css, instead of the feature in the theme… because Multisite just won’t allow me to use the Woo functionality without being a SuperAdmin… It is a pain to have to set up JetPack for every site, but at least it will do what I need.

One reason for posting the question here was to try to determine if this is specific to the Woo themes/Woo framework, or is it a WP Multisite issue. Indeed, it seems that it might be a combination: I’m not sure how JetPack Custom CSS make CSS mods without incurring the gatekeeping for unfiltered_html whereas the woo theme options have a problem; but, since I have a solution I’ll not waste any more time on it.

And believe me, I use Woo support. You wouldn’t be undercutting them at all.

thanks — I began to think about it, and thought that it might not be a bad plan, if one uses a custom image for the featured image — then you might want it left out of the slideshow.

So — if it is “fixed” – great. If not, maybe you need to make note of how it works.

Duh! (Dope slap to self) — thanks. Not sure how I missed it.
…

And it seems to have resolved the problem.

How would I get 1.5b1?

The issue: WP 3.4, multisite: 5 sites in the network, using the same theme (a customized child of WooThemes Headlines, framework at the latest version): we are unable to add or change tags, or see what tags are in use in the admin screens when the plugin is activated. Other sites on the network are fine; a site where this theme is activated after the upgrade to 3.4, works fine.

so, I’m thinking there is some sort of caching issue. Not on my installation, because I had to turn off my caching plugin for other reasons.

I’ve about given up on this… I even tried working around it using mod rewrite (in my .htaccess) to no avail. I have it happening on 2 separate multi-site subdirectory installs. These are on 2 different hosting services.

It would be nice to know if anyone actually can use page 2 and beyond in a search from the admin search bar in this case.

You might try the stuff at this site:

https://insites.ingenesis.net/2008/08/17/wordpress-bbpress-mediawiki/

or this one where they took it a step further:

https://ciarang.com/wiki/page/WPMW

I’ve been looking at this as well. I found this: https://insites.ingenesis.net/2008/08/17/wordpress-bbpress-mediawiki/

It seems to work with a single wordpress install. I haven’t tried it with a multi-site.

I’m still looking for something a bit more seamless — this uses the same users, but you still have to log in to each piece. Maybe there is something that would share a cookie so it would act like a true single login.

I did check and the paths are correct ( like /en/ or /es/, etc) — I also found in the codex that bloginfo(‘url’) strips the final /

I have a multisite that is subdomains, and these problems do not exist in that network, so I think it has something to do with the subdirectory variation.

I can work around this in search boxes inside my themes by adding the slash. I can’t see how to get that to work in the admin-bar search box.

I have discovered that <?php bloginfo(‘url’); ?> always returns the url for the sites without the trailing / — even tho siteurl in the wp_options tables all include the trailing slash.

I’m thinking that might be related.

I thought I had this fixed, or maybe I just selectively ignored it. But I continue to have issues on all sites in this network. I have a new quirk: I have a sitewide tags blog set up (not really used, but there); I selected TwentyTen as the theme, and the search seems to work from within the theme. But, the admin-bar still returns bad URL’s for page 2 and beyond.
example: https://famvin.org/anniversary-en?s=paris (which gets a page)
and “previous”:
https://famvin.org/anniversary-en/anniversary-en/page/2/?s=paris (which of course returns the a 404);

I’m guessing it has to do with the Rewrite Rules, but they are pretty standard:

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

# END WordPress

If I modify the search URL to add a slash after the sitename (subdirectory) then all is well.

WP Multi-site (subdirectory) 3.2.1
WP SuperCache (could this be a problem?)

I’ll take a swing at it — obviously TwentyEleven uses more or different hooks than TwentyTen did (TwentyTen works fine).

I’ll post back if I find it.

OK — after further testing and deliberations, this appears to be theme related, but the theme that is causing it is not Headlines, Coffeebreak, or other non-woothemes themes I have tried. The error only occurs when the tags blog is using Twenty-Eleven and the subdomains use a wootheme. Interesting. I changed the tags blog theme to 2010 and now all works well.

Not sure how or where to report this.

I have checked using another site in the network, and it is the theme… or rather, I suspect it is the Woo Framework which is at the core of the theme for most of the sites on the network.

I’ll push it from that angle.