|
41.
|
|
|
An IP address has been automatically banned
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]AUTO_BAN_SUBJECT
|
|
42.
|
|
|
An IP address, {1}, has been automatically banned for generating {2} hackattack alerts. If you believe these were false alarms, or that the user was manipulated into triggering the alerts, you may wish to unban this IP address. A summary of the alerts follows:\n{3}\n\nManage IP bans from this screen:\n[url="{4}"]{4}[/url]
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]AUTO_BAN_HACK_MESSAGE
|
|
43.
|
|
|
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
|
|
44.
|
|
|
No such theme, <tt>{1}</tt>.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]NO_SUCH_THEME
|
|
45.
|
|
|
No such theme image, <tt>{1}</tt>.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]NO_SUCH_THEME_IMAGE
|
|
46.
|
|
|
There was a problem retrieving the XML data:
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]PROBLEM_RETRIEVING_XML
|
|
47.
|
|
|
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
|
|
48.
|
|
|
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
|
|
49.
|
|
|
(Referrer is: {1}, User agent is: {2})
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]REFERRER
|
|
50.
|
|
|
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
|