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

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


Hi Jeff,

Jeff Segars schrieb:
> Steffen Kamper wrote:
>  > thanks for the text, much better :-)
>>
>> I changed it this way, removed progress (first i wanted to have 
>> animation) and added info icon, see screenshot.
>>
>> vg Steffen
>>
>>
>> ------------------------------------------------------------------------
>>
> 
> Thanks Steffen. I'm really close to giving my +1 on testing but I've got 
> one more outstanding question.
> 
> The info box looks really nice and seems intuitive for someone working 
> on the site. However, when a user starts to log in and the backend is 
> already locked, they log in with no indication that the backend is 
> locked. After their login is processed, they get the white screen with 
> the die() message that tells them the backend is locked. Before this 
> patch, the die() message appeared as soon as /typo3/ was visited and not 
> after login.
> 
> If we're going to use the die() message, then it seems like that should 
> happen before login.  If we let the user login, then we should use the 
> ExtJS modal box.
> 
> I'm sure there are some technical considerations for why this needs to 
> be the behavior, but I just wanted to ask to be sure :)  If it can't be 
> changed, then I'll go ahead and give my +1 on testing.
> 
> Thanks!
> Jeff

yes, as i stated in internal list, this is not perfect. So my patch 
helps logged in users _not_ to loose their 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

vg Steffen


More information about the TYPO3-team-core mailing list