sub domain redirecting to wp-signup.php

I dont know how to access the httpd.config

you won’t have to. ??

redirecting to the signup page is what it does if it can’t find an exisiting blog. Yes, the www and the non are considered 2 sites. So, stop it redirecting.

Put
define( 'NOBLOGREDIRECT', '' );
in wp-config.php

Cheers Andrea, worked like a treat. Your a life saver, now I can go to bed ??

Andrea, thanks for the tip. However, in my case when I add that line, going to example.com instead now just returns a blank page (no source at all). I’ve even tried using the Redirection plugin to redirect example.com to https://www.example.com but it seems to ignore that directive.

I’m stumped. Any ideas?

Thanks!

Hmm. Well, I looked at another thread which recommended I change define( 'SUBDOMAIN_INSTALL', true ); to define( 'SUBDOMAIN_INSTALL', false );

When I do that, it fixes the problem (with a warning on the home page to drop the define('VHOST', 'yes'); definition from wp-config due to deprecation, so I commented that out).

But doesn’t this mean now that I can’t use subdomains for additional blogs on my Multi-Site setup? I’d really like to use subdomains, but I still want to avoid the problem defined at the beginning of this thread.

It may mean your server isn’t set up to handle subdomain wildcards and redirects correctly. WHich would be a time to talk to your web host.

Thanks, Ipstenu, I’ll look into that as well.

(with a warning on the home page to drop the define(‘VHOST’, ‘yes’); definition from wp-config due to deprecation, so I commented that out).

Ten you have an upgraded wordpress MU install, yes?

Because on a 3.0 and up install, this line is not used. which is why it;s deprecated – it was only in mu.

Yes, come to think of it, this would be an upgraded WPMU install. It’s been a long time in development, as you can tell, but it’s now at 3.1.1.

Good to know – cuz if you start mixing up the old wpmu defines and the new multisite defines… it gets hairy.

Is there a way that I can refresh my wp-config to act more like a straight-up 3.1.1 install, rather than an evolution from WPMU? For example, do I just back up, then delete wp-config.php and let a new one generate as I go through the install wizard, and then add any customizations necessary after that?

No.

Because you’ll get a message that an existing network is detected.

The config defines aren’t the only differences. WPMU has _1_ on each of the main site’s tables and places the uploads on blogs.dir/1/.

Back to the original issue – when you put the noblogredirect (which should have worked in mu as well) and get a blank page…. that;s the sign of a php error. Did you read the error logs?

I’m afraid what you’re trying to do may make things worse and have nothing to do with the actual error you were experiencing.

Thanks for this post, i had the same issue and this worked for me and all my subdomains are working like a charm!

change define( ‘SUBDOMAIN_INSTALL’, true ); to define( ‘SUBDOMAIN_INSTALL’, false );

Back to this. So, I will need to backup and then wipe out my DB, then reinstall WordPress (upgrading to 3.2.1 now) and re-import content (not the whole original DB) to get it to be a pure WP 3.2.1 install?

To get a ‘pure’ install, yes.

I am using Multi Sites on a UNIX (Plesk) box & had the same problem of redirecting to wp-signup.php. I am using domain mapping and sub domains ( not sub dirs). I wanted all domains to use wildcards… you just never know when someone erroneously types 2 or w’s… right? so I added this code to my wp-config.php… I hope this helps someone.

list($we_tld,$we_dom) = array_reverse(split(“\.”, $_SERVER[“HTTP_HOST”] ));
$we_url_to_reolcate_to = ‘https://www.’ . $we_dom . ‘.’ . $we_tld;
define(‘NOBLOGREDIRECT’,$we_url_to_reolcate_to);

I also had to configure Apache for wildcards to get this to work properly.