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

[Steffen Kamper]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 10322_v4.diff
Type: text/x-diff
Size: 6610 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090205/a85731bb/attachment.diff