Closed cameronterry closed 5 years ago
The following syntax would make more sense to me conceptually:
# add and enable
wp --url="sites.my.com/siteone" darkmatter domain add www.example.com --primary --https --enable
# reserve and enable
wp --url="sites.my.com/siteone" darkmatter domain add www2.example.com
wp --url="sites.my.com/siteone" darkmatter domain set www2.example.com --enable
wp --url="sites.my.com/siteone" darkmatter domain set www2.example.com --disable
Grats
VERY MUCH STILL A WORK IN PROGRESS AND NOT COMPLETE BY ANY MEANS.
Complete rebuild of the plugin.
New Features
is_active
is now included in the logic, allowed Sites to be prepped with a primary domain but activated at a later time. (https://github.com/cameronterry/dark-matter/issues/13)$current_blog
(Site) and$current_site
(Network) - on every request.define( 'DARKMATTER_HIDE_UI', true );
.darkmatter_allow_logins
.darkmatter_domain_add
- fires after a domain is successfully added to the database and object cache.darkmatter_domain_basic_check
- fires at the end of the checks for a domain. Enables additional checks which are environment specific.darkmatter_domain_delete
- fires after a domain is successfully deleted from the database and object cace.darkmatter_domain_updated
- fires after a domain is successfully updated.darkmatter_primary_set
- Fires after a domain is set as the primary domain for a site.darkmatter_primary_unset
- Fires after a domain is unset as the primary domain for a site.darkmatter_restrict_add
- Fires after a domain is successfully added to the Restricted list.darkmatter_restrict_get
- Fires between the Restricted domains being returned from Object Cache and then going to the database.darkmatter_restrict_delete
- Fires after a domain is successfully deleted to the Restricted list.Improvements over 1.x.x
$current_blog
now utilisesWP_Site
. (https://github.com/cameronterry/dark-matter/issues/17)the_content
filter now occurs later, to catch all URLs, including those from additional implementations such assrcset
.get_home_url()
andhome_url()
) now map appropriately within the context ofswitch_to_blog()
(https://github.com/cameronterry/dark-matter/issues/3).muplugins_loaded
action, much earlier in the process lowering the amount of WordPress which is loaded before sending a redirect header.Backward Compatibility Notices
CLI Commands
Add / Update / Remove Domains
Examples of adding, removing and updating a domain for a Site.
Listing Domains
Examples of listing domains for a Site.
Examples of listing domains for the entire Network.
Retrieve all the primary domains for the Network.
Reserving Domains
Reserving a domain. This allows an administrator to setup the primary and / or secondary domains but stop Dark Matter performing redirects and rewrites. Please note; domains are enabled by default.
Restricting Domains
Examples of adding and removing a restricted domains for a Network. This permits administrators to stop domains from being used for a WordPress website; useful for organisations which use multiple CMS.
Examples of retrieving a list of all restricted domains for a Network.
Check / Upgrade Sunrise Dropin plugin
The following commands can be used to check if the Sunrise Dropin plugin (sunrise.php) matches the version contained with the Dark Matter plugin. You can also use the
update
command to install or update Sunrise Dropin.Check if the Sunrise Dropin plugin matches the version within the installed version of Dark Matter.
Install the Sunrise Dropin plugin (this command will error if a sunrise.php file already exists).
Update and / or replace the Sunrise Dropin plugin with the version within the installed version of Dark Matter.