|
|
44.
|
|
|
No such theme, <tt>{1}</tt>.
|
|
|
|
|
No existe tema tal, <tt>{1}</tt>.
|
|
Translated and reviewed by
Nicolás M. Zahlut
|
|
|
|
Located in
[strings]NO_SUCH_THEME
|
|
|
45.
|
|
|
No such theme image, <tt>{1}</tt>.
|
|
|
|
|
No existe tal imagen de tema, <tt>{1}</tt>.
|
|
Translated and reviewed by
Nicolás M. Zahlut
|
|
|
|
Located in
[strings]NO_SUCH_THEME_IMAGE
|
|
|
46.
|
|
|
There was a problem retrieving the XML data:
|
|
|
|
|
Hubo un problema obteniendo la información XML:
|
|
Translated and reviewed by
Nicolás M. Zahlut
|
|
|
|
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.
|
|
|
|
|
Un posible intento de hackeo ha sido detectado. Por favor, no se alarme: aproximadamente la mitad de los intentos sospechados son producidos inocentemente (el programa intencionalmente tiene un modelo paranoico de seguridad, para darle una seguridad muy alta). Los intentos reales de hackeo son casi siempre causados por 'bots' (programas de computadora) que automáticamente se arrastran por la Internet buscando sitios que puedan contener vulnerabilidades, reportando lo encontrado a su 'dueño' para explotación futura (usualmente, asisten en la creación de spam). Si este fue un ataque de hackeo real, ha fallado - puede analizar los detalles registrados (en caso de que le dé alguna pista en cuanto un atacante real y persistente). Más información de seguridad es proveída en la documentación del programa.
|
|
Translated and reviewed by
Nicolás M. Zahlut
|
|
|
|
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
|
|
|
51.
|
|
|
You have gone to an URL which requires ‘posted’ data to be sent (<tt>{1}</tt>), 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
|
|
|
52.
|
|
|
It appears that you have made a file upload but exceeded this servers ‘post_max_size’ limit ({2}) or ‘upload_max_filesize’ limit ({3}). Unfortunately this renders your form submission invisible to the software. Please try again with a smaller size, or get the <tt>post_max_size</tt> limit increased. An alternate explanation is if you reached this URL manually – this URL is intended solely for processing the result of a form submitted to it, and the <tt>{1}</tt> parameter is missing.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]SHOULD_HAVE_BEEN_POSTED_FILE_ERROR
|
|
|
53.
|
|
|
Cannot read the <tt>{1}</tt> file. It is probably missing.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]READ_ERROR
|
