• I’m a relative newbie to WordPress and coding for the internet in general, so please excuse any stupidity right away.

    I set up the Network for my personal homepage last night as I wanted to have the travel photo blog be my main page as well as have a second blog for personal musings. Naturally, everything seemed to go ok, but it doesn’t work.

    First issue: All the permalinks were changed on my photo blog. I had them set for category and post name (for SEO purposes) and now they are all blog/year/month/date and post name. Can that be changed back or will it screw things up? And if it can be done, are there any special steps I need to take?

    Second issue: I created the subdomain via my webhost. It placed the subdomain folder within the root level of my FTP. The second site shows in the SuperAdmin panel and seems to be setup, but I can’t visit the site to create new posts. There is nothing in the subdomain folder except what was placed there by the webhost when it created the subdomain.

    My main site is http://www.chaseclark.com and the secondary blog is at http://www.blog.chaseclark.com.

    Obviously, I’ve missed something important, but have no idea what it is. If anyone has any clue how to rectify either situation, I’d appreciate the help. Thanks.

Viewing 15 replies - 1 through 15 (of 18 total)
  • Second issue: I created the subdomain via my webhost. It placed the subdomain folder within the root level of my FTP. The second site shows in the SuperAdmin panel and seems to be setup, but I can’t visit the site to create new posts. There is nothing in the subdomain folder except what was placed there by the webhost when it created the subdomain.

    The subdomains are virtual. You do not need a folder on the server. All files are served thru the main folder, yes even for the sub-blogs. 🙂

    Thread Starter ChaseC

    (@chasec)

    Ok, that might explain it. The company I use for webhosting has an ability through their control panel to create subdomains and when doing that is creates a folder for the subdomain. Is that the likely cause of the problem? In a way perhaps I’ve got a real subdomain instead of a virtual subdomain?

    Yes, that’s exactly it.

    Thread Starter ChaseC

    (@chasec)

    Thanks. Well, now the question becomes if there is a way to fix it? Can I fix it through the WordPress Admin panels or is there something I need to ask my webhosting company to do for me?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    When you make the subdomain, does it ask you where the folder should be? Like /public_html/subdomain?

    If you’re using cPanel, you should be able to make a subdomain of * and point that right at public_html

    Thread Starter ChaseC

    (@chasec)

    No it does not ipstenu. I go to the web domains panel and click on add subdomain. All it does is ask for the name of the subdomain and then handles everything from there.
    Obviously, I need to bypass the standard way it makes subdomains. Not that it probably helps with anything, but my webhosting company is ix.webhosting.com.

    Is there anyway to make WordPress use the subdomain as created?

    Also, what about the permalinks structure that was changed automatically apparently when creating a Network. Can I return to the old permalinks structure or not?

    Thanks for the help so far. I know that newbies can be annoying. lol

    WordPress doesn’t create subdomains anywhere. It uses *wildcard* subdomains.

    If you have no way to tell the subdomains to go look in the wordpress folder, then you are stuck. Pick subfolders or move to a host with wildcard subdomains.

    This is a function on the server side. not all hosts support it.

    Also, what about the permalinks structure that was changed automatically apparently when creating a Network. Can I return to the old permalinks structure or not?

    This only happens with subFOLDER installs.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    Obviously, I need to bypass the standard way it makes subdomains. Not that it probably helps with anything, but my webhosting company is ix.webhosting.com.

    Yeah, I don’t know how that host sets up subdomains.

    Delete the subdomains you’ve created, they won’t work. Then open a ticket with your host and ask if you can create wildcard subdomains OR if you can point subdomains to the public_html folder. The latter isn’t the best, since you’d have to muck with your subdomaisn every time you make a new one, but as Andrea mentioned, not every host supports wildcard subdomains.

    Thread Starter ChaseC

    (@chasec)

    I’ve deleted my subdomain created by the hosting company. The support rep has told me that wildcard domains are allowed by default. So, I’ll delete the subdomain in WP and then try to create one again and hope for the best. They said subdomains could take 24-72 hours to work right, so only time will tell.

    Thanks for the help. Hopefully this works, otherwise, back to square one again.

    The only subdomain you need to have created in your cpanel is one with a value of *. WordPress takes care of the rest.

    Thread Starter ChaseC

    (@chasec)

    Sorry, duplicate posting.

    Thread Starter ChaseC

    (@chasec)

    Ok, my webhost assured me that wildcard domains were activated on my account.

    I erased the old subdomain in both places, and recreated the one in WordPress, yet it is still not there. I’ve waited enough time that it should be, but no luck.

    1) The blogs.dir folder is created and in the right place, but otherwise empty.

    2) The htaccess file reads:
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]

    # uploaded files
    RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ – [L]
    RewriteRule . index.php [L]
    </IfModule>

    # END WordPress

    3) The wp-config.php file has this added before the ‘That’s all…’
    define(‘WP_DEBUG’, false);
    define(‘WP_ALLOW_MULTISITE’, true);

    define( ‘MULTISITE’, true );
    define( ‘SUBDOMAIN_INSTALL’, true );
    $base = ‘/’;
    define( ‘DOMAIN_CURRENT_SITE’, ‘chaseclark.com’ );
    define( ‘PATH_CURRENT_SITE’, ‘/’ );
    define( ‘SITE_ID_CURRENT_SITE’, 1 );
    define( ‘BLOG_ID_CURRENT_SITE’, 1 );

    Whenever I try and go to the subdomain’s dashboard I get … http://chaseclark.com/wp-content/uploads/2010/08/Screen-shot-2010-08-30-at-10.40.56-AM.png

    Whenever I try and visit the site I get … http://chaseclark.com/wp-content/uploads/2010/08/Screen-shot-2010-08-30-at-10.41.04-AM.png

    At this point, unless someone sees my obvious error in here, I’ll just uninstall the Network completely and manually create a real subdomain and install another copy of WordPress in there and manage the second blog there via http redirects.

    Thanks for any and all help.

    Ok, my webhost assured me that wildcard domains were activated on my account.

    On the server side, yes. Which is why you see a server page.

    Did you add the * to the DNS records?

    Thread Starter ChaseC

    (@chasec)

    It appears to be.

    http://chaseclark.com/wp-content/uploads/2010/08/dns-settings.png

    I’m likely missing something that will seem so silly and stupid once it is discovered. Human error is always the most difficult to trace.

    Is chaseclark.com the main domain on the web account?

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Subdomain and Permalinks Wackiness’ is closed to new replies.