Project

General

Profile

Actions

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.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-03-14
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #20167: Integrate nice looking message and integrate resend when backend was locked for maintenanceClosed2009-03-12

Actions
Related to TYPO3 Core - Bug #20589: Login page is not translatableClosedBenni Mack2009-06-07

Actions
Actions #1

Updated by Ernesto Baschny about 14 years ago

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.

Actions #2

Updated by Chris topher over 13 years ago

I think #20589 basically dealt with the same kind of problem.
Maybe that helps us here, too.

Actions #3

Updated by Xavier Perseguers over 13 years ago

  • Target version changed from 4.6.0-beta1 to 4.6.0-beta2
Actions #4

Updated by Xavier Perseguers about 13 years ago

  • Target version changed from 4.6.0-beta2 to 4.6.0-beta3
Actions #5

Updated by Oliver Hader about 13 years ago

  • Target version changed from 4.6.0-beta3 to 4.6.0-RC1
Actions #6

Updated by Xavier Perseguers about 13 years ago

  • Target version changed from 4.6.0-RC1 to 4.6.0
Actions #7

Updated by Chris topher about 13 years ago

  • Target version changed from 4.6.0 to 4.6.1
Actions #8

Updated by Chris topher almost 13 years ago

  • Target version changed from 4.6.1 to 4.6.2
Actions #9

Updated by Xavier Perseguers almost 13 years ago

  • Target version deleted (4.6.2)
Actions #10

Updated by Riccardo De Contardi over 11 years ago

6.1.0: the message is still hardcoded into /typo3/sysext/core/Classes/Core/Bootstrap.php

Actions #11

Updated by Riccardo De Contardi over 10 years ago

still present in TYPO3 6.2

Actions #12

Updated by Fabien Udriot over 10 years ago

  • Is Regression set to No

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?

Actions #13

Updated by Benni Mack almost 10 years ago

  • 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?

Actions #14

Updated by Alexander Opitz over 9 years ago

  • 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.

Actions

Also available in: Atom PDF