Project

General

Profile

Actions

Bug #71950

closed

sys_log doesn't show latest sys_history Entry if there are multiply with the same sys_log_uid

Added by Andreas Allacher over 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Start date:
2015-11-29
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
On Location Sprint

Description

Due to the fact that sys_history Relation (via Icon) is done by transmitting the sh_uid which is retrieved by quering sys_history for sys_log_uid
and that is done by using the magic function findOneBySysLogUid or via direct query without any order by.

The icon might link to older records instead if sys_log has been truncated previously but not sys_history.

The easiest solution for now would be to query for the latest record in sys_history with the corresponding sys_log_uid.

It is realted to https://forge.typo3.org/issues/55298

However, where as #55298 proposes to decouple sys_history and sys_log (which is a good idea) for a first solution to 6.2 and 7.6
it would be good to just get the latest entry of the sys_log_uid in
\TYPO3\CMS\Backend\History\RecordHistory
and
\TYPO3\CMS\Belog\ViewHelpers\HistoryEntryViewHelper

so just ORDER BY tstamp DESC in RecordHistory and a corrsponding method for the HistoryEntryRepository which then will by called in HistoryEntryViewHelper.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #55298: sys_history broken because of sys_log taskClosed2014-01-24

Actions
Actions

Also available in: Atom PDF