First: TIKIWIKI is now one of the best choices. - Here the "but be aware of":
The TIKIWIKI manuals, doc service and so on say:
- If you update TIKIWIKI over FANTASTICO, some part of content may be (or will be) lost.
- So this has to be checked before doing updates. Back-ups of content may be helpful in theory, in practice diffidult to restore prior state of all the reciprocal pointers, DB iids etc.
Possibly, FANTASTICO settled thsi aspect meantime. So check it before making decisions.
A different problem is :
On TCH the very newest TIKIWIKI version 18.104.22.168 will be installed by FANTASTICO - very good. - This had some basic config problems for PHP, or so. - TCH apparently just settled some such basic PHP configuration problems - at least, me new install of approx. 17 Dec. did not accept user registrations, but started to accept them since Dez. 19. (the only stated fault of 22.214.171.124: user registration impossible when server config's do not fit.)
A different current aspect is that TIKIWIKI apparently requires for extended features to execute a shell script /tiki/setup.sh . As far as I remember, we (mostly working in shared hosting) do not have SSH access on TCH (in fact a bit risky for shared hosting). - There are work-arounds for it, but do not count on them if you are not experienced for this.
The additional aspect is up to which level the individual site (shared hosting) can opt for individual configuration of Apache, without affecting global configuration for all accounts on the same server. As far as I could see in /tiki/setup.sh , Tikiwiki requirement there is still on the "free of problem" side, concerning this.
A further aspect to observe: Current Tikiwiki as by FANTASTICO only installs a very basic level (now, for TIKIWIKI v.126.96.36.199 from October 2007). Far more then CMS TYPO3, but practally all functions switched OFF. - Even user registration and WIKIs still not yet activated. - It is not too difficult to switch all the featutes to ON. But this apparently requires just those complications mentioned above. - While when installing on your own, you could opt for an extended initial configuration, with many functions already switched to ON,
So that is my current state of testing. - Some of the aspects here above have been brought into discussion on the TIKIWIKI forums. May be, I will soon have more clarity about it. May be that a new TIKIWIKI "stable version" willl soon provide better solutions. (The currnt TCH Tikiwiki is the newest "stable" version, very recent, TCH i top service. :-) )
The underlying more general problem is that PHP had now an evolution without thinking enough about backwards compatibility and consequently without enough behavior similarity from hoster to hoster. A problem for server configurators, for software providers and for site owners. The generated problems will accompany us still for a while... I think, 6 to 12 months...