TYPO3 Core

Sorry for the repeated posting, but it seems that even your bugtracker is buggy ;)
I got this error on sending my bugreport:
"SYSTEM WARNING: email_send(): open_basedir restriction in effect. [...]"

you`re right, clicking on the waste-bin icon won`t delete content elements. However, if an admin clicks on the pencil and switches to edit mode, he can delete the content element there. ASFAIK Robert is aware of the problem.

I could not reproduce your bug. I created a non-admin backend user, created a content element with the TV page module and deleted (ie. unlinked) it afterwards by clicking on the trash can icon. Works.

This is still an issue in Typo3 version 4.

A BE User (non-admin) can delete a content record by clicking on the 'Delete' Trashcan icon whilst editing the content record. However, in the TV Page view, the 'Unlink Record' trashcan icon does nothing unless I am a BE Administrator user.

After having the same kind of issue, I've followed the execution of an "unlink element" from the page menu and pointed out that BEuser must be allowed to edit tt_content-tx_templavoila_flex from the exclude fields.

In the BE screen of group or user config, the exclude field is named "Pagecontent: content" which is not so clear...

So, in my case, allowing this field to my user allow him to unlink content

I came accross the same problem in Typo3 4.0. It is not a bug, more of a user / group permissions issue. The problem I experience was that non-admin back-end users were able to create content but not unlink it or copy / cut & paste it on the same page.

The problem was fixed by allowing my 'Editor' group access to the following fields in the 'Allowed excludefields' list:
- Page: Content
- Pagecontent: Content

I'm pretty sure those fields are enabled by default but I tend to lock editors down (disable everything then enable only what they need) so it probably got broken during that process.

I can confirm this: the BE-users need Page:Content and Pagecontent:Content in allowexcludefields.
Is there something more to do in this issue or should it be resolved..?

But if you can ad content without these permissions, why can you delete content?

i can confirm this also. Non-admins need Page:Content and Pagecontent:Content in allowexcludefields.
imho this should be changed asap, because showing the content fields to normal editors is not very usability friendly...

They really need these two fields. Page:content is for flexform, which TV change, it is a property of the page. Pagecontent:content is for tt_content. All correct except that it is not clear for admins why it should be so... May be a warning in page module should be displayed...

hello,
i disagree that 'they' - the editors - need the fields page:content. they simply don't - templavoila need them to work properly. nobody uses these fields to show content on the website, thats all done in the module. and for admins it's a pitfall because - at least in my case - they only want to show the absolut minimum amount of fields which are needed for editors so that they can edit/create content. So imho tv constrains admins to show fields which clutters the interface of typo3 which is detracting the usability of typo3...

You must understand: TV has to modify this filed, so user must have access for it. If you do not want editors to see this field, hide it with TSConfig!

ok, hiding the fields are the best solution!

TCEFORM.pages.tx_templavoila_flex.disabled = 1
TCEFORM.tt_content.tx_templavoila_flex.disabled = 1

Moved issue to "Core" since the purpose of this one is now to cover the hook-request. Once this is done #3903 can be finished.

committed CGL-cleaned v3 to trunk, rev 7272