[TYPO3-dev] in 6.0 can't edit BE user groups from Backend Users module

[Philipp Gampe]

Hi Stefano,

Stefano Cecere wrote:

> @Philip: TYPO3 CMS is a "dying" project.. (if NEOS wants to grow).. i
> don't see why i should pain to bring back perfectly working features,
> taken off by no public reasons by someone.. it should be up to who
> removed / refactored those features, to take care about them.
> at least explaining the positive effects of these changes!

I guess you don't know much about code :(
The pain for bringing back features is, that you need to bring back all code 
that was required to drive those features.

Actually the new extbase version (rewritten from scratch) is much more 
powerful:

1. Add this snippet (e.g. at line 13) to
typo3/sysext/beuser/Resources/Private/Partials/BackendUser/IndexListRow.html

<td>
	<f:for each="{backendUser.BackendUserGroups}" 
as="backendUserGroup">
		<a href="#" onClick="showClickmenu('be_groups', 
'{backendUserGroup.uid}', '1', '', '', ''); return false;" 
title="id={backendUserGroup.uid}">
			<bu:spriteIconForRecord table="be_users" 
object="{backendUserGroup}" />
		</a>
		{backendUserGroup.title}<br />
	</f:for>
</td>

This will show the user groups the same way as in the compare list. You 
might as well want to create an edit link for each user group:
<a href="alt_doc.php?edit[be_users]
[{backendUserGroup.uid}]=edit&returnUrl={returnUrl}">

(must be inside the for loop above)

To make changes persistent, copy the partials folder to an extension and 
change the default TS such that you modify the partials path (untested).

The same way you could render nested groups, however you might need to 
extend the mapping information from the default TS shipped:
typo3/sysext/beuser/Configuration/TypoScript/setup.txt

If you want those changes to become part of the core, please file at least 
an issue or even better provide a patch.

> (the same happened with the new em, and FAL.. all new features or
> refactored ones that are giving more headaches than benefits)
> for hot new stuff.. there's NEOS!

Neither Flow nor Neos have FAL!


Just because you might not see the benefits, that does not mean that there 
are none. Nobody does patches without a clear purpose.

We do our best to refactor only parts such that the whole construct does not 
crash. Once a while, we overlook a certain feature or do not consider it 
important enough.
If you have ideas, please share them. If they are easy enough, someone might 
jump in and do it for you.


BTW, took me 5 minutes to check and test the solution for your problem with 
a bit of minimal extbase knowledge.

Best regards
-- 
Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
Documentation – Active contributor TYPO3 CMS
TYPO3 .... inspiring people to share!