Execute TYPO3 core master pre-merge tests. Auto generated! See Build/bamboo of core git repository.

Build: #136 was successful Manual run by Bamboo CLI Admin

Build result summary

Details

Completed
Duration
12 minutes
Flags
Custom build
Labels
change-65107patchset-1
Revision
51a9d0cc057d774e3be36342e7761496a0dfc0f3 51a9d0cc057d774e3be36342e7761496a0dfc0f3
Total tests
74473
Successful since
#118 ()

Tests

Custom variables

Name Value
patchset 1
changeUrl 65107

Code commits

Author Commit Message Commit date
Christian Kuhn <lolli@schwarzbu.ch> Christian Kuhn <lolli@schwarzbu.ch> 51a9d0cc057d774e3be36342e7761496a0dfc0f3 51a9d0cc057d774e3be36342e7761496a0dfc0f3 [BUGFIX] No bogus log entries when discarding workspace records
Selecting a page and records on the page to be discarded in the
workspace module can lead to log entries that records could not
be deleted.
This can happen when discarding (deleting) a page that only exists
in the workspace already has deleted records on the page. The explicit
call to delete single records then creates this log.
The solution is to ask the DataHandler if the record in question
has already been deleted to avoid deletion in this case.
Additionally, the log entry now contains the table:uid to
make it more useful in case it pops up again.

Resolves: #61719
Releases: master, 10.4
Change-Id: I8fee34fad2484e9e656bcb5ff611a91374127d94
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65106
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Daniel Goerz <daniel.goerz@posteo.de>
Reviewed-by: Daniel Goerz <daniel.goerz@posteo.de>

Jira issues

IssueDescriptionStatus
Unknown Issue TypeCHANGE-65107Could not obtain issue details from Jira
Unknown Issue TypePATCHSET-1Could not obtain issue details from Jira