I also have a more general question- are upgrades usually fairly easy? I'm asking this because I just set up my wiki (I'm using 1.3.9- I couldn't get 1.3.10 to work) and I don't want to invest a lot of time on this thing if the data is not easily portable to newer versions or possibly even different wikis.
FWIW, my domain is hosted on an ultra-cheap service but I have ssh access and limited MySQL access and I was able to get the wiki up and running with minimal difficulty. To me, that indicates good design on the part of the developers that root access or rebooting is not necessary. Well done.
-cr
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been able to use <pre> and the <verbatim> tags, but <code> doesn't seem to do anything. Is there something special about this tag?
-cr
pre and verbatim are block tags,
code is just an inline tag.
So it must be within one block - one line usually.
Ah- I see now. Thanks for the help.
I also have a more general question- are upgrades usually fairly easy? I'm asking this because I just set up my wiki (I'm using 1.3.9- I couldn't get 1.3.10 to work) and I don't want to invest a lot of time on this thing if the data is not easily portable to newer versions or possibly even different wikis.
FWIW, my domain is hosted on an ultra-cheap service but I have ssh access and limited MySQL access and I was able to get the wiki up and running with minimal difficulty. To me, that indicates good design on the part of the developers that root access or rebooting is not necessary. Well done.
-cr
non-sql upgrades are trivial,
sql upgrades ask for the dbadmin password,
the dbuser who has the correct permissions.
?action=upgrade is all that's needed.
1.3.11 will change the tabel layout again, but action=upgrade will do that for you.