It's so odd, hopefully this gets rectified as a UX concern.
It was explained as a child lock. So the doors under the sink
no longer open, there's a "new feature" stopping the doors
from being opened. You have to disable that childlock in order to use
the doors.
At the moment this "child lock" is worded as "Disable
Private Pages". So in order to enable them you have to disable
them. I think "Choose an Option" means private pages are
disabled and "Disable Private Pages" means they are enabled.
The child lock is defaulted on, but it's not obvious that the child
lock was installed and the child lock is hard to find.
They haven't yet given us a way to convert a private page to a
public page, I think they just want people to stop creating new
"old style" private pages so it makes it easier to convert
them to "restricted public" when we get that feature, maybe?
Or they are trying to speed up a process to remove Private Pages
(/group pages) as a feature? I think private pages will be reborn as a
new feature in the future using permissions, but view permissions was
a tiny part of the features of private pages.
It feels like they are shrinking the feature set, in anycase I
think the intention is good I just can't make any sense of it.
I hear it makes sense in Hawkins, Indiana #upsidedown
