Feature #17630

gr_list concept needs to be improved

Added by Michael Stucki over 13 years ago. Updated 3 months ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2007-09-27
Due date:
% Done:

0%

Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:
Needs Decision

Description

TYPO3 uses the "gr_list" which indicates the groups of which a frontend user is a member of.

This information is used to identify cache records, indexed records, and probably more.

If user A is a member of group 1 while user B is a number of groups 1 AND 2, both can't use the cached page which has been built for the other gr_list, even if their content is exactly the same.

One of the resulting problems of this are:
- page needs to be built multiple times (which is not needed in many situations)
- users cannot find indexed content before someone else having the same gr_list has visited (=> indexed) the page
(issue imported from #M6403)


Related issues

Related to TYPO3 Core - Feature #17638: Integrate possibility to show content elements depending on a given ruleClosed2007-09-29

Actions
Related to TYPO3 Core - Feature #17253: indexed_search should allways include indexed pages for "not logged in" userClosedDmitry Dulepov2007-04-27

Actions
Related to TYPO3 Core - Bug #16597: FE- Users with more than one group get wrong searchresultsClosed2006-09-26

Actions
Related to TYPO3 Core - Bug #15250: t3lib_BEfunc::blindUserNames() does not work sometimesClosed2005-11-30

Actions

Also available in: Atom PDF