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

Jetpack Monitor: Use mapped domains on multisite #180

Closed
v18 opened this issue Nov 19, 2015 · 1 comment
Closed

Jetpack Monitor: Use mapped domains on multisite #180

v18 opened this issue Nov 19, 2015 · 1 comment

Comments

@v18
Copy link
Contributor

v18 commented Nov 19, 2015

When Monitor is activated on a multisite with mapped domains, the alert emails use the "base" URL, rather than the mapped domain. Ideally we'd use the mapped version everywhere we showed it to a user.

8d0907de-5240-11e5-9efb-f9ad29ecadf1

In this example, originaldomain.mainsite.com is mapped via mappeddomain.com.

@jeherve
Copy link
Member

jeherve commented Apr 28, 2016

I wasn't able to reproduce the issue on my end. Mapped domains on Multisite appear to be displayed properly in my Monitor emails. Here is an example:

screen shot 2016-04-28 at 5 47 18 pm

That domain is mapped to a subdomain of the network admin, but this was handled by Jetpack.

In this happens again, I'd suggest trying to disconnect Jetpack from WordPress.com, and then reconnect it to force an update of the Jetpack options, and make sure the site URL is properly synchronized.

@jeherve jeherve closed this as completed Apr 28, 2016
jsnajdr pushed a commit that referenced this issue Jan 27, 2020
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

2 participants