Permissions and locations for new network blog

  • Resolved davidbgonzalez

    (@davidbgonzalez)


    13 years, 11 months ago

    I just updated to 3.0.1 on my site ldspunk.org. Following some of the chatter on the integration of MU functionality into the main www.ads-software.com trunk I thought I might be able to consolidate two of my blogs.

    I followed the directions here.

    And I get the DNS to resolve the subdomain (checked using ‘host’ internally and externally to my network). I verified Apache’s configuration-subdomain resolving. But I’m still getting a 403 error when I try and navigate to journal.ldspunk.org (my new network blog). The root blog still functions.

    Could anyone point me, further, to locations and permissions of network blogs. I don’t do much web development and I’m often baffled by where every piece gets resolved; though I can verify that my dir /wp-content/blogs.dir is rwx for www and admin and rx for all.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Where is the journal subdomain pointing to?

    It sounds like you didn’t point it to public_html, but to the journal location, which is incorrect.

    Thread Starter davidbgonzalez

    (@davidbgonzalez)

    Ipstenu,

    The DNS is pointing to the root domain, a la:

    journal CNAME ldspunk.org.

    Since, ldspunk.org resides at 69.169.164.27, a little more similar approach to the one illustrated in the referenced doc page would be something like an A record:

    *.ldspunk.org. IN A 69.169.164.27

    Either way, they should be handed off to Apache to serve according to the apache alias: ServerAlias *.ldspunk.org or ServerAlias journal.ldspunk.org if I wanted to get picky.

    About the only thing that seems to point anywhere, and I apologize for my lack of understanding with www.ads-software.com, are the rewrite stanzas in the .htaccess (as generated by www.ads-software.com):

    # 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

    And somewhere the php, it would appear, is serving a dir or file that is not chmod’d correctly. But I don’t know which dir or file that would be; seeing as how the root domain ldspunk.org’s blog is resolving and serving without incident.

    Thanks,

    David

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Well that’s because it’s not wordpress that redirects your subdomains, at this point.

    You don’t JUST set this in DNS, though. You have to edit your httpd.conf to know to redirect the subdomain. That’s what I’m asking about when I asked if it was pointing to journal or to public_html.

    You add in a virtual host like this:

    <VirtualHost 111.22.33.55>
    DocumentRoot /www/
    ServerName www.domain.tld
    ServerAlias *.domain.tld
</VirtualHost>

    Thread Starter davidbgonzalez

    (@davidbgonzalez)

    Ipstenu,

    I feel like such a tool. Turns out I had a typo in my ServerAlias stanza!

    Thank you for your response, and sorry to take up your time.

    Happy Holidays!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    No prob ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Permissions and locations for new network blog’ is closed to new replies.