Actions
Bug #42111
closedLockfiles retain on sql error, no further versioning is possible for affected record in the fututer
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2012-10-18
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
if you try to publish a page and i.e a sql error occurs there will be retain a lockfile for this page so that even if the error is removed the file stays locked in PATH_site.'typo3temp/swap_locking/ an can't be published
\typo3\sysext\version\class.tx_version_tcemain.php
...
// Lock file name:
$lockFileName = PATH_site.'typo3temp/swap_locking/' . $table . ':' . $id . '.ser';
if (!@is_file($lockFileName) ) {
...
After deleting the lockfile in PATH_site.'typo3temp/swap_locking/ everything works fine again
Is ist for example possible to add a max lifetime to the lockfile and request in like
if (@is_file($lockFileName) && $maxLockFileLifetime > now() ) {
Actions