Project

General

Profile

Actions

Feature #48895

closed

Missing "Compare User Settings" in TYPO3 6.x

Added by Claus Harup almost 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Won't have this time
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2013-06-05
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

When upgrading to TYPO3 6.x the function Compare User Settings is missing....

See attachements...


Files

beuser01.png (27.3 KB) beuser01.png Claus Harup, 2013-06-05 17:35
beuser02.png (26.6 KB) beuser02.png Claus Harup, 2013-06-05 17:35

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #52141: show/display effective User-TSconfigClosed2013-09-19

Actions
Actions #1

Updated by Markus Klein almost 11 years ago

  • Status changed from New to Needs Feedback
  • Priority changed from Must have to Won't have this time

This module has been rewritten for 6.0.

Refer to https://git.typo3.org/Packages/TYPO3.CMS.git/blob/TYPO3_6-0:/NEWS.txt

Actions #2

Updated by Claus Harup almost 11 years ago

Having:

  • New backend user administration module
    The backend user administration module was created from scratch again. The
    interface changed a lot, it is now possible to filter large groups of users
    with certain criteria and to compare specific user information. The code was
    made more flexible to easily cope with different use cases and to be more
    open for future enhancements.

....should I understand it as it is not possible to view the userTSconfig settings for the various be_users at the moment?

Actions #3

Updated by Jigal van Hemert almost 11 years ago

After you select users for comparing (using the "compare" button in the list) these users are added to a list at the top of the module. Below the list is a button to compare the selected users.

In the compare overview the userTSconfig field is unfortunately not present. If this field is what you need in the comparison, could you please create a separate issue for that feature request? (Not to annoy you, but this issue already has a discussion in it and cleaning it up requires more effort than creating a new issue and closing this one)

Actions #4

Updated by Peter Niederlag over 10 years ago

see #52141

Actions #5

Updated by Jigal van Hemert over 10 years ago

  • Status changed from Needs Feedback to Closed

Closed because the feature request #52141 describes what's missing.

Actions

Also available in: Atom PDF