An admin can set an expiration date on a site or one can be set automatically when the site is created.
Admins can set what will happen to expired sites – there are four choices:
To set an expiration date:
Sites that are expired but not deleted will have labels automatically applied to them in the site list:
Additionally, you can quickly filter the site list to view expired sites:
As mentioned earlier there are four options that can apply to a site when it expires. You can set these in the SETTINGS area.
When you create a new site you can automatically set an expiration date for it.
To do this you use SITE PACKAGES.
Site packages have an EXPIRE SITE option. If this is set and the site package is used when creating a site, the new site will automatically have an expiration date calculated and applied to it.
If a site is expired (and not deleted of course), you can un-expire it:
You can force a site to be tagged as ‘expired’. However, the rules for an expired site (such as applying an admin lock or password protecting the site) will not be executed. The only effect this action will have is to tag the site as expired – it will also show up in the site list as expired with the associated labels.
To force a site to expired status:
You can combine Site Expirations with Disk Quotas and Custom Post Type Quotas in an interesting way.
You can set a site expiration when a quota is exceeded – example, 30 days. This allows the site to stay up for a period of time after the quota is exceeded. Then, when the expiration date arrives, stricter expiration rules can apply (such as deleting the site or locking it.)
Two bulk actions are optionally available in the site list.
To use these actions you must first enable them in SETTINGS:
Now you should see two new items in the BULK ACTIONS menu in your site list:
You can set a site package for a WooCommerce product. This means that IF the site package has an EXPIRE SITE value, it will apply to new sites when the product is purchased and the new sites will have an expiration date.
One thing to keep in mind is your setting for what happens when a site is expired. If you set the option to delete the site, it is possible the site will be deleted but your customer’s subscription will still be in effect.
Thus, it is better to create subscription products with one time payments if you intend to delete the site when it expires. You can do this by setting the subscription payment to zero but using a one time fee and automatically cancelling the subscription after 1 month:
You can, of course include this product in a GROUPED product so that the customer can have the option to upgrade to a real subscription before the site expires.
When a site is cancelled, you can specify that it is set to ‘expired’ after X days instead of being deleted right away. Then, for your ‘expiration’ options, you can specify that the site is to be deleted.
This allows you to give your customers a grace period to change their minds about the cancellation.
Availability: Requires WPCloudDeploy 5.7 or later.