CMS 4.0.0-rc2 released

@dan , just an FYI, I’m seeing this same behavior in the GA release that I updated to…

For me it seems that not all the modules that were already enabled stayed enabled after the upgrade.

Apologies, we hit very similar issues in other places too:

These will be fixed in a 4.0.1 patch.