primeros pasos

<note important> A la hora de hacer un buen seguimiento de control de cambios, los arreglos de texto o composición (poner negritas, corregir un error tipográfico, arreglar una lista que no sale bien) tendrían que marcarse como Minor Chages antes de guardar. </note>

En el caso de que sea requirido crear una sub-página de esta sección se han de aplicar los siguientes criterios:
namespace (crear nueva página):

[[namespace1:namespace2:<nombre sub-página>|nombre de la sub-página]]

tag:

{{tag>tag1 tag2}}

para evitar que aparezca un resumen en la zona superior derecha de los temas que se tratan en la página, poner en cualquier lado:

~~NOTOC~~

1. hacer una copia de seguridad del directorio (ojo, dokuwiki no usa BDD, es todo sobre fichero de texto): \\eurocity\e$\eurocity.es\www\root\wiki
2. descargar la actualización pertinente
3. copiar en el directorio, sobrescribiendo

Proceso de Instalación Proceso de Upgrade

Origen

By default DokuWiki checks a special URL for messages once a day. This message system is used to notify administrators of DokuWiki installations about new releases and security warnings.

When the ACL is enabled , messages are displayed only to superusers.  If ACL is disabled, all users can see the message.

The feature needs to contact ''update.dokuwiki.org'' on Port 80 - make sure your firewall allows this. If you don't want this feature, you can disable it with the updatecheck option in your config manager.

Each message has a unique ID shown in square brackets. Only messages which have a higher ID than the one configured in ''conf/msg'' will be shown. When you upgrade to the release announced in the message, the ''conf/msg'' file will be upgraded as well, suppressing the message. If you don't want to upgrade to an announced release you can simply increase the number in ''conf/msg''.

When upgrading your installation, it might happen that DokuWiki continues to show the update message, even though the number in ''conf/msg'' was increased by the upgrade. This is because DokuWiki caches already fetched messages for a day and will only refetch if the last modified timestamp of ''conf/msg'' is higher than the one of the cache file. To stop the outdated update message from showing you can simply wait a day, touch((//touch// is a UNIX command to change a file´s date and time, the so-called "timestamp")) the ''conf/msg'' or delete the ''data/cache/messages.txt'' cache file.