Bug #18330

Fatal error if caching is disabled and locking enabled

Added by Uschi Renziehausen over 13 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Communication
Target version:
-
Start date:
2008-02-28
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

After having updated my core this morning I got a fatal error in my frontend:
Fatal error: Call to a member function sysLog() on a non-object in J:\web\typotester.de\htdocs-neu\typo3\sysext\cms\tslib\class.tslib_fe.php on line 2737
Testing the revisions one by one, I found out that revision 3312 is the one that causes the error.

Regards, Uschi

(issue imported from #M7700)


Files

0007700.patch (1.01 KB) 0007700.patch Administrator Admin, 2008-02-28 10:39

Related issues

Related to TYPO3 Core - Bug #18279: Several problems with locking API (t3lib_lock)ClosedOliver Hader2008-02-22

Actions
Related to TYPO3 Core - Bug #18654: Fatal error on calling sysLog() of lock object if locking method is unknownClosedOliver Hader2008-04-21

Actions
#1

Updated by Peter Niederlag over 13 years ago

I can at least confirm that the changeset 3312 seems not to be fully accurate.

we have a try/catch block for (!is_object($lockObj)) in there. It does not make sense to:
a) use $lockObj before this try/catch block
b) use $lockOb within catching the exception

I guess Oliver might be the best guy to solve this.

#2

Updated by Oliver Hader over 13 years ago

Committed to TYPO3_4-2 (rev. 3314)

Also available in: Atom PDF