-
Ran into a gotcha and think it could be improved.
If you have an Overlay that is published, and you set the Condition for that overlay to Draft, the Overlay behaves as if it has no Condition and then appears everywhere, even when the Condition is still selected in the Overlay settings.
It makes sense that an Overlay with no Condition selected appears everywhere. I get that.
However, it would be more useful for an Overlay that has a Draft condition applied to it to default to not showing at all. To prevent the issue where you have accidentally disabled the condition without disabling the Overlay. Or when you have accidentally created the Overlay and forgotten to publish the Condition in the first place.
Managing a long, separated list of Conditions and Overlays is already getting confusing for me, and I accidentally disabled a Condition while leaving the Overlay Published. This caused everyone to see an old offer on every page of my site after the offer had already ended.
An alternative would be to issue a warning when you set a Condition to Draft while it is still applied to an Overlay.
-
Hi there,
However, it would be more useful for an Overlay that has a Draft condition applied to it to default to not showing at all.
Why not set the overlay to draft directly?
-
Yeah you can do that. I’m just saying that it doesn’t seem intuitive to me that when you have a condition applied, if that condition gets set to Draft, the Overlay suddenly appears globally. I can’t think of a scenario where, if you have applied a condition, you would ever want it to appear globally unless you made a move to do so by manually removing a Condition that was applied in the Overlay settings.
Adopting my suggestion would eliminate the accidental scenario that happened to me, where I disabled the Condition but forgot to disable the corresponding Overlay. That’s easy to do when you are trying to manage two separate lists of Conditions and Overlays. It already feels cumbersome, so any way to help avoid accidentally globally publishing an Overlay seems like a reasonable feature request.
-
if that condition gets set to Draft, the Overlay suddenly appears globally.
When a condition is in draft, it’s expected that it no longer takes effect — that’s actually how the feature is designed to work.
I understand this might be frustrating, but your request doesn’t quite align with how the system is intended to function.
But I think showing the status of the condition in the overlay panel page would be a good idea, so you can tell if the overlay panel’s condition is set to draft. Something like this:
https://app.screencast.com/nCmlLngQtwfwhLet me know your thoughts!
-
Yeah, that’s a good idea. Especially if you make it red when it is a draft. It might help some people avoid this issue if they realise its significance.
That said, it wouldn’t have helped me. I set a condition to draft from the list of conditions by pressing the three little dots and popping open that little menu. I did that without realising that I had some published Overlays using that condition, which then caused them to go global.
If you can think of another way, in addition to your idea, to make it very clear when viewing the list of Conditions, which Conditions are attached to currently published Overlays, people would then know, with a quick glance, which Conditions can safely be disabled.
Thanks for taking the time to consider this scenario.
-
You are welcome 🙂
- You must be logged in to reply to this topic.