[Resolved] [Plugin: W3 Total Cache] Preview mode usage
The Preview mode buttons are confusing.
The 3 buttons “Disable”, “Preview”, and “Deploy” do very different things. Yet they sit right next to each other with the “Disable” button highlighted.
– Enable/Disable: toggles preview mode
– Preview: launches a separate page. This is confusing because I’m already in Preview mode. So why would I hit Preview again. Maybe this should say “Preview new settings”?
– Deploy: seems to be equivalent to hitting Disable (which deploys) and then Enable again. Or maybe “Disable” doesn’t deploy, and I have to hit “Deploy” before I hit “Disable”; otherwise I lose all my changes. So I’m not sure if this button is necessary. Another way to look at it is: if “Deploy” is a sort of “Save settings”, then does “Disable” auto-save?
The top of the settings page doesn’t help much:
Preview mode is active: Changed settings will not take effect until preview mode is “Disable” or “Deploy”. “Preview” any changed settings (without deploying), or make additional changes.
How can “preview mode” be “deploy”?. That doesn’t make much sense: new settings or changes can be deployed, but not a mode. “Disabled”, I can understand because that’s a state that a mode can be in. But “deploy” is not a state, it’s an action — which only applies to settings.
Plus the grammar is confusing without “d” and “ed”.
Maybe it should say:
Preview mode is active: you can make changes to the settings and check the effects by hitting “Preview new settings”. Changed settings will not be deployed for your visitors until you “Disable” preview mode. To deploy your new settings but keep preview mode active, just click “Deploy”.
I would also rename the “Disable” button to “Deploy + Disable”. Then the relationship between “Disable” and the “Deploy” button would be clearer.
(Unless I completely misinterpreted the buttons, of course)
- The topic ‘[Resolved] [Plugin: W3 Total Cache] Preview mode usage’ is closed to new replies.