With a few thousand users here, next time please LINK to your previous post please 🙂
http://wordpress.org/support/topic/pagination-problem-10
I did the switch manually.
Which switch?
Also, you probably have to set up wildcard subdomains again. — http://codex.wordpress.org/Create_A_Network#Step_2:_Setting_Wildcard_Subdomains
Sorry, I didn’t link back to it.
The switch I meant was from Host Gator servers to the GoDaddy servers as I explained in my previous post that I didn’t link to.
Just got off the phone with GoDaddy.
They said on a shared server account I cannot have a change made to put in the wildcard subdomain. I would have to switch all the way up to their fully dedicated server in order to be able to change the necessary file. Not sure we can afford that at the moment. (Jump from $15 to $70 a month.)
Is there anyway for me to switch from subdomain to subdirectory? My WordPress site was originally made about two years ago, but the move was just this month with a new install of WordPress followed by replacing the new files and database with the old ones.
Thanks for any advice. (I also got an answer from them on the pagination issues in the above linked post. Going to update it in a minute.)
Sure. In your wp-config file, where the line says subdomains and has a value of true, change to false.
Making that switch won’t have adverse affects on blogs already in place? Will I have to go make a separate folder for each in the subdirectory setup?
OK, this is odd. Since GoDaddy said I can’t add the line of code (ServerAlias *.example.com) to server file httpd.conf I was on my way to delete the wildcard domain I created in the DNS records. Right before clicking delete on it since it was no useless I decided to check something.
I went and created a new blog site and it worked! Then I went and checked all the spam blogs that were created last night that weren’t working and they were working too! So apparently WordPress doesn’t need both portions of this instruction…
1. Apache must be configured to accept wildcards.
1. Open up the httpd.conf file or the include file containing the VHOST entry for your web account.
2. Add this line:
ServerAlias *.example.com
2. In the DNS records on your server, add a wildcard subdomain that points to the main installation. It should look like:
A *.example.com
Am I the only one that this works for? Has anyone else tried it?
I’ve heard of it working for others, so I’m not too shocked they tell you it doesn’t. GoDaddy works best if you don’t need their help 😉
To your other (now unneeded) question:
Making that switch [to subfolders] won’t have adverse affects on blogs already in place? Will I have to go make a separate folder for each in the subdirectory setup?
Remember. The folders are VIRTUAL. Don’t make ’em. EVER. You’ll screw it up 😉
And as for adverse affects … well. If you switch from subsite.domain.com to domain.com/subsite, YES, obviously you’ll have to redirect people. But that’s pretty easy.
Thanks for responding even though it seems I might not need it anymore. I was prepared to make each folder if I had to switch.
Hopefully this post will help someone in the same situation.
Thanks again.
So apparently WordPress doesn’t need both portions of this instruction…
Actually, yes it does need it. 😉
The subtle difference here is the host has it set up like that, and doesn’t want you to know. Or will not support it.
Ahh, well either way. I just hope they don’t decide to change anything.
That would be the risk right there in an unsupported feature. 😉
