When you modify the date to set it with an older value, this result is to remove the slave site from the Multisites index like when a website is not confirmed (ie. cancelled).
In this case, the processing performed by JMS Multisites fails and it uses the "configuration.php" located in the current directory.
When you have deployed the slave site into a specific directory, this is the slave site configuration that may explain that you see the slave site.
If you don't set the date manually to an older date, the information remains in the Multisites index and in this case the expiration is processed.
I will try to see if I could keep in the Multisites index the expired slave site and not remove them from the list of slave sites. In fact, I remove the older slave site speed-up the processing.
|