Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • That’s precisely my set-up, too. (I’d have to check the plugin settings, though). As far as I can tell, http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/ is part of WordPress, even though it’s not part of the standard shipment.

    The external (front-end) links are clean, it’s just the backend that’s affected. I’m worried about users (visitors) and search engines, for the users (sub-site admins) I’m more relaxed.

    Forum: Networking WordPress
    In reply to: Attachments
    Thread Starter Josef

    (@grainger)

    Hi Mika,
    thanks for looking into this.

    Are they in your media dashboard?

    No. I didn’t realize until you asked, but that’s of course where they should be. Any way to “rescan” the media directory? Uploading again will lead to different URLs, which is undesirable but OK if need be.

    They’re aliases, so <a href="http://subdomain.domain.com/path/to/doc.pdf">My PDF!</a>

    I think I’m not understanding the question on that one… If the file’s uploaded to the correct site, it should show the correct domain name.

    I’m afraid not. For the file I’ve uploaded since the installation, the attachment seems to point to an endless loop of redirects. Let me take it slow. The media library currently contains one file. The link to that file is: http://brillianteams.digitaler-heimwerker.de/?attachment_id=12946 (contains the undesired subdomain.domain.tld format). Clicking that link seems to lead to an infinite redirect loop between brillianteams.com and brillianteams.digitaler-heimwerker.de

    For the rest, I’m missing where I can find the link.

    forgotten attachment types

    Seriously? There is no way in the backend? No way to do that per site? That’s hard to believe, seeing all the perfectionism that has gone into WordPress over the years (I’m with WordPress since at least 2009).

    Anyways, thanks SO MUCH for your effort!

    Did you use subdomain or subdirectory install?
    If subdomain: Did you adjust your nameserver entries?

    Sorry… as far as I can tell, the domain mapping is done by the plug-ins, so without knowing more about the set-up in general and the plug-in in particular, I’m not sure if there’s help.

    As far as I can tell, what happens is that WordPress is primarily using the subdomains internally. When you open the admin menu, it goes to subdomain.domain.com and gets redirected from there, so subdomain.domain.com needs to work.

    Unless you haven’t entered a wildcard subdomain (“*.domain.com”) in your DNS, there is no difference in the outcome. There is also no difference between subdomain.domain.com/wp-admin and subdomain.com/wp-admin. What *exactly* is it that you’d like to achieve, and what *exactly+ is the present behaviour?

    If it’s just the cosmetics of the navigation: I don’t care, it’s just the backend. It’s neither user-relevant nor search-engine relevant. There are many more important places that need to consistently use the mapped sites before I’d start worrying about the admin menu.

    If you get a browser error when navigating to subdomain.domain.com/wp-admin, you need to enable the wildcard subdomain (or every subdomain individually). It will still use the subdomain style, but you won’t notice it anymore 🙂

    Otherwise, I’m missing the point.

    Thread Starter Josef

    (@grainger)

    I got a solution that’s good enough for the moment:
    Dean’s Permalinks Migration Plug-In.
    http://www.deanlee.cn/wordpress/permalinks-migration-plugin/

    At least, everybody following an “old” link will end up on the “real” destination.

    But how does it do it??? It doesn’t add redirects to .htaccess, so the work is done in WordPress code. But if WordPress does this job, then why not the other, more basic one???

    Josef

    Thread Starter Josef

    (@grainger)

    … still strugglin’.

    Here is a snippet from the logfile, two consecutive lines (minus the first three fields) from my experiments:

    [13/May/2010:12:07:35 -0400] "GET /2010/05/pink-on-motivation/ HTTP/1.0" 404 11490 "http://www.dietl.org/" "Opera/9.80 (Windows NT 6.1; U; de) Presto/2.5.24 Version/10.53"
    [13/May/2010:12:07:40 -0400] "GET /2010/05/lostfound-quote-whats-going-on-in-the-project-ward-cunningham/ HTTP/1.0" 404 11490 "http://www.dietl.org/" "Opera/9.80 (Windows NT 6.1; U; de) Presto/2.5.24 Version/10.53"

    Any ideas?

    Josef

    Thread Starter Josef

    (@grainger)

    Update: Pathinfo Permalinks work, e.g. with a permalink structure
    /index.php/archives/%post_id%

    But I’d like to have “Pretty” Permalinks back 🙁

    Thread Starter Josef

    (@grainger)

    (switching back to the default settings for the time being – time to go to sleep here in good old Germany)

    Thread Starter Josef

    (@grainger)

    Hi samboll,

    Again thanks for the suggestion. It’s now

    Options +FollowSymLinks
    
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    … and still doesn’t work. I have the suspicion that I’m missing the obvious, but what? 🙁

    Best

    Thread Starter Josef

    (@grainger)

    Thanks for the suggestion! Unfortunately, no luck.

    This is the .htaccess for the moment:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    Options +FollowSymLinks
    # END WordPress

    I’ve chosen the standard “numeric” structure for now, and you may see that it hasn’t helped so far…

    Best,

    Josef

    Thread Starter Josef

    (@grainger)

    Hi samboll,

    thanks for looking into this – yes, the default set-up is the work-around until I’ve found a real solution. Otherwise, nobody can reach any of the posts 🙁

    What would help? An appointment to demonstrate the issue? Logfile snippets?

    BTW, it’s apache at work.

    Best,

    Josef

    Thread Starter Josef

    (@grainger)

    Sorry for not making the actual issue clearer.

    The issue is: “nice” Permalinks don’t work in the sense that following a link to a nice permalink ends on the 404 page.

    I just discovered the situation, and I’m not aware what could have triggered this behavior, nor have my activities over the past few days (see above) fixed the problem.

    Thanks and best regards,

    Josef

Viewing 13 replies - 1 through 13 (of 13 total)