jimesten

Same error here .. on 3.5.1 multisite

I have finally resolved this one .. if anyone is in similar situation, please contact me. Part of the problem appears to have been in the order of instuctions in the WP multisite .htaccess file and which lines had the [L} directive

Basically, the working format is:

RewriteCond %{HTTP_HOST} ^domain.com [OR]
RewriteCond %{HTTP_HOST} ^www.domain.com
RewriteRule page.html$ https://domain.com/programs/newpage/ [R=301,NC,L]
RewriteRule pg2.html$ https://domain.com/programs/newp2/ [R=301,NC,L]

I did note elsewhere that someone had found they need to repeat the RewriteCond statement before each rule, but I have now got the first 6 domains done using only the pair of conditions for www vs non www and then just the rules (about a dozen per domain) for each page where I needed to do the redirection.

Does anyone actually have this working under the following scenario:

1. Old standalone sites migrated to a multisite network
2. Old sites have pages with same name so need to distinguish between domains on the new networked sites
3. New page names are different from old page names..
4. I have roughtly a dozen of these for each domain .. so already need hundreds…

Example:
Old pages:
https://domain.com/page.html
https://anotherdomain.com/page.html

New networked pages:

https://domain.com/category/newpagename
https://anotherdomains.com/category/newpagename

I have tried matching http host with a rewrite condition to no avail. The only way I’ve been successful is a vanilla:

Redirect 301 oldpage.html https://domain.com/category/newpage

… but that doesn’t cut it because the old pages have the same name on all the old sites. I’ve tried several redirect plugins as well.

I’ve love to the see the .htaccess file of a fully working site that has the same scenario!!

thanks,

Jim

Even better!! I had already started down that path.. thanks for shortening it!

peace,

Jim

Excellent. Thanks for quick reply!!

Jim

Ditto … when can we expect an update to this … we use almost 150 plugins across out 1500+ sites .. only 2 have had issues with WP 3.5 and the other one was updated overnight last night.

thanks,

Jim

Anyone? I can’t be the only one looking for this sort of functionality..

thanks,

Jim

We found the culprit .. someone fessed up to having changed a permalink setting. We had already verified theme by swapping to default and the plugin set was same as functioning sites.

So.. now we add checking permalink to the troubleshooting checklist!!

thanks,

Jim

We imported a site on which all the pages had relative paths. These showed up as broken images even though the image was definitely in that path. Any new image inserted via the editor was inserted with the FQDN in the link — with the path portion containing the exact same information as the relative path only version.

Same behavior in text widgets .. I don’t understand what is unclear at all about the original question. There are two ways to construct a link to an image .. with a relative path (preferred for portability) or using the fully qualified domain name and the path. Path only was fine on the site when it was part of a simple multisite installation, but the same content would not display images on a multisite with the Networks for WordPress plugin enabled unless the FQDN was added to the link.

thanks,

Jim

Are people actually using this thing? Given the complexity of what this plugin is capable of, this forum area seems frightfully quiet.

On topic .. are we really not able to use relative paths (very applicable to text widgets in particular!) when using this plugin? Putting a fully qualified domain name in the link for every image radically reduces the portability of a site and in my experience is typically seen as poor practice. I’ve been in shops that explicitly called this out in best practices documentation so I hope this can be addressed.

thanks,

Jim

Themes working now .. sort of .. will open new thread with better description.

Disregard last .. I logged out and back in and they showed up. Odd behavior, but working now.

I wiped it all out and started over and all is working.

Yes, I know that .. what I’m saying is that when I go to the new network’s dashboard, the option to add sites isn’t there.

thanks,

Jim

Again…

2. Larger problem though … (I do have DOMIAN_CURRENT_SITE commented out in wp-config) .. I don’t have an option to create new sites on my new network.

Anyone out there?

thanks,

Jim