Commit 67ad9d7a authored by Christian Kuhn's avatar Christian Kuhn Committed by Benni Mack

[TASK] Separate restore from delete in DataHandler

The DataHandler delete related methods still handle
too many things.
This is yet another divide & conquer patch: Move
the 'undelete' functionality to dedicated methods,
drop handling from 'delete' methods and refactor
'undelete'.
The result is a quite straight forward 'undelete'
implementation, plus reduced complexity in 'delete'.

Change-Id: I6ea2326fa2ad6de03c8cd3bd37184fff116fda06
Resolves: #93253
Releases: master
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67368Tested-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
Tested-by: default avatarTYPO3com <noreply@typo3.com>
Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
Reviewed-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
parent b66d495e
......@@ -747,7 +747,7 @@ class BackendUserAuthentication extends AbstractUserAuthentication
* @return bool TRUE if OK, otherwise FALSE
* @internal should only be used from within TYPO3 Core
*/
public function recordEditAccessInternals($table, $idOrRow, $newRecord = false, $deletedRecord = false, $checkFullLanguageAccess = false)
public function recordEditAccessInternals($table, $idOrRow, $newRecord = false, $deletedRecord = false, $checkFullLanguageAccess = false): bool
{
if (!isset($GLOBALS['TCA'][$table])) {
return false;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment