Support » Plugins » [Plugin: WordPress MU Domain Mapping] Multisite 3.0 and domain mapper

Viewing 7 replies - 1 through 7 (of 7 total)
  • I’ve traced it to 1) The login table isnt being updated, 2) remapped domains are not retaining the login state for the user.

    Setting primary domain to the subdomain makes everything work fine, but now when someone goes to the url in question it translates out as the subdomain.

    Using just sunrise.php and the domain_mapping table, with the domain-mapping plugin removed from the mu-plugins, setting the wpurl and siteurl to the mapped domain makes everything work, without having to go through the trouble of the redirects.

    Which leads me to believe that a domain mapping plugin that sets the wpurl and siteurl in that’s options would be sufficient.

    Which means a plugin like this written that allows you to add/remove from the domain_mapper or ‘reset’ from the wp_blogs would be more valuable and less intensive with the SQL calls per user.

    When primary domain or reset to original wp_blogs domain is triggered it updates the wpurl and siteurl in the options.

    WPMU Tutorials domain mapper here: for purchase has pretty much fixed all the issues with redirects and etc.

    Its behaving (more or less) how I was thinking donncha’s domain mapper should be behaving.

    Worth it.

    Frumph – tried the development version of the plugin?

    If the logins table wasn’t being updated what was being inserted into it?

    ^^ update.
    Donncha (the man the myth) worked with me on getting any issues fixed and it’s functioning great in wordpress 3.0 multisite now. (the development ver. of the plugin) dunno when it’ll be released.

    It was some weird problem with timestamp of the logins table. Dunno why it worked on Linux and didn’t work in Windows. I don’t think it has anything to do with WP 3.0 though.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] Multisite 3.0 and domain mapper’ is closed to new replies.