TYPO3 Core

This is the same as #17384.

It seems to be somehow connected to #20335, #19644, #17298.

Yes, seem to have creeped up all at the same time. :)

I suggest to consider the proposed logic and respect the "Show ..." settings of the adminPanel instead of making an ad-hoc "show-all or hide-all on condition".

This is only true for the Web->View module, right?

Yes.

I don't know if this is an additional bug:

While investigating how I can teach enableFields() to declare "show on not logged in" content elements hidden in the presence of feGroup-simulation, I detected that a BE-user which has no workspaces enabled, sees the 'Preview of workspace "" (0)' message in his Web->View ... that also means that $this->versioningPreview is set, which kills all enableFields()-restrictions!

Workspace 0 is the default workspace? If workspaces are disabled, why does it lead to superpowers regarding element-visibility?

As a side-effect it means that the BE-user can't run start/stop-time simulations, because the necessary query is never extended/appended ...
Did I oversee something?

Maybe this is the real question:

• If workspaces are enabled, why does it lead to superpowers regarding element-visibility?

Why is this unconditional statement been made in the first place?:

if (!$this->versioningPreview || !$ctrl['versioningWS'] || $noVersionPreview) { // In case of versioning-preview, enableFields are ignored (checked in versionOL())

I mean intuitively a selection of a version and/or a workspace does not mean that now all is visible.? Just digging for the underlaying explanation ...

I fixed the "Preview of workspace" issue in 11311
I understood now why the superpowers and I'm going to make a final patch for 10951/9843.

Finally I'm going to add that the "Hide on FE-login" content elements appear with the "Show Hidden Records"-switch. Except you say no ...