64516[BUGFIX] Re-add initialization of PageRepository::$where_groupAccess
Commit message
Review
-
Code review CR +2 Done
- Georg Ringer +2
- Oliver Hader +1
- Benni Mack +1
-
Verified V +2 Done
- Georg Ringer +2
- Benni Mack +1
- TYPO3com +1 CI
Issues 1
Files 1
Review log 1822
-
Thomas Hohn uploaded patch set 1 05/18/20, 12:51
-
TYPO3com voted on patch set 1 V -1 05/18/20, 13:04 Completed build in 12m 42s on Mon, 18 May, 01:04 PM Test Summary: 1 of 74284 failed Find logs and detail information at https://bamboo.typo3.com/browse/CORE-GTC-3436
-
Oliver Hader voted on patch set 1 CR +1 05/18/20, 13:08
-
Oliver Hader updated the commit message in patch set 2 05/18/20, 13:10
-
Oliver Hader voted on patch set 2 CR +1 05/18/20, 13:10
-
TYPO3com voted on patch set 1 V +1 05/18/20, 13:14 Completed build in 35m 14s on Mon, 18 May, 01:14 PM Test Summary: 73799 passed Find logs and detail information at https://bamboo.typo3.com/browse/CORE-GTC-3436
-
TYPO3com voted on patch set 2 V -1 05/18/20, 13:21 Completed build in 11m 14s on Mon, 18 May, 01:21 PM Test Summary: 1 of 74283 failed Find logs and detail information at https://bamboo.typo3.com/browse/CORE-GTC-3437
-
Andreas Kienast commented on patch set 2 CR -1 05/18/20, 13:38
-
TYPO3com voted on patch set 2 V +1 05/18/20, 13:41 Completed build in 42m 49s on Mon, 18 May, 01:41 PM Test Summary: 73799 passed Find logs and detail information at https://bamboo.typo3.com/browse/CORE-GTC-3437
-
Thomas Hohn commented on patch set 2 05/18/20, 13:49
PageRepository.php:156ReplyThis was so before - there is a guard in the constructor - Benni is under the impression that he removed it by accident.. -
Andreas Kienast voted on patch set 2 CR 0 05/18/20, 14:16
-
Oliver Hader commented on patch set 2 CR -1 05/18/20, 19:30
PageRepository.php:156ReplyAnd actually Benni's impression seems to be correct... by looking to the whole code (including the constructor), I wonder that this change actually fixes the bug * init (protected) sets it to empty string * constructor sets it to context-base value Does ext:solr have it's own PageRepository extending the core class (I don't think so)? -
Oliver Hader commented on patch set 2 05/18/20, 19:32
PageRepository.php:156Reply*"impression does not seem to be correct" (correction of my previous comment) -
Thomas Hohn commented on patch set 2 05/18/20, 19:58
> Patch Set 2: > > (1 comment)PageRepository.php:156ReplyI took the whole PageRepository class from 9.5.16 and "pasted" it into 9.5.17 and it works again. Then I debugged it down to this missing statement. The Solr version I use 8.x also calls the init method explicit, through "magic. Somehow it must assumes that the $this->where_groupAccess would be set to the empty string. The Solr code looks like and returns a "weird" rootline without this reset. I also heard about others having trouble indexing pages with TYPO3 9.5.17: public static function getAccessRootlineByPageId( $pageId, $mountPointParameter = '' ) { $accessRootline = GeneralUtility::makeInstance(Rootline::class); $pageSelector = GeneralUtility::makeInstance(PageRepository::class); $pageSelector->init(false); $rootline = $pageSelector->getRootLine($pageId, $mountPointParameter); $rootline = array_reverse($rootline); ...} So yes I mean that this is the cause. So if it was removed by "accident" then please re-add it. -
Oliver Hader commented on patch set 2 05/18/20, 20:04
Thomas, thanks for your reply. I don't know how to put that different - but by reading the code in context (including __constructor, I did not check that for my previous vote) it actually does not make a difference. This aspect would have been discovered when actually testing the patch in production. However, I was digging a bit further in the mentioned original change - yes, there seem to be some unconsidered tasks - specifically using frontend user groups and time-controlled content. I've pasted them into a new ticket → https://forge.typo3.org/issues/91432 Since ext:solr is (probably) using many different implicit contexts when invoking PageRepository, it's probably the reason for the misbehavior you experienced. -
Oliver Hader commented on patch set 2 CR 0 05/18/20, 20:15
Thomas, can you please post the reference to ext:solr where this is used - maybe I'm overlooking something (I checked master version of ext:solr). -
Benni Mack commented on patch set 2 V +1 CR +1 05/18/20, 20:33
This fix is correct for older versions of EXT:solr and TYPO3 v9, so I think this should be re-added properly. -
Oliver Hader commented on patch set 2 CR +1 05/18/20, 22:08
Thx for your feedback Benni! For plain use-cases without ext:solr at least it does not modify the behavior - fine with me. -
Thomas Hohn commented on patch set 2 05/19/20, 04:30
> Patch Set 2: -Code-Review > > Thomas, can you please post the reference to ext:solr where this is used - maybe I'm overlooking something (I checked master version of ext:solr). Solr versions below 10 would be affected - I'll inform the Solr team via the slack channel -
Thomas Hohn commented on patch set 2 05/19/20, 04:31
> Patch Set 2: > > > Patch Set 2: -Code-Review > > > > Thomas, can you please post the reference to ext:solr where this is used - maybe I'm overlooking something (I checked master version of ext:solr). > > Solr versions below 10 would be affected - I'll inform the Solr team via the slack channel It's the method public static function getAccessRootlineByPageId() -
Georg Ringer voted on patch set 2 V +2 CR +2 05/19/20, 10:54
-
Georg Ringer merged patch set 3 05/19/20, 10:54
PageRepository.php:156