• Resolved Robert

    (@redrings)


    We just moved our network to a new base domain name and the domain mapping stopped working. Mapped domains were resolving to the base domain name. I uninstalled the plugin and deleted the two tables from the database. I then re-installed the plugin, but the tables were not recreated in the database. How can I get the plugin to recreate the database tables?

    Thanks!

    http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Robert

    (@redrings)

    Okay, I got the tables back by running these queries in the database:

    CREATE TABLE IF NOT EXISTSprefix_domain_mapping(id` bigint(20) NOT NULL auto_increment,
    blog_id bigint(20) NOT NULL,
    domain varchar(255) NOT NULL,
    active tinyint(4) default ‘1’,
    PRIMARY KEY (id),
    KEY blog_id (blog_id,domain,active))

    CREATE TABLE IF NOT EXISTS prefix_domain_mapping_logins (id bigint(20) NOT NULL auto_increment,
    id varchar(32) NOT NULL,
    user_id bigint(20) NOT NULL,
    blog_id bigint(20) NOT NULL,
    t timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
    PRIMARY KEY (id))`

    However, now I’m back to where I started with the mapped domains just going to the network’s base domain. Anybody have any ideas?

    Plugin Author Ron Rennick

    (@wpmuguru)

    Did you re-add the domain maps?

    Thread Starter Robert

    (@redrings)

    Hi Ron!

    If you mean by going to the sites with domain mapping and re-adding them via Tools->Domain Mapping, then yes.

    Thanks!

    Thread Starter Robert

    (@redrings)

    Can you tell me if prefix_domain_mapping_logins should have anything in it or not?: it has structure but there is no data to browse. prefix_domain_mapping contains a list of the domains we wish to map.

    thanks again!

    Plugin Author Ron Rennick

    (@wpmuguru)

    That table is for the remote/cross domain login. If you’re not using that feature, the table will be empty.

    The domains ending up at your main site could be your web server configuration.

    Thread Starter Robert

    (@redrings)

    Thanks Ron. That makes sense.

    I talked to our server admins and they said the following:

    We have a dns alias pointing to the cluster that hosts our site. We have a vhost with a server alias for http://www.ourwordpresssite.schooldomain.edu that redirects to ourwordpressite.schooldomain.edu

    mappeddomain.schooldomain.edu then is an alias to http://www.ourwordpresssite.schooldomain.edu

    They ensure me that this is the same configuration we had before we changed the site from ourwordpressite2.schooldomain.edu to ourwordpressite.schooldomain.edu (the Domain Mapping was working fine prior to the domain name change on the network base site).

    Any ideas or suggestions on how to proceed? Thanks again!

    Thread Starter Robert

    (@redrings)

    I just had them change mappeddomain.schooldomain.edu to be an alias for ourwordpresssite.schooldomain.edu instead of http://www.ourwordpresssite.schooldomain.edu – unfortunately that didn’t seem to make a difference…

    Thread Starter Robert

    (@redrings)

    Ron,

    Turns out the alias to www. wasn’t commented out so it was still going there. Everything is working again now.

    Plugin Author Ron Rennick

    (@wpmuguru)

    awesome 🙂

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] Not working after changing network domain name’ is closed to new replies.