[TYPO3-core] RFC #11799: Use typo3printError() if backend is locked
Oliver Hader
oliver at typo3.org
Thu Aug 27 09:19:49 CEST 2009
Hi Steffen,
Steffen Gebert schrieb:
> Hi!
>
> This is a SVN patch request.
>
> Type: bugfix
>
> Branches: trunk
>
> BT reference:
> http://bugs.typo3.org/view.php?id=11799
>
> Problem:
> You can create a file called typo3conf/LOCK_BACKEND to disable all BE
> access.
>
> If this file exists, TYPO3 will die("'Browser backend is locked for
> maintenance. Remove lock by removing the file "typo3conf/LOCK_BACKEND"
> or use CLI-scripts").
>
> Solution:
> make this nice-looking using typo3printError()
+1 on reading and testing
I removed the "chr(10)" from the end of the message since it's not
required at all. The block will always exit from script execution, thus
using die() is not required anymore.
I consider this as nobrainer that just represents a lowlevel message in
a different and better way. I'm going to take care of the commit later.
olly
--
Oliver Hader
TYPO3 Release Manager 4.3
More information about the TYPO3-team-core
mailing list