|
44.
|
|
|
An IP address, {1}, has been automatically banned for generating {2} flood warnings in {3} seconds. If you believe that the user was manipulated into triggering the alerts, you may wish to consider unbanning this IP address. Be advised that the website software has essentially prevented what could be a 'DOS' (Denial Of Service) attack which could over-load the server if left to continue; it may have been triggered by innocent infected computers, or other form of computer manipulation. This said, this may just be an innocent computer that accidently or for good reason, using up a high server load.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]AUTO_BAN_DOS_MESSAGE
|
|
45.
|
|
|
No such theme, <kbd>{1}</kbd>.
|
|
|
|
Kein Thema mit den Name <kbd>{1}</kbd> vorhanden.
|
|
Translated and reviewed by
Nico Verse
|
|
|
|
Located in
[strings]NO_SUCH_THEME
|
|
46.
|
|
|
No such theme image, <kbd>{1}</kbd>.
|
|
|
|
Kein Themenbild für <kbd>{1}</kbd> vorhanden.
|
|
Translated and reviewed by
Nico Verse
|
|
|
|
Located in
[strings]NO_SUCH_THEME_IMAGE
|
|
47.
|
|
|
There was a problem with an AJAX request:
|
|
|
|
Es gab ein Problem mit einer AJAX-Abfrage:
|
|
Translated and reviewed by
Alex
|
|
|
|
Located in
[strings]PROBLEM_RETRIEVING_XML
|
|
48.
|
|
|
The network or website appears to be down, so an AJAX request has failed. You won't receive further warnings during this page view, but some actions may not work correctly until connectivity is restored.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]NETWORK_DOWN
|
|
49.
|
|
|
A potential hacking attempt has been detected. Please do not be alarmed: approximately half of the suspected attempts are triggered innocently (the software intentionally has a paranoid security model, to give you very high security). Real hacking attempts are almost always caused by 'bots' (computer programs) that automatically crawl the internet looking for websites which may contain vulnerabilities, and then reporting any found vulnerabilities to their 'master' for future exploitation (usually, to assist in spam relaying). If this was a real hack attempt, it has failed - you might want to try and analyse the logged details (in case it gives clues to a real and persistant offender). More information on security is given in the software documentation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]HACK_ATTACK_INFO
|
|
50.
|
|
|
An error occurred at:\n[url="{1}"]{1}[/url]\n\nThe full error details follow:\n\n[html]{2}[/html]
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]ERROR_MAIL
|
|
51.
|
|
|
(Referrer is: {1}, User agent is: {2})
|
|
|
|
(Referenz von: {1}, User-Agent ist: {2})
|
|
Translated and reviewed by
Nico Verse
|
|
|
|
Located in
[strings]REFERRER
|
|
52.
|
|
|
Language corruption detected and fixed (when looking up language string #{1}). This means that a database inconsistency had developed, but has fixed itself.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]LANGUAGE_CORRUPTION
|
|
53.
|
|
|
You have gone to an URL which requires ‘posted’ data to be sent (<kbd>{1}</kbd>), as well as the information in the URL itself. This is most likely because you have copied and pasted a link to a new browser window, but the page the link was for was a results page for an action.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]SHOULD_HAVE_BEEN_POSTED
|