1.0.0 Release Candidate 6

• [Fix] The pre_option_home no longer fires on the page powering Customizer, meaning the IFrame loads on the Admin domain entirely. This should resolve;
  • An authentication issue which sometimes results in a "Cheating huh?" error.
  • A problem where Customizer couldn't load the IFrame if the Admin area is HTTPS and the mapped domain is HTTP due to browser security.
• [Fix] Removed an unused variable in the Admin-side pre_option_home filter handler.
• Removed a blank question in the FAQ of the readme file.

1.0.0 Release Candidate 5

• [Fix][Critical] An issue where Dark Matter would not catch all Admin requests to initiate the correct redirect.
• [Fix] Redirects for direct PHP files - like wp-login.php - no longer erroneously contain a trailing forward slash.
• [Fix] Improved the database version checking mechanism slightly for which, in some scenarios, may run more than once.
• [Fix] The first column of the Domain Mapping UI no longer just displays the digit one (1) but now the Domain ID.
• [Fix] Removed a breaking conditional when mapping "home" option on the admin side. This was causing issues with;
  • The "Visit Site" link in the Admin bar on the admin area.
  • Yoast SEO snippet preview when Editing a post / page.

1.0.0 Release Candidate 4

• Cleaned up and eliminated some code duplication on handling redirects from the admin actions for Add / Remove HTTPS, Make Primary, etc.
• [New] Dark Matter will now warn Super Admins if the SUNRISE constant is not detected.
• [Fix] admin_url() will no longer map to the primary domain if the URL contains "admin-ajax.php", as usage of this is common for AJAX powered plugins (for now).
  • This only occurs if WordPress is viewed through a "mapped domain" (primary or not) and should leave the admin-side untouched.
• [Fix] Redirects no longer erroneously contain a trailing forward slash after all the query string parameters.
• [Fix] An issue where sub-folder Networks would not redirect properly if omitting the trailing forward slash. (Thanks @svandragt)
  • For example; wordpress.test/sitetwo would redirect to www.example.com/sitetwo instead of www.example.com
• [Fix] If WP REST API v1.x.x is in use, then Dark Matter will no longer redirect to the primary domain.

1.0.0 Release Candidate 1

• pre_option_home now checks to make sure the URL is actually the one used for the domain mapping before changing it.
• This should improve the issue where Network Admin "Visit Sites" was being mapped for all websites and not just the one the user is looking at.
• Tidied up the readme.txt file to;
  • Standardise on the usage of WordPress Network / Network rather than WordPress Multisite / Multiste.
  • Line breaks now inline with Atom text editor.
• [Bug] $wpdb is now explicitly global rather than implied in sunrise.php file. (Thanks @svandragt)
• [Bug] Fixed a bug with sub-folder WordPress Networks where redirecting from the Admin Domain to the Primary Domain would in some scenarios omit the forward slash between Domain and Request URI.
• [Enhancement] Removed an unused parameter in dark_matter_api_get_domain(). (Thanks @svandragt)
• [Enhancement] Removed some unnecessary wp_die() calls on admin actions as the logic meant they would never be reached. (Thanks @svandragt)
• [Enhancement] Removed an unused variable on dark_matter_blog_admin_menu() which was designed to catch the hook name. But the implementation changed direction. (Thanks @svandragt)
• [Enhancement] Removed unnecessary declaration of $path variable inside dark_matter_redirect_url() function. (Thanks @svandragt)

0.11.0 (Beta)

• Completely rewritten the redirects logic to fix the following issues;
  • Post previews not working and being served from the mapped domain (rather than the admin domain).
    • This is because the parse_query action runs too earlier and the is_preview() API returns "false" rather than "true".
  • To ensure the Admin area redirects properly.
  • To ensure the Login page is always served on the admin domain.
• Fixed a bug where redirects from the admin domain to the mapped domain included an extra forward slash in the domain.
  • This in turn caused a double-redirect; one from the admin domain to the mapped domain and then a second from the double-slashed version to the single-slashed version.

0.10.0 (Beta)

• Fixed a typo with dark_matter_map_content() which prevented the logic handling array types (like upload_dir).
• Put in additional logic in dark_matter_map_content() so that it doesn't accidentally convert booleans to strings.
• The front-end redirect logic now detects if wp-login.php or wp-register.php is in use and exits, to let a more suitable process handle the redirection logic.
• Moved the dark_matter_prepare action to execute immediately upon inclusion of the dark-matter.php file and BEFORE the rest of the plugin loads.
  • This is so that actions and filters can be executed from being added in the scenario of a website not having a mapped domain.
• API dark_matter_api_get_domain_primary() now returns null rather than the original domain.
• Now checks to make sure we have a primary domain before attempting to change URLs.
• XMLRPC requests are no longer redirected.
  • This was preventing sites from connecting to WordPress.com for Jetpack functionality.
  • Jetpack now connects but the debugger fails with a "Could not validate security token" if Jetpack is not connected. However, if once connected the debugger claims all is fine!
• A lot of the fixes solves problems with sites which have no mapped domains.

0.9.0 (Beta)

• Removed the Network Admin page as it is currently has no options or need.
• Added the L10n API calls where relevant in the code for localisation.
• Standardised indentation to tabs rather than spaces for all files.
• Added a license block, as recommended in the WordPress.org Plugin Handbook.
• Changed the sunrise.php so that grunt work version is in the dark-matter/inc/ folder and the one to be used inside wp-content/ references the one inside the plugin directory.
  • This should make upgrades more seamless without manual intervention from site owners in the future.
• Removed a superfluous check on version number when retrieving the primary domain.
• Removed the sarcasm from the error message when someone has defined a "COOKIE_DOMAIN" value.

0.8.0 (Beta)

• Front-end redirect is now executed on parse_query action rather than template_redirect.
  • The way Yoast SEO sitemaps are generated means that template_redirect is never fired.
  • It has the added bonus of being a handful of actions before template_redirect, so means less of WordPress loads before issuing the redirect and is bit more efficient.
• Fixed the logic inside the front-end redirect so that it no longer attempts to fix both a domain and protocol mismatch at the same time. Now it is one or the other.
• Completed testing with Yoast SEO and Custom Post Type Permalinks plugins.

0.7.0 (Beta)

• Added primary domain to the allowed_redirect_hosts, so that it passes the validation for wp_safe_redirect().
• Set domain HTTPS API mechanism now respects the FORCE_SSL_ADMIN constant setting.
• Fixed the issue which caused the options on the Settings -> Domain Mapping admin panel to redirect to the Dashboard upon save.
• Fixed an issue in which the domain mapping would not fire or map correctly during a Cron job.
• Fixed an issue on the front-end domain mapping which now points admin URLs to the correct domain.

0.6.0 (Beta)

• Removed URL mapping from the filters "stylesheet_directory" and "template_directory" as these filters handle folder paths. Not URLs.
• Fixed a regex bug with the URL mapping API not handling the difference between HTTP and HTTPS URLs.
• Changed the upgrade mechanism to have a separate version number for the plugin itself and the database.
  • This is to stop database upgrade procedure running when it is not needed.