First I’d like to thank the team for the amazing effort on putting together the v14! From a technical POV and as far as I can tell it’s a wonderfull piece of machinery.
I’ve been testing this new version on a client that has a huge DB (over 1M+ posts in the network and a peak 500k posts in a single site) and, for security reasons, has the wp-admin served on a different domain, e.g a full backend network DNS. Each site is served to the public with a proper DNS handled by the WPMU domain alias.
So far, so good.
Until Yoast v13, since all the content is generated “on-the-fly”, the URL’s are generated properly on the site-face, such as: og:* tags, canonical URL’s, and so on.
Unfortunately, with the v14 Indexables, on every update done on wp-admin, the indexed information is saved with the backend DNS and populated in the frontends with that data.
Are there plans to make the Indexables domain-friendly or must I apply the domain translation on every available filter to avoid this issue?
Thanks in advance and best regards,
- The topic ‘Yoast 14 Indexables and WPMU with domain alias’ is closed to new replies.