Loading...
 
Skip to main content

Features / Usability


Is Tiki right for my company?

Hey there, erm... Gary?

I've been very busy trying to find a suitable wiki/cms package suitable for my place of work. We are very 1990 when it comes to communication around here. Suffice to say, Tiki seems to be the ONLY PHP/mysql package I can find that combines a wiki and blogs (most important features for us) and supports LDAP to boot. Mediawiki is great but it would be inappropriate (by design) for use here, TWiki looked good too but I can't go about learning perl/cgi just to find out I'll never know enough to get it rolled out properly.

Anyway, though there are some things about Tiki I'm not crazy about, it's feature set seem to make it, my only option (props to the devs. you are really onto something here). Some answers to a couple questions would just make me feel better about moving on:

1. What kind of adoption rate is Tiki enjoying? (I see it's relatively popular on sourceforge).
2. Will it require advanced skills to upgrade to future versions?
3. Any major changes around the corner I should hold off for?
4. What's the deal with needing absolute URLs to link to images in the galleries from the wiki? Booo!
5. No warning of simultaneous wiki edits?

Everything else looks awesome. Really like the modules (latest activity, blog posts etc). Customized menus based on user groups is great too. This could really change the way we communicate/collaborate.

Cheers,

Lucas

Hi. Thanks for your interest.

1. I'm not sure about the adoption rate. Marc Laporte would know better about that. There are 6000 or so downloads per month. I'm not aware of a breakdown in terms of movement to and from Tiki, etc. or type of user.
2. Maintaining a smooth upgrade path is a priority ("Preserve the environment" in Tiki terminoloy) so upgrades should always be possible for non-experts to handle using the web interface.
3. Version 1.10, which is available now as a beta, is already very solid and has a lot of features beyond what's in 1.9 — WYSIWYG editing, tags, more view options like fullscreen and fullscreen editing window, Ajax (mostly for images and MyTiki info so far) to name a few. You can see the full list on ReleaseProcess1_10_0 (some of these have been backported to 1.9). Of course the 1.9 branch is more tested so is a better choice in terms of security at this point.
4. Relative URLs work fine for images in wiki pages. If this isn't working at a particular site, there must have been a site installation or configuration problem. I don't recall any reports here about people needing to use absolute URLs.
5. Warning of simultaneous editing is in fact a configuration option in TikiWiki. Do we need to update/correct a feature list somewhere?

About LDAP, I don't use it myself and haven't really followed the discussion, but my impression is that it might not be smooth as silk to set up. You can check this forum — LDAP forumQuestion — for more information.

-- Gary

Thanks for the reply!

Found the edit warning setting (forgive my laziness).

Wrt image linking, the tips/syntax/hints displayed (which I love) when browsing images in a gallery read...

"You can include the image in a tiki page using one of these lines:
img src=http://cardweb/tiki/show_image.php?id=4&scaled&scalesize=0
img src=http://cardweb/tiki/show_image.php?name=cob.png&scaled&scalesize=0"

I guess I was mislead by this... I tried "img src=show_image.php?id=4&scaled&scalesize=0" and it worked fine. I just don't want our employees using absolute references (should we ever change things around). On another note, can I make just the thumbnail appear on a tikipage? one that links to the full image in a gallery (wikipedia style)? Having a hard time finding a simple way to do that. I suppose it's right in front of me like the rest.

Again, thanks. Feeling better about this route all the time.

Lucas