You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Behavior
When allowedColPos is set for templateLayouts in PageTSConfig, the layout is not removed if the colPos is not allowed.
Expected behavior/output
If 1.allowedColPos = 1, the layout 1 should not be visible if the content element is in a column other than colPos=1
Environment
TYPO3 version: 11.5
news version: 10.0.3
Composer Mode: yes
Possible Solution
This is where the real problem begins. The solution already existed in ticket #810. However, this was undone with ticket #963. I can't quite understand the reasoning from the ticket. What exactly was meant here? Even if I remove the option allowedColPos or activate this option only for one of the templateLayouts, I get the correct layouts for selection with the solution from #810$allLayouts[$layout[1]] = $layout;.
Is there anyone who can confirm this or test the other option if there are still errors here?
The text was updated successfully, but these errors were encountered:
Bug Report
Current Behavior
When allowedColPos is set for templateLayouts in PageTSConfig, the layout is not removed if the colPos is not allowed.
Expected behavior/output
If 1.allowedColPos = 1, the layout 1 should not be visible if the content element is in a column other than colPos=1
Environment
Possible Solution
This is where the real problem begins. The solution already existed in ticket #810. However, this was undone with ticket #963. I can't quite understand the reasoning from the ticket. What exactly was meant here? Even if I remove the option allowedColPos or activate this option only for one of the templateLayouts, I get the correct layouts for selection with the solution from #810
$allLayouts[$layout[1]] = $layout;
.Is there anyone who can confirm this or test the other option if there are still errors here?
The text was updated successfully, but these errors were encountered: