[TYPO3-core] RFC: #10322: Send Notification if BE is locked

Steffen Kamper info at sk-typo3.de
Thu Feb 5 23:04:51 CET 2009


Hi,

FYI: committed to trunk rev 4958 (after removing the empty line)

vg Steffen

Steffen Kamper schrieb:
> Hi Jeff,
> 
> Jeff Segars schrieb:
>> Steffen Kamper wrote:
>>  > yes, as i stated in internal list, this is not perfect. So my patch
>>> helps logged in users _not_ to loose their work.
>>
>> Yep, that's why I'm fine with it even without those small 
>> improvements. It's definitely an improvement over losing work :)
>>
>>> There is still the time window of the first 60 seconds where it could 
>>> happen that user try to save.
>>> If BE is locked, you don't see the login screen because of die, 
>>> that's ok imho
>>
>> One small clarification on this point: when the backend is locked, I 
>> do see the login screen.  It's only after login that it tells me the 
>> backend is locked...and that's what I have a small problem with :)
> 
> ah, you're right, after my patch login screen was visible.
> 
> I made a slight change to the constant defined in ajax.php
> define('TYPO3_PROCEED_IF_NO_USER', 2);
> 
> 2 is used only by ajax. It doesn't cjange behaviour as all compares use
> if(TYPO3_PROCEED_IF_NO_USER) ...
> 
> So i could make difference in init.php. Now with updated patch login 
> isn't possible again.
> 
> vg Steffen
> 


More information about the TYPO3-team-core mailing list