Bug #20180
closed
The Message "The backend is locked" is not translatable
Added by Yannick Pavard over 15 years ago.
Updated over 9 years ago.
Description
Hi,
The following message in typo3conf/init.php is not localized:
Browser backend is locked for maintenance. Remove lock by removing the file "typo3conf/LOCK_BACKEND" or use CLI-scripts.
See this revision for more information: http://forge.typo3.org/repositories/revision/27/4901
Thank You
(issue imported from #M10691)
Difficult task, because this is an Exception. These are currently not translateable, because they could happen even without translation support being able to load (e.g. database unavailable).
One idea would to make our language system work completely also without a working database connection, then we could tackle:
- error messages
- install tool
To be translateable. Thus postponing this to 4.6, sorry and thanks for your report. Contact the core team if you want to help in tackling this project.
I think #20589 basically dealt with the same kind of problem.
Maybe that helps us here, too.
- Target version changed from 4.6.0-beta1 to 4.6.0-beta2
- Target version changed from 4.6.0-beta2 to 4.6.0-beta3
- Target version changed from 4.6.0-beta3 to 4.6.0-RC1
- Target version changed from 4.6.0-RC1 to 4.6.0
- Target version changed from 4.6.0 to 4.6.1
- Target version changed from 4.6.1 to 4.6.2
- Target version deleted (
4.6.2)
6.1.0: the message is still hardcoded into /typo3/sysext/core/Classes/Core/Bootstrap.php
still present in TYPO3 6.2
Could it be made that if any content is found in file LOCK_BACKEND, it will be displayed to the User instead of the untranslated (and quite technical) message?
- Status changed from Accepted to Needs Feedback
Hey, if you add something like this in your typo3conf/LOCK_BACKEND: "/mystaticmessage.html" you can actually put anything in this file, even translated. Is this sufficient?
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by