Invalid page path when <current> is an absolute URL (incompatible with Domain Source module)

Oof. So this module family creates a pseudo-multisite with multiple domains being served from one DB?

If that is the case, I don't think we should drop the domains from the url -- you'll want them later, to search and filter the API reports. Probably better to rewrite the not-much-better-than-a-placeholder Editoria11y API path validator to accept absolute paths. Maybe that should be replaced with a call to PathValidator or something like that?

This may have some downstream affects on the views as well; that would need to be tested once the API was accepting absolute URLs.

Thanks for considering this. That sounds like it could be a more robust solution than our simple workaround.

The reason why the workaround works for us is because, even with the Domain Source module installed, our path aliases are still required to be unique. So we have aliases like /domain1/home and /domain2/home where the reporting still makes sense to us without a domain present. We also have domain aliases set up for our different environments, like a dev.domain1.com or staging.domain2.com, which complicates it further.

Granted, we have a lot of custom code gluing this together, so supporting a full URL here might still be the better general solution.

Fixed in 2.1.19 →

Automatically closed - issue fixed for 2 weeks with no activity.

Drat -- reopening this as the fix caused a regression that prevents populating reports for sites that are installed in subfolders.