Bug #18330: Fatal error if caching is disabled and locking enabled - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #18330

closed

Fatal error if caching is disabled and locking enabled

Added by Uschi Renziehausen over 16 years ago. Updated over 14 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Oliver Hader

Category:

Communication

Target version:

Start date:

2008-02-28

Due date:

% Done:

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 2 (0 open — 2 closed)

Actions

Copy link

Updated by Peter Niederlag over 16 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.

Actions

Copy link