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
If I restrict the max item count of a content column via the max attribut in my backend layout, every thing is fine as long as the client adds new content elements with the "new item" button. If the client try's to copy an allowed content element, the client is able to paste the element without any count restrictions. Debugging the extension code shows that in line 80 of CmdmapDataHandlerHook.php a backend layout for the pid of the element not of the page is loaded...assuming the variable $pageId definied in line 67, 70 and 74 should store the page id not the element pid. This results that the loaded config for the colPos in line 81 doesn't containing any item restriction for the column of the element.
I am using TYPO3 Version 9.5.11 and Content Defender 3.0.11.
Thanks for your help.
The text was updated successfully, but these errors were encountered:
Hi @IchHabRecht, I haven’t checked the most recent version, the bug was reported way back in 2019 and until August last year the bug still existed. But thanks for the feedback.
If I restrict the max item count of a content column via the max attribut in my backend layout, every thing is fine as long as the client adds new content elements with the "new item" button. If the client try's to copy an allowed content element, the client is able to paste the element without any count restrictions. Debugging the extension code shows that in line 80 of CmdmapDataHandlerHook.php a backend layout for the pid of the element not of the page is loaded...assuming the variable $pageId definied in line 67, 70 and 74 should store the page id not the element pid. This results that the loaded config for the colPos in line 81 doesn't containing any item restriction for the column of the element.
I am using TYPO3 Version 9.5.11 and Content Defender 3.0.11.
Thanks for your help.
The text was updated successfully, but these errors were encountered: