You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
improve efficiency of isRecordsOnPageShouldBeChecked
possibly get rid of the function isRecordsOnPageShouldBeChecked or some functionality by performing the checks in PagesRepository::getPageList => however some checks should be performed in pages (e.g. for doktype = 3 and doktype=4 but not for records), but could be
be careful: is not called for table pages, is only called for other records, should maybe do pages first or store result in $this->pids
do not make this so complicated => some of the content which should not be checked should not really exist in the first place (e.g. tt_content on doktype = 3 or doktype = 4
alternative: make isRecordsOnPageShouldBeChecked configurable (it seems pretty resource-hungry and is of little value)
instead of fetching each page, already do a join with pages on fetching records
(handle in separate issue!) in BE do not fetch all broken links (and paginate the entire array), fetch only max. 100 at a time
isRecordsOnPageShouldBeCheckedshould be reducedisRecordsOnPageShouldBeCheckedisRecordsOnPageShouldBeCheckedor some functionality by performing the checks inPagesRepository::getPageList=> however some checks should be performed in pages (e.g. for doktype = 3 and doktype=4 but not for records), but could be