ddarby14

Great job! Going to look into the code to see how to randomize the question order. Any thoughts?

@huyz’s solution works, thx!

@huyz – thanks a ton, great plugin fix and great explanation.

I assumed wp-plugin.php was a WP file so I was hesitant until I realized *both* of these file edits are in the actual plugin. Now all is peaceful again.

Thx again

After dropping rule #1, I’m still getting the rule #2 regardless of domain. Now I’m spinning…going to clear my head, clear cache and try again.

Works like a charm and makes perfect sense, thanks. And don’t call me Shirley ??

That takes care of 50-ish standardized redirects.

When I try to then add an additional rewrite for non-conforming pages:

#Domain Specific Redirects
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?domainname\.com [NC]
RewriteRule ^aboutus.html$ https://domainname.com/our-history [R=301]
RewriteRule ^(.*).html$ https://domainname.com/$1 [R=301,L]

a few things happen.

First, rule #2 still works, but now it works regardless of the domain (losing the RewriteCond??) and second, rule #1 does not redirect, just fires up a 404.

Arggg….I’ll keep Googlin, but if you see anything I am missing, I appreciate it.

great stuff thx. mobile now but will try in the next hour. thanks for pointing out the cleanup!

@andrea – Thanks. Tried the full URL like this:

# 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

#Domain Specific Redirects
redirect 301 https://domainname.com/aboutus.html	https://domainname.com/our-history/

but it didn’t work. Loading https://domainname.com/aboutus.html just brought up a 404 page.

@ipstenu – thanks. It is a subfolder multisite install with the Domain Mapping plugin.

Would love to do something dynamic on this whereas
https://domainname.com/(*).html redirected to https://domainname.com/$1/

I’m not sure where to place it in .htaccess so that it a) catches the domain mapping still and b) redirects the page if matched.

Thanks in advance.

I’m in along the same lines. Have an existing client on standalone WP that we have converted to our multisite WP.

In the standalone WP .htaccess, we had:

redirect 301 /local_staff.htm /local/staff/

Obviously we wouldn’t want all domains (using domain mapping) to follow these links.

Also, they have about 50 client pages that have simply dropped the html

redirect 301 /companyname.html /companyname/

Any thoughts on how to accomplish these two needs in multisite? Would LOVE if you know of a plugin in which client (site owners) could manage their own. In the worst event that we have to do it in .htaccess, not sure how to proceed.

Could do RewriteCond/RewriteRule but that would be tedious and I have no idea what performance effect. Could create those pages with some kind of redirect I guess, but that again would pollute the page manager.

Appreciate any thoughts/help.

you are, you;re just unaware of it. ??

Oh how true that usually is! I’m not tech smart, but I make up for my stupidity in determination/stubbornness. (and of course, with great people like you) ??

Yeah, that’s why I think that using a dedicated server is what is making this tick for us. All incoming requests by default are going to this main domain. When we test this weekend on another box with 2 main domains/wp network installs and CNAMEs coming in, I expect it to blow up.

Lesson for me (and maybe others) is small cost for extra box on cloud/extra IPs is great payoff for not managing serveraliases individually.

You rock. ***bows***

Hopefully, this is helping to clarify. Even though we aren’t using the serveralias Andrea, you were a HUGE help in me sorting through this to a working solution. I don’t think I’ve said it yet (sorry) but THANK YOU! ??

I think the parking (or serveralias or whatever the flavor) is the catch for people, at least it was for me, maybe Mark. Not in the terminology or employment, but in terms of added effort/management.

We’re not using serveraliases at all, so therefore the plugin is working as I expected – whereas client can come and go with using our services/pointing their own domains, we never have to think about it.

We’re also not using wildcard host (I believe that is only for the subdomain version and we’re only using subdirectory).

I really would not want a setup in which, say I get 1000 users who add 1000 domains and requires our team to add 1000 serveraliases – oy, that is a nightmare. Our goal is always to create a self-managed system so that we (the host/supplier) are never a hurdle/manager for clients. ??

With the way we have it setup (still guessing it’s because only 1 install per server or IP), our team does nothing at all in the process.

It’s all up to client to a) add CNAME (or A) record and b) add matching entry to Domain Manager.

The other thing too that was blocking us before, in the Domain Mapping area for the blog/subdirectory, when using the CNAME only DNS, we were using “mappedsite.com” as our entry which failed.

If using CNAME only, we had to put “www.mappedsite.com” in our Domain Mapping entry.

If using both CNAME and A record, then we had to add both the www. and non-www. At that point, it’s up to personal preference which one to make the primary/default.

But the plugin works like a dream with that configuration/knowledge.

Andrea – is the domain parking (server side) a necessity only when having a shared IP environment or shared hosting with multiple wordpress installs?

We moved servers and dns hosts during this exchange which made things crazy. All is settled now. Now we have a cloud of servers now each with unique IPs. All I am doing to get the plugin to work now, is what I expected/wanted. No parking/vhosts changes, just add the Domain Mapping entry for the desired blog(subdirectory), then:

1) CNAME record pointing to our wordpress install (we had to include the “www.” here which added to part of our problem before.)

Working Example (**take out the https://, forum here is adding that**):

CNAME    www.    www.wordpressinstall.com

Before we were using this which failed even though our WordPress install/site uses the non-www of https://wordpressinstall.com:

CNAME     www.     wordpressinstall.com

2) Since we’re using GoDaddy now exclusively for our registrar/dns, we’ve also learned that we cannot do a wildcard CNAME with them (with some dns providers you can) to route the https://mappedsite.com the same as https://www.mappedsite.com. If we REALLY want this, we had to send the A record IP to our wordpress install IP.

We are employing this only for our domains as we’ve grown accustomed to site URLS without the www. We will condition our clients to use the www. CNAME only.

Both 1 and 2 worked as standalone solutions after adding a Domain Mapping entry in the WordPress plugin. No server side parking required.

That was what I was expecting, and sounds like Mark too – complete self-management by the enduser.

However, we have not yet tested anything with multiple IPs (or same IP wordpress installs) on a single server yet. We’re hoping to do that this weekend.

Hey Andrea – sorry for the delay, slammed this past week. I had 1 domain working without the alias, one with. I need to isolate my settings/dns, wait for propagation and test. Still thoroughly confused and appreciate your guidance once I report back to you.

Thanks.

ServerName	mybasedomain.com
ServerAlias	*.mybasedomain.com

This is the only vhost config for these 2 domains. Really hoping (my understanding) that I do not have to do ServerAlias for myblogdomain.com manually – but instead users will be able to add their own via the plugin and need nothing from the server side. I’m guessing you’re just checking to trace the flow though. ??

Thanks again for working through this with me. It really has me stumped.