codeslinger

Oddly, after I logged in as Admin, I got a warning about no theme setup, I set one up, then I could go to the “MySecondSite.com” URL just fine. THe “SecondSite.FirstSite.com” I fixed using a combination of clearing the cache and setting some url properties on the site in the site admin page. Marking resolved. Thanks, Dave

Maybe this helps – I deleted the second site and started over and now if I enter “MySecondSite.com” in my browser I get a blank screen in FireFox and in IE8, the URL changes to “MySecondSite.MyFirstSite.com” and I get an “Oops!!! Page not found”.

But if I enter “MySecondSite.com/wp-login.php” in FireFox or IE8, I am able to login into my second site just fine.

– Dave

I marked the other as resolved since did not know how to close or delete it.

I am using WordPress 3.4, turned on networking, installed ‘WordPress MU Domain Mapping’ version 0.5.4.2 and followed your instructions as best I could since the menus were different, and have my basic or first site working Ok.

When I login as admin, I see “My Sites”/Network Admin with Dashboard, Sites, Users, Visit Network but do not see any Super Admin menu though do see admin is a “Super Admin” from the Users’ tab.

I do not see the “Super Admin” tab with Domain Mappings and domain tabs like in your example, but do see a Settings tab with Settings, Domain Mappings and Domains.

I don’t see any Tools menu for the Network Admin dashboard nor a Tools menu on the Dashboard for a particular site that has a Domains Mapping submenu.

And when I select Settings/Domains in the Network Admin dashboard, I am asked for a site id. I just picked number 2 and managed to add a new domain but what number to use was not intuitive though I saw my first site was #1 hovering on some button.

So I have two sites defined and only my main site (e.g. MyFirstSite.com) works, and it happens to also be my GoDaddy shared hosting site URL.

So I am unclear what I need for the second domain site in terms of a virtual directory at GoDaddy, a real directory in the file system under the root, or as a path in WordPress multisite. I did set mapping to the actual URL of the second site (e.g. MySecondSite.com) but if I do the dashboard or visit that site I get a 404.

Also don’t know if I’m supposed to check “Update siteurl and home as well” (I did check that) or am supposed to have a path of “MySecondSIte” in the site info as well (I do have that), or have a real such folder under the root, which I do have, though nothing was put into it.

Thanks so much, Dave

Marking this thread “resolved” since cannot figure out how to delete. Keeping thread https://www.ads-software.com/support/topic/can-wordpress-mu-domain-mapping-be-made-to-work-with-wordpress-34?replies=3#post-2932297

David,

Any suggestions as to what to put in the hosting subdomains or in the WordPress admin for sites and domains? I’m confused if I need an actual subfolder under my root, or if I need a subdomain.

Not sure why I don’t see your post in this thread either since the email I got implied you responded to the thread and not directly to me.

Thanks, Dave

Thanks esmi. That is what I ended up doing but was hoping I could get the domain alias working. I found everything worked until I setup permalinks but since am a .NET programmer and not a php guy I did not know enough to figure out why and had little time to learn php and no easy way to debug it. The “own directory” solution worked out well though and my root folder is not too cluttered and I can still setup domain alias definitions for other sites.

I created a writeup at https://www.49thlatitude.com/wordpress/wordpress-folder-on-godaddy-wimp listing my experience installing into a separate subfolder on GoDaddy WIMP along with a few caveats as well as another article on setting up permalinks for WordPress on a GoDaddy WIMP site at https://www.49thlatitude.com/wordpress/permalinks-on-godaddy-wimp to hopefully save some folks the time I spent and to not have to switch to Linux which seems the standard suggestion here. And hopefully they won’t run into the GoDaddy permission/scheduling bugs I ran into along with the standard GoDaddy solution of waiting up to 24 hours for something that should take seconds. You wait, complain and then finally they fix it after 24 hours.

I also sporadically got 500 server errors and a couple timeout complaints from WordPress but at least everything is setup and running now reasonably well. I suspect I was put on a server that had not been fully/properly configured.

– Thanks, Dave

I got permalinks working on GoDaddy WIMP with their new grid hosting where they do not have Microsoft URLRewrite installed, thanks to an article by John Sessford. I have posted a reference to John’s article, code and my GoDaddy tailored instructions at my new WP site located at https://www.49thlatitude.com/wordpress/wordpress/permalinks-on-godaddy-wimp which nicely uses the new permalinks ability. – Dave

I got permalinks working on GoDaddy WIMP with their new grid hosting where they do not have Microsoft URLRewrite installed, thanks to an article by John Sessford. I have posted a reference to John’s article, code and my GoDaddy tailored instructions at my new WP site located at https://www.49thlatitude.com/wordpress/wordpress/permalinks-on-godaddy-wimp which nicely uses the new permalinks ability. – Dave

I got permalinks working on GoDaddy WIMP with their new grid hosting where they do not have Microsoft URLRewrite installed, thanks to an article by John Sessford. I have posted a reference to John’s article, code and my GoDaddy tailored instructions at my new WP site located at https://www.49thlatitude.com/wordpress/wordpress/permalinks-on-godaddy-wimp which nicely uses the new permalinks ability. – Dave

I got permalinks working on GoDaddy WIMP with their new grid hosting where they do not have Microsoft URLRewrite installed, thanks to an article by John Sessford. I have posted a reference to John’s article, code and my GoDaddy tailored instructions at my new WP site located at https://www.49thlatitude.com/wordpress/wordpress/permalinks-on-godaddy-wimp which nicely uses the new permalinks ability. – Dave

Now I understand and I got permalinks working on GoDaddy WIMP with their new grid hosting where they do not have Microsoft URLRewrite installed, thanks to an article by John Sessford. I have posted a reference to John’s article, code and my GoDaddy tailored instructions at my new WP site located at https://www.49thlatitude.com/wordpress/wordpress/permalinks-on-godaddy-wimp which nicely uses the new permalinks ability. – Dave

I wish WP forums would add an email alert but at least this is a decent workaround. I’m hoping there is a plugin I can use in my own forum when I get it setup. Have not investigated that yet…

I got permalinks working on GoDaddy WIMP with their new grid hosting where they do not have Microsoft URLRewrite installed, thanks to an article by John Sessford. I have posted a reference to John’s article, code and my GoDaddy tailored instructions at my new WP site located at https://www.49thlatitude.com/wordpress/wordpress/permalinks-on-godaddy-wimp which nicely uses the new permalinks ability. – Dave

I got permalinks working on GoDaddy WIMP with their new grid hosting where they do not have Microsoft URLRewrite installed, thanks to an article by John Sessford. I have posted a reference to John’s article, code and my GoDaddy tailored instructions at my new WP site located at https://www.49thlatitude.com/wordpress/wordpress/permalinks-on-godaddy-wimp which nicely uses the new permalinks ability. – Dave

Changing to Linux is NOT the global solution for getting WordPress to work. There are quite legitimate reasons to want/need to run IIS and .NET on the web server. It would be nice if some attempt was made to help folks in this environment who may be using it not by random choice but by actual need. Web.config is not the same as wp-config.php and servers an entirely different purpose and is what is used to specify config info to allow URL Rewrite under IIS.