Bug #91432
Updated by Oliver Hader almost 4 years ago
Looking into @PageRepository::enableFields@ reveals that the cache-identifier probably should have more information, e.g. some "state-hash" of the currently applied Context. h3. Currently considered * show-hidden - context:visibility/includeHiddenPages * workspace ID - context.workspace.id h3. Probably not considered * starttime/endtime - context:date/accessTime * -fe_group fe_group - context:frontend.user/groupIds (has it's own cache - but does not modify @PageRepository_hidDelWhere@ cache identifier)- ** not affected, since excluded with @$ignore_array@ in @init@ method identifier) h3. Expected impact Using @PageRepository@ without taking these two additional aspects into account, it might happen that invoking @PageRepository@ multiple times with different contexts (having different aspects for date and frontend.user) leads to unexpected results - basically, the first @PageRepository@ invocation defined the where clause.