Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify need for this plugin in the readme #95

Open
johnbillion opened this issue Aug 22, 2017 · 3 comments
Open

Clarify need for this plugin in the readme #95

johnbillion opened this issue Aug 22, 2017 · 3 comments

Comments

@johnbillion
Copy link
Member

A few people have asked if and why Mercator is necessary for domain mapping, especially since core's multisite routing now supports domain mapping out of the box. The current readme doesn't explain well why you might want or need to use Mercator.

  • Mercator supports multiple domains for each site.
  • Mercator correctly handles auth cookies for mapped domains.

What else should be added to the readme?

@roborourke
Copy link
Contributor

@johnbillion if you update your site url and the domain hasn't propagated does it make your site inaccessible or could you still get to the subfolder / subdomain? That's a compelling reason on its own

@antonyjsmith
Copy link

I'm still unconvinced of the need for this plugin anymore, I ditched Wordpress MU Domain mapping after support was added to core and haven't looked back. I've never had auth cookie issues with mapped domains. I also think multiple domains are more effectively and efficiently handled by the web server rather than wordpress. Obviously open to correction or any other rational for using that I'm not aware of though!

@roborourke
Copy link
Contributor

roborourke commented Jan 19, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants