2.3.1
- Fixed a major performance issue introduced in 2.3.0 for excessive database calls for primary domains. (#99)
- This was caused by a malformed cache set for primary domains, after it was moved to resolve an issue previously where it would update only the database when a new primary domain was set.
- Also removed an old call to set a primary domain, which is no longer needed and was causing irrelevant
UPDATE
SQL queries (it was essentially update the values to exactly what they were already).
- Moved the primary domain cache set when retrieving a domain to slightly later in the process.
- Atypical installations should not need to flush the cache. However, you may need to use WP CLI
wp cache flush
- or equivalent - after upgrading.
Full Changelog: 2.3.0...2.3.1