You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
@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
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!
Does it still work in core if someone updates their site URL without the
DNS being updated? I’m not sure if a DNS lookup is in core but it’d be a
good addition. Guess the main advantage you’d get with Mercator is the UI
and SSO for users belonging to multiple sites on different domains.
On Fri, 19 Jan 2018 at 15:52, Antony Smith ***@***.***> wrote:
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!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#95 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABbeYxukHy1WOrwssPRr0dUsOv09rIyks5tMLoxgaJpZM4O-bOy>
.
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.
What else should be added to the readme?
The text was updated successfully, but these errors were encountered: