I noticed that other people say there are issues with 3.1.1. We’re deploying a network right now. Should we stick with 3.1?
A new install of 3.1.1 is not working with this plugin.
I have a network blog with this plugin working and that blog is at 3.1.1, but the plugin was installed and activated pre-3.1.
– Trey
Thanks for that info. We’ll install 3.1, install the plugin, back up and then update to see if it works for us in 3.1.1 as it does for you.
I appreciate it.
Can anybody give any kind of specific details as to what is not working so the plugin devs can fix it? 🙂
smaller point releases of WP usually have less of a chance of breaking plugins.
After upgrading, my mapped sites don’t allow logging in, instead constantly redirecting (I assume) to the login page in a never ending login loop. If the credentials are already present it does allow me in.
Hi,
In our experience, in 3.1.2, the plugin seems to break a lot of things…actually rendering the entire network unusable. Symptoms:
1) There are no mapped domains yet.
2) The first user maps a domain (let’s call it mappeddomain.com) in the plugin’s settings screen. When the user clicks “Save” there is a 404.
3) From this point on, ANY attempt to visit ANY site on the network attempts to go to the mapped domain, which then throws a 404. Yes, even an attempt to visit mainsite.com then redirects to mappeddomain.com. So no one’s sites can be visited, and no one’s admin area can be logged into.
Fortunately, this is a sandbox site, but we need to go live soon. Any ideas?
Thanks,
Mark
Is the user mapping a domain from their sub site?
Did you follow all the instructions?
Given any site on the network is trying to go to the mapped domain, I’m thinking some server side settings are messed up somewhere. Nothing significant enough between WP 3.1 and 3.1.2 changed enough to affect domain mapping.
>> Is the user mapping a domain from their sub site?
Yes. Well, actually, we are doing it from a sub site as if we are a client/user, since we’re still in testing mode. That’s when the problem starts. As soon as the “user” maps the domain, everything breaks.
>> Did you follow all the instructions?
Yes, we’ve been testing this plugin successfully for several months now.
>> Given any site on the network is trying to go to the mapped
>> domain, I’m thinking some server side settings are messed
>> up somewhere. Nothing significant enough between WP 3.1
>> and 3.1.2 changed enough to affect domain mapping.
We haven’t changed a thing on the server. And the WordPress installation was created by doing a fresh restore of a backup of an installation that worked (including domain mapping). The only thing we changed in that installation was updating it from 3.1 to 3.1.2. Then everything fell apart. 🙁 This would be consistent with other reports that 3.1.1 or above breaks the plugin.
We will try restoring fresh again and not updating, to verify that it does work in 3.1. Maybe we missed something, but the configuration is pretty straightforward.
@andrea_r, I wanted to clarify…I’m not saying there’s absolutely nothing wrong with our configuration, or that it’s definitely the plugin’s fault. I just meant that this is baffling, as we’re using a proven install. It seems to have broken with the WordPress update, but we’ll definitely do regression testing to see if we missed something along the way.
Just wanted to clarify that my tone wasn’t meant to say it’s absolutely not our fault. We’re digging into it now to see, and I’ll report any relevant results.
Mark
Okay, first try has similar results. But in this case, the mapped domain points to the main site, not the sub site that the domain was mapped to. This leads to other problems including inability to log in as Super Admin because WordPress tries to resolve the mapped domain to the main domain.
More results as we test more.
Mark
the mapped domain should point to the main site on the server side, but within wordpress itself should direct it to the right blog. hrm.
Exactly. And it worked beautifully for a few months of testing, until the WP update. Weirder is the fact that we’re seeing slightly different results when we test now. Starting over with another fresh install…will report.
Mark
After upgrading, my mapped sites don’t allow logging in, instead constantly redirecting (I assume) to the login page in a never ending login loop. If the credentials are already present it does allow me in.
BTW, in some of our testing, we have seen this behavior too.
HTH,
Mark
Well, actually, we are doing it from a sub site as if we are a client/user, since we’re still in testing mode. That’s when the problem starts. As soon as the “user” maps the domain, everything breaks.
I just tried this in my test install where I do the DM development and had no problems. Try removing all of your other plugins and see if the issue persists.
One of the things I fixed (currently in the development version) is that under the right circumstances the domain_mapping table wasn’t being created.
Also, I have not been able to reproduce the redirect issue from the original post in this thread with either 3.1.1 or 3.1.2.
Thanks Ron, will do.
Do you think I should try with the development version right away, or troubleshoot the current release version? The fix you mention regarding the development version could conceivably explain this.
Thanks,
Mark
