WordPress 3 subdomain installation

  • Will WP3.0 work installed in a subdomain (https://wordpress.mydomain.com) or must it be installed in a primary domain (https://www.otherdomain.com), for the multi-site features to work?

    I have an existing website in (Apache) public_html/, a WP2.97 blog in public_html/blog, an add-on domain (https://www.addondomain.com) in public_html/addon.

    I want mydomain.com and addondomain.com to have a blog (either blog1.mydomain.com and blog2.addondomain.com, or mydomain.com/blog1 and addondomain.com/blog2).

    I have wildcard DNS configured for my main domain, WP3 installed in a subdomain (wordpress.mydomain.com) and Donncha’s “WordPress MU Domain Mapping” plugin installed.

    The “Create a Network of WordPress Sites” page says to add lines to wp-config.php file in /home/username/public_html/wordpress/, and update .htaccess file in /home/username/public_html/wordpress/, and I have done that.

    The Add Site page asks for _____.wordpress.mydomain.com

    No error messages, seems like it should work, and yet when I create a site, it doesn’t display. When I create a blog “chess”, and browse to https://wordpress.mydomain.com/chess/, it displays my main blog (https://wordpress.mydomain.com/) and https://chess.wordpress.mydomain.com gives “Oops! Firefox could not find chess.wordpress.mydomain.com”.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter lernerconsulting

    (@lernerconsult)

    On my host (LunarPages, and I’ve seen the same on other hosts), all subdomains are created in public_html.

    So, https://www.glerner.com is in public_html/glerner, movies.glerner.com would be in public_html/movies, etc.

    I have installed WordPress 3.0 (RC3) in public_html/wordpress, as https://wordpress.glerner.com

    No error messages setting up WordPress, configuring Networks, or adding a site.

    When I try to Update my network, I get errors like this:

    * https://opera.wordpress.glerner.com

    Warning! Problem updating https://opera.wordpress.glerner.com. Your server may not be able to connect to sites running on it. Error message: Couldn’t resolve host ‘opera.wordpress.glerner.com’

    Is there a way around this? Or must WordPress 3 be installed in public_html, with a new domain name to access it?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    You’re trying to use subdomains on a subdomain install of WP, which is creating SUB subdomains.

    I don’t think you can do this.

    It’s more because it’s an add-on domain of the main domain. Your WEBHOST is the one who is controlling where the wildcard subdomain record is in Apache.

    Use subfolders, or make the install the primary of the account.

    Thread Starter lernerconsulting

    (@lernerconsult)

    To put it in most basic terms:

    Move lernerconsult.com from public_html to an add-on domain, located in public_html/lernerconsulting

    Then move the WordPress files from wordpress.lernerconsult.com (public_html/wordpress) to public_html, and point a new domain name (e.g. lernerconsulting.info) to there.

    I also had to go into phpMyAdmin to replace all the occurrences of wordpress.lernerconsult.com with lernerconsulting.info (I had done enough configuring plug-ins to make it worth while, instead of re-installing).

    Now multi-site is working (after the DNS changes had propagated through the Internet).

    Grrr, there are a lot of people who have their hosting account set up with mydomain.com in public_html. Do all these people have to move their web site to an add-on domain, to have WP3 multi-site work?

    I am making a WordPress 3.0 post on exactly what I did, on https://lcblog.lernerconsult.com/

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    there are a lot of people who have their hosting account set up with mydomain.com in public_html. Do all these people have to move their web site to an add-on domain, to have WP3 multi-site work?

    Only if you’re moving from wordpress.com hosting to your own. Which … well I know jack about how that works. I know that I have www.ads-software.com’s install on my server in public_html, no ad on anything needed for multisite.

    Grrr, there are a lot of people who have their hosting account set up with mydomain.com in public_html. Do all these people have to move their web site to an add-on domain, to have WP3 multi-site work?

    No, but some of them have to do the reverse. running a network is mocu more technically involved, and if you know ahead of time you want to use it, it’s easier to plan your server setup.

    Thread Starter lernerconsulting

    (@lernerconsult)

    @ipstenu: I don’t understand. Yes, I am talking about installing WordPress 3 on my web hosting account. Are you saying you install both a web site and WordPress, both in public_html? I’d have to at least make my web site not have an index.php, since WordPress uses that.

    Usually I’d want to keep major applications in their own folder, easier to update, less confusion “Is this file part of my web site, or of one of these big applications?”.

    Certainly less work than moving a big existing web site out of public_html, though…

    Thread Starter lernerconsulting

    (@lernerconsult)

    @andrea_r Maybe WordPress will make instructions for web hosting companies?

    None of the techs at my web hosting provider had done anything with WPMU, even though it’s a good hosting company. A few couldn’t understand that the new version might possibly need different setup…

    • How to configure WordPress 3 for customers
    • Advantages of starting new accounts with web sites not in public_html
    • How to move web sites out of public_html, so public_html is for WordPress multi-site.
Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘WordPress 3 subdomain installation’ is closed to new replies.