WordPress.org

Ready to get started?Download WordPress

Forums

WordPress MU Domain Mapping
[resolved] Does Not Appear To Work With 3.1.1 (23 posts)

  1. ng.tinyreef
    Member
    Posted 3 years ago #

    I am using 3.1.1 and it appears as either your plugin is not working or your configuration tutorial has not been modified to work with the latest version of multiuser.

    I have uninstalled the plugin and I have set everything up.

    My sites seem to work fine except I am unable to login as SuperAdmin on my other sites.

    I have been able to successfully redirect the sites WITHOUT using your plugin except I have had the superadmin login issue.

    I am using *.mydomain.com wildcard redirects and I am using the latest (fresh) install of wordpress 3.1.1
    any advice would be greatly appreciated!

  2. markb1439
    Member
    Posted 3 years ago #

    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?

  3. treydock
    Member
    Posted 3 years ago #

    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

  4. markb1439
    Member
    Posted 3 years ago #

    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.

  5. 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.

  6. bluenote
    Member
    Posted 3 years ago #

    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.

  7. markb1439
    Member
    Posted 3 years ago #

    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

  8. 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.

  9. markb1439
    Member
    Posted 3 years ago #

    >> 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.

  10. markb1439
    Member
    Posted 3 years ago #

    @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

  11. markb1439
    Member
    Posted 3 years ago #

    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

  12. 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.

  13. markb1439
    Member
    Posted 3 years ago #

    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

  14. markb1439
    Member
    Posted 3 years ago #

    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

  15. Ron Rennick
    MultiSite Guru
    Plugin Author

    Posted 3 years ago #

    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.

  16. markb1439
    Member
    Posted 3 years ago #

    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

  17. markb1439
    Member
    Posted 3 years ago #

    Actually, in retrospect, I think I remember seeing the notice that the domain mapping table was created each time I tested and activated the plugin. The notice didn't appear on the Network Admin page, but showed up as soon as I switched to Site Admin.

    But I'm happy to try the development version.

    Thanks,

    Mark

  18. Ron Rennick
    MultiSite Guru
    Plugin Author

    Posted 3 years ago #

    You can look at the history of any plugin via the development log link in the sidebar of the plugin page. Once on the development log you can look at the view changes to see what changes were made.

    In this case, I moved a line of code and changed a text string.

    Do you think I should try with the development version right away, or troubleshoot the current release version?

    Once we start on a newer version we never try to troubleshoot the release version.

  19. picard102
    Member
    Posted 3 years ago #

    So I take it I shouldn't try to use this plugin on 3.1.2?

  20. Ron Rennick
    MultiSite Guru
    Plugin Author

    Posted 3 years ago #

    So I take it I shouldn't try to use this plugin on 3.1.2?

    I take it you skimmed the thread...

    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.

  21. picard102
    Member
    Posted 3 years ago #

    I read the posts. 4 people are having issues despite you not being able to reproduce the problem, and the thread is still marked as unresolved.
    I figured that was enough reason to ask anyways.

  22. Ron Rennick
    MultiSite Guru
    Plugin Author

    Posted 3 years ago #

    There has been no one in the thread who has reported the issue since I said that.

    As far as this (or 99.9% of the other) plugin goes, there is no difference in WP 3.1 through 3.1.2. The only thing that happens in maintenance releases of WP is bug fixes. There are no functional changes in the plugin or theme API, database structure, etc.

    I've been writing plugins for 6 years and having to update a plugin due to a maintenance release is extremely rare.

    The original poster indicated he/she edited the sites in network admin. Undoing that would be the first step in troubleshooting/fixing the problem.

  23. bluenote
    Member
    Posted 3 years ago #

    I re-mapped my sites and otherwise played with the config and was able to fix my problem.

    Love the plugin, I'm grateful for the work developers have put in, thank you.

    If I could just comment though, getting defensive and quoting credentials is a pretty good way of making sure you don't have any *reported* bugs.
    It's not really a substitute for not having any bugs though. And in the end this may be more of a combination of circumstances and not a per se bug.

    Personally this problem actually cropped up (I believe) between one of the last few point updates to WP and/or the last point update of domain mapper (I dont think there's been two?). Unfortunately I was not often logging in to my installation or mapped blogs so I can't be exact.

    I'm happy with how the plugin is working for me now and I don't have any skin in the game beyond that so please feel free to ignore this.

    thanks for your work on this Ron

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic