WordPress.org

Ready to get started?Download WordPress

Forums

WordPress MU Domain Mapping
[resolved] breaks site names when no primary is selected (7 posts)

  1. datapharmer
    Member
    Posted 3 years ago #

    When the domain mapping plugin is used with wordpress, but no domain is selected as primary for the blog (ie the domain.com/blogname is the primary by default) selectors that rely on the blog name all read domain.com where the should be domain.com/blogname or name of blog.

    If that sounds hard to follow, do this to reproduce:

    1. Create a wordpress 3. multisite install using subfolders.
    2. Create sub sites subsite1 and subsite2
    3. Install domain mapping plugin, map subsite1 to subsite1.domain.com and subsite2 to subsite2.domain.com but uncheck primary on each.
    4. Install plugin "Add Clone Sites for WPMU (batch)" from http://wordpress.org/extend/plugins/add-cloned-sites-for-wpmu-batch/installation/ and network activate it
    5. Go to Sites > Add Cloned Sites in the wordpress backend, click the dropdown list "Select the template site which will be cloned" and note that they are all the same name and impossible to distinguish between!

    Note that this is not specific to this plugin, using the Blog Diamond Multisite Widgets bloglist widget will generate a list that contains the same main site over and over again when using the domain mapping plugin, this is not an issue when the domain mapping plugin is not used or is an earlier version (not sure when this issue was introduced though).

  2. I'm not sure this woudl classify as a bug, since the main intent of using the plugin is to change the domain name.

    You are supposed to map the domain from the subsite, where you pick the primary domain.

  3. datapharmer
    Member
    Posted 3 years ago #

    This is definitely a bug:

    Here's why I think so:

    1. We do want to map domains, we just don't want the domains to be primary; if this isn't supported it shouldn't be allowed (ie you should be forced to pick a primary domain). Since it is allowed, it should be supported.
    2. At worst the plugin should not undo the built in wordpress function for listing blog names; if there is null data, do nothing, don't replace it with bad data!
    3. This worked fine previously!

  4. Ron Rennick
    MultiSite Guru
    Plugin Author

    Posted 3 years ago #

    "1. We do want to map domains, we just don't want the domains to be primary; if this isn't supported it shouldn't be allowed (ie you should be forced to pick a primary domain). Since it is allowed, it should be supported."

    If that's what you are trying to accomplish you are using the wrong plugin. That isn't what the Domain Mapping plugin was written to do.

    Just because software allows you to do something that leads to an non working state does not mean that the software has a bug.

    On your webserver you can delete all the files in your website which leads to a broken website. No one calls that a bug in the webserver software.

  5. datapharmer
    Member
    Posted 3 years ago #

    You are kidding right? This is not at all the same as deleting all the files in your website! If this wasn't considered as a possible use of the plugin then why is there a comment in the code that alludes this exact situation:

    // get primary domain, if we don't have one then return original url.

    And why did it work previously?

  6. datapharmer
    Member
    Posted 3 years ago #

    Ok, so this is a larger issue. Even if I set one of the subdomains as primary the same issue occurs.

  7. datapharmer
    Member
    Posted 3 years ago #

    closing this issue. determined it is due to deprecation of get_blog_list

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic