[TYPO3-core] RFC: Bug #7630: Locking Problems with TSFE->set_no_cache()

[Uschi Renziehausen]

Oliver Hader wrote:
> FYI: Committed to TYPO3_4-2 (rev. 3312)
> 
> olly
> 
> 
> Oliver Hader schrieb:
>> Hi,
>>
>> Michael Stucki schrieb:
>>> Hi Olly & Jeff,
>>>> Thanks for your patch. The debug during development is fine, maybe we
>>>> can introduce a global configuration property to toggle this logging 
>>>> via
Morning,
after having updated my core this morning my FE ended up with the 
following error caused by this patch:

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

I opened up a BT entry for this: http://bugs.typo3.org/view.php?id=7700

Did none of you experience this error?

Regards, Uschi

>>>> install tool / typo3conf/localconf.php?
>>>
>>> Call t3lib_div::sysLog() and set severity to "info" (0). That should be
>>> complitely fine for things like this.
>>>
>>> So can you please incorporate the sysLog() calls from Jeffs patch?
>>>
>>>> What do you think?
>>>
>>> Reviewed & tested, +1!
>>
>> I've modified the post patch of #7333. It has the following 
>> modifications:
>> * adds a new method t3lib_lock::sysLog() which calls again 
>> t3lib_div:sysLog and prepends some common information, e.g.:
>> 25-02-08 18:09 - cms: Locking 
>> [simple::0aeafd2a67a6bb8b9543fb9ea25ecbe2]: Acquired lock
>> 25-02-08 18:09 - cms: Locking 
>> [simple::712fa1bc0bb5e4e6a491065c075cecd2]: Acquired lock
>> 25-02-08 18:09 - cms: Locking 
>> [simple::0aeafd2a67a6bb8b9543fb9ea25ecbe2]: Released lock
>> 25-02-08 18:09 - cms: Locking 
>> [simple::712fa1bc0bb5e4e6a491065c075cecd2]: Released lock
>>
>> * added a new class variable $resource which is used for the filename 
>> of the lock or the semaphore resource
>> * changed to disposal of class variable $id to contain the hash which 
>> was used to create the locking resource (=identifier)
>> * added a check if typo3temp/locks/ directory exists and creates it
>>
>> Please test and review this patch again. Thanks!
>>
>> olly