FloLaunch Cache conflicts
Strong caching plugins are known to cause conflicts to the FloLaunch test mode.
If you are encountering confusing behavior while using FloLaunch (test mode being visible to the public, changes not applying on the site etc.) a caching plugin is most likely the culprit.
One example would be the W3 Total Cache plugin. While this plugin has lots of useful and strong features to speed up your website, it has a few options that can sometimes cause inconsistent database reading, meaning that some changes are not reflected as expected.
If you are using the W3 Total Cache plugin together with the FloLaunch plugin, we strongly recommend disabling the Database Cache and Object Cache options while using FloLaunch: