I have the same problem. If I deactivate the the MU Domain Mapping plugin, then the internal page links work. If I activate the Domain Mapping plugin, I get 404 errors.
Is this a bug?
I need the internal pages also to work using the same domain name as my sub-site is mapped to.
They will – it’s not just a main page thing. URL, please.
This plugin works almost exactly like the feature they have at wordpress.com, when you upgrade to domain mapping there.
In my case look at stoer.de/sportsignale
The link to stoer.de/sportsignale/page/2 leads to a 404 error.
Oliver
So basically you didn’t map a full domain name, you’re mapping SUBdomains.
That 404 you’re getting is your web server’s 404 page.
It’s not an issue with the plugin – I think it’s because you;re mixed subfolder and subdomains and the htaccess is for subfolders.
Now I am confused. I thought the point of the plugin was, to make things like that possible.
What is the difference between mapping a full domain name and mapping a subdomain?
What I have, is a multi-site installation of the subdirectory variant. stoer.de being my domain and also the main blog. I have subdirectories like stoer.de/sportsignale.
I wanted to use the domain mapping plugin to map subdomains like sportsignale.stoer.de to this subdirectory blog. If this is not possible, what is the point of the domain mapping plugin?
Thanks for your help.
The point of it originally is to map fully qualified top level domains.
Go to wordpress.com and get a blog. Now look in the backend under Domain Mapping. See? This plugins does the same thing (minus the payment part).
While you *can* map subdomains (in theory) the htaccess rules are now interfering, so if you’re planning on using all subdomains on the blog, either switch out the htaccess rules, or find a host to give you the wildcard subdomains.
Thanks for the explanation. Unfortunately mapping a tld didn’t work for me either.
That’s why I had the idea to at least map the subdomains. Interestingly the setup I use, is described in the german wordpress faq as a workable setup.
Thanks for the hint.
I checked my setup, and I did everything as described in the document.
In my case it seems to be a problem somewhere between the domain registrar (domaindiscount24) and the webhost (1und1). Even if I simply try to point the domain to my webspace, I get a 404 error.
Seems I have to talk to them. Do you have any experience with this combination?
