Posted By: Orlin on January 15 2011 08:06 am
There is not bulgarian language ("bg" lang folder)! But above in the article us wrutten "bulgarian" maybe to boost search results?

Posted By: Mike on January 9 2011 04:36 pm
I would seriously question the productivity possible with this package. If you want to get things done quickly, I suggest you look elsewhere.

This is great software for students and technically interested people that have a lot of time, and want to play with something. There are loads of options, and possibilities. However, this is not recommended for pure business purposes. It is likely that you will spend far more time than you will gain.

I hope the developers of Tiki Wiki, or the community see the absolute need to produce different versions of this package. 'One size fits all' just does not do the job well enough nowadays. What this package needs is focus, not just on-going development of modules.

As someone else said, the main aspects of this system can be done much quicker with other CMS or wiki systems.

My point is, who can use this and gain from it? The one thing it could do well but doesn't do easily is project management. If you need a pure wiki, why would you want to go through the 100 other options? If you want a community portal, there are better options.

The reason for the long post? Because Tiki Wiki has enormous potential, but only if developers connected with this project get more focus - it can't be everything to everyone. Otherwise it will be become nothing to no-one.

Easily installable profiles don't help, because you just end up with an example system and no knowledge of how it fits together. so modifications / additions are more difficult.

Take the hint. Why were profiles needed? Because it was too complicated. Solve the complications (not by creating profiles), focus the development, and this could be a really good system.

for the time being, my advice is save your time, decide what you actually want, and look elsewhere.

p.s. If people involved in the project would like to discuss this, I am quite open to that.

Posted By: Randall on October 1 2010 08:59 am
Nice. Thanks for making this available. Looking forward to testing Tiki6 to see if some of the bugs are worked out.

Posted By: christine on September 8 2010 08:08 pm
It seems that there is a mix of Polish and English in this demo version.

Though one could flounder through makes it very difficult for single language people.

Posted By: nkoth on September 1 2010 01:31 pm
By the way, in Tiki now there is a search feature that searches for the configuration options that match what you are looking for in the admin panel. Yes there are many options, but with the search it's easy to find, plus with Tiki Profiles can be scripted.

Posted By: jonny B (a Tiki dev) on August 7 2010 07:06 am
I agree there are far too many things to configure, but i doubt we could get rid of more than a dozen or two, even if we really really tried. Each checkbox will have a champion! That's just "the Tiki way" - keep it optional and everyone has a right to keep what they need.

Meanwhile, have any of you (saying it takes too long to set up etc) tried "profiles" in Tiki? Check out http://profiles.tikiwiki.org for more.

Thanks for the kind words as well though, it's nice to know we're going in the right direction generally! :)

Posted By: Tiki is a really nice Wiki, but...... on August 2 2010 11:58 pm
Like everyone said, the admin is a total mess. There is FAR too much to play with. In all reality, there doesn't need to be this many options and configurations. If kept this way, there should be "Simple" or "Minimal" variations accessible with the click of a button. Or a simple "Advanced" menu option.

Sure, it is, in my opinion, the most powerful Wiki out there and is probably the best looking one, but man, it takes hours and hours to do a very simple task that I can accomplish in 1 or 2 minutes in Drupal or Joomla.
Some items should also be combined to increase admin user friendliness. I'll still use it, as it really is a great Wiki, but I sure wish they'd ditch some of these useless options. A lot are just not needed. Even still, I'd choose it a million times over Media Wiki, that's for sure!

Posted By: Oliver on July 22 2010 07:23 am
the installation is a standard one..but the administration is a mess. too many switches and tweaks distributed over a dozen of config pages...this wiki/cms may be a powerful one, but it's usability and administration however are only for those with lots of time to find out how to do simple things..
i spent couple of hours trying to display a navigation menu for non-registered users..

Posted By: Jack on April 9 2010 01:50 pm
Couldn't even get it installed on 2 different platforms following their instructions to the letter. Also used IRC chat for help in the matter and was unable to get help with the install. I eventually gave up and I'm not linux guru but I've installed and used hundred of apps that required configuration. This one was a waste of my time.

Posted By: ricks99 on March 22 2010 05:16 pm
To vasco:

The link is working correctly for me. The correct URL should be: http://php.opensourcecms.com/free/videos/tikiwiki.php?videoid=1

Posted By: vasco on March 22 2010 03:30 pm
Maybe someone would like to fix the link in the first video
#1 Installing TikiWiki
It presently goes to shopping carts.
Not a good reference for this complicated wiki which seems impossible to upgrade with fantastico

Posted By: ricks99 on February 17 2010 11:03 pm
To edibile: Tiki's UI is a continuous work in progress. Each release continues to improve the overall UI experience. Take a look at http://dev.tikiwiki.org/AdminUIRevamp for details.

Posted By: edibile on February 3 2010 06:01 pm
The admin area is a mess!!
Maybe it's very powerful, but I think they have to improve accessibility and usability..

Posted By: soulhunter on November 25 2009 07:21 am
In answer to: Fidelis C Obodoeze

Hi!

You should try the tikiwiki forums at tikiwiki.org, or the users mailing list. I'm sure that there you will find someone who will give you that step-by-step guide.

Posted By: Fidelis C Obodoeze on November 6 2009 11:27 pm
TikiWiki seems to be an ideal solution for a complex community portal but I am scared by the complaints about its ambiguity in installation. Can somebody out there give me a clear step-by-step guide on how to install TikiWiki 3.3 on my XAMPP server?

I will appreciate it.

Posted By: George on August 5 2009 08:25 pm
I tried it. Took an age to upload. Huge footprint. Plus there is a bit of a learning curve. Agree with others, it's quite frustrating to set up.

Posted By: Jen on June 25 2009 10:15 am
If you can present an outline-style of navigation, then this is a good choice. I am still trying to figure it out.

Posted By: littledove22 on April 22 2009 09:13 am
TikiWiki is the best CMS out there. I have been developing in it since 2002. I have rarely had to add features, its all there. The CSS and themes make it really easy to use and change layout, plus page templates, widgets, video integration and layered permissions.

TikiWiki trumps Plone, Drupal, any other CMS hands down.

50 sites and counting, all built on TikiWiki.

Posted By: mythus on April 17 2009 12:21 am
Ok I tested this a little bit.

The good points:

There is a lot of functionality to this product. You can add mods and such with the click of a check mark, the forums work decently as do the wiki, photogaleries and such. As far as functions go, this has a lot going for it. It is also very fast and responsive. I noticed also that it uses css themes, so theming should be incredibly easy.

The bad points:

The way it is set up is extremely cluttered. I'd suggest a more uniformed approach, with an admin back end that separated the different functions in pages than tabs. I would add the administrative functions of thinks like forums and wiki into for example an admin page for the forum set up all tied into the forum options, instead of on the forum page itself and in the nav menu as is now. Really, the way everything is thrown together is confusing to navigate, and I have navigated my fair share of CMS'es. It can be done, but it should be neater and more organized. I'd say this is this project's weakest point, something that should be improved upon.

I am intrigued by this cms, and it comes close to matching the cms I use and love now. So over all, good job. Fix up the navigation and clutter and this would be gold.

Posted By: Xavi on April 12 2009 01:41 pm
Hi "tikiwiki long on features, short on data integration":

I understand what you say. However, MediaWiki and TikiWiki target different type of communities. Both with their strengths, and both with weaknesses. For what you say, you need more a Mediawiki type of software product. Glad you found it. Whenever you are in a group/project where "just a wiki" is not enough, you'll be welcome to help make other products (such as TikiWiki, or whatever else suits you the best) a bit better.

I'm glad with TikiWiki product and community, and the work being done, since it suits my needs of many many projects, groups, communities.

I'm very glad the MediaWiki exists, since it suits very well the need to produce a huge encyclopedia (or encyclopedia-like web sites).

And I would be very pleased when TikiWiki and/or MediaWiki support the WikiCreole markup, which in my honest opinion deserves to be "the standard" no wiki markup. You can google for it a bit, and you'll know why.

Cheers, and long life to free software communities and products! :-)

Posted By: Boxx on February 9 2009 01:19 pm
Oh my god, it's UGLY UGLY UGLY !!!! and confusing too. Clearly developed by technicians.

Posted By: tikiwiki long on features, short on data integration on January 11 2009 07:44 am
Tikiwiki has lots of features but they are quite poorly integrated. Everything including configuration files should be wiki pages, especially since the permission system already makes those configurations that shouldn't be seen, easy to hide. It's social features are also sadly lacking, they are nowhere near as reliable and readable as mediawiki, facebook or most other wikis, which make edit summary lines something akin to tweets (twitter), letting you know what others are up to right now.

Its worst misfeature however is "its own" data format that is incompatible with mediawiki's. If only they would ditch their worthless format in favor of extending mediawiki's (things like ==+ HEADER2 instead of the !! nonsense) they would find a huge number of people want the mobile, maps, blog-like comments, RSS inclusion, calendar and so on...

But we all know mediawiki, thanks to Wikipedia, will be around in twenty years, and it's data format will always be supported. We have no such assurance about tikiwiki and so its a dangerous data jail. You can always get your data out of mediawiki format into something else, but you can't be sure you can get it out of a minor wiki's format - ever.

Then there's the naming problem. Everything in the known universe has been named already in mediawiki's admissible title characters, in fact it's been named in every language humans speak almost. And they've argued over it for weeks or months sometimes to pick the exactly correct neutral name to avoid conflicting or appearing biased or overlap, and they're constantly improving this massive ontology. In the meantime over in tikiwiki-land, I am all alone with my naming scheme, and no one else will ever help me with what things should be named unless I pay them. That is not fun.

Finally if I want to spread some page around from mediawiki I just cut and paste, say into a Wikipedia talk page on that topic. From tikiwiki? No such convenience. If I've got to have people updating other wikis to spread the word, they'll have to learn mediawiki no matter what. So using tikiwiki just slows them down and confuses them. No fun.

Please, tikiwiki team, ditch that failed data format and make yourself a better front end for mediawiki format data. It won't be difficult, make that a goal of 3.0.

And if you think having a flexible parser that supports several formats including mediawiki solves this problem, you simply have not understood what I've said. There is no way that any obscure parser used only by a very few people is going to be supported well enough and have the bugs all worked out. If a native data format is retained at all it becomes a huge suck of talent and time away from what we really need: a better user interface to our mediawiki data.

Tikiwiki obviously has all the UI geeks but mediawiki has all the data management geeks. And guess which one I want writing my CMS?

Posted By: Gary Cunningham-Lee on August 6 2007 09:37 pm
I'm not sure what to make of comments like this in view of the active community support at tikiwiki.org and something like 950 pages of docs at doc.tikiwiki.org: :I found that TikiWiki has limited online instructions for this ,(and the module in not very intuitive)and the community support for this task is negligible. I don't recall seeing a post about the adsense module recently in the forums. Did you try posting there? Also, the documentation pages are a work in progress. We would appreciate any specific feedback if you find them inaedequate, etc. About the Adsense module, did you see [doc.tikiwiki.org]? Thanks for trying Tiki but, again, it is a large collaborative effort and it's best to give feedback directly so any problems can be solved. -- Gary themes.tikiwiki.org

Posted By: Cruth Aitheoir on August 4 2007 02:57 am
As a person with low-to-middle level experience and expertise, I have to say I have an initial not-great experience. I did easily set the site up, via CPanel Fantastico installer; and it works fine, so far, but when I went to do what should be a simple task, ie add adsense code, I found that TikiWiki has limited online instructions for this ,(and the module in not very intuitive)and the community support for this task is negligible. Considering how widely used adsense is, these seems like NOT a good sign for TikiWiki. 2 hours later, I am giving up. I tried to log-in to TikiWiki, and its says I need to activate cookies, but my cookies ARE activated.

Posted By: Marc Laporte on December 27 2006 07:45 am
Hi 'Some Call Me Tim', I thank you for taking the time to evaluate Tiki and to share your thoughts. However, I disagree strongly with many of your comments and certainly your conclusions. I especially object to your comment 'and would not recommend it to anyone'. How could a project as popular as Tiki not be good 'for anyone'? I have prepared a general page which addresses common concerns / questions about Tiki (which covers many of your comments): http://marclaporte.com/TikiSucks Here are some replies to your other comments: 'Advertised compatibility with Postgres is just wrong' -> OK. I see some bug reports http://dev.tikiwiki.org/tiki-searchindex.php?highlight=PostgreS&where=pages&search=go Many CMSs offer only MySQL. Besides, this should be easy to fix for someone with 20 years of experience :-) 'Modifying the system can only be done through annoying hacks/patches' -> What type of feature would you like to add? Depending on the answer, there are several ways to add functionality to Tiki: A great deal of modifications can be done using the templates. Tiki uses the Smarty template engine and some basic programming is possible there. You can save these custom *.tpl files in their own 'theme' to override the default templates, and to make sure future upgrades are easy. http://themes.tikiwiki.org/tiki-index.php?page=Template+Overview Also, new functionality can be achieved in many ways: Mods: http://mods.tikiwiki.org Plugins: http://tikiwiki.org/PluginsList New feature: http://dev.tikiwiki.org/Hello+World Advanced developers can create their own custom applications from the Galaxia Workflow Engine: http://workflow.tikiwiki.org/ In my experience, Tiki is very easy to upgrade. I have used other 'modular' systems before and it was more complex to upgrade because the 'core' and the 'modules' were not released at the same time, and this adds burden to the site admin to manage versioning (which is problematic especially for less technical users) 'In forums, comments always have a 'Vote' and a 'Score' option' -> I just fixed this and it will be in Tiki 1.9.8. 'Integrator plug-in...' -> Integrator is a powerful but complex feature to integrate apps. Again, this should be fairly easy to fix for someone with 20 years of experience :-) For people with less technical knowledge, I recommend using 'featured links' instead. This is a simple iframe of an external site. 'Menu configuration is terrible' -> That is the default system menu. It is designed to be smaller or larger depending on how many features are activated. You can and should create your own menus with the menu generator. You can also change ' Maximum number of records in listings:' at tiki-admin.php?page=general 'What Tiki CMS needs is not a complete rewrite. I mean, why? There are other projects that could better use good developers' time. My next project will be on Drupal, which so far seems elegant and well designed. We'll see how long that lasts. :)' I don't know if this is your case, but often, people with strong programming skills underestimate the unique challenges & dynamics of an Open Source project, especially a community-development project like Tiki. Some people come from a commercial background and think that they can manage an Open Source project the same way they managed a team of paid staff to work on a project. Some will design something which supposed to be 'superior', but it is too complex for people to use & participate to. Tiki is designed so many people with different skill levels can participate and improve the application. 190+ people have contributed to Tiki via CVS so the model has proven that it works and it scales. So somewhere, somehow, all these people thought it was a worthy enough project. Do you know a lot of Open Source projects with as many contributors? And countless others have helped with tech support, testing, documentation, etc. For people that do get involved in development, they want a friendly place, access to other people to bounce ideas & ask for some help. Most of them also want to be able to contribute back. While I disagree with your conclusions and many things you brought up, I do thank you for taking the time to write your detailed message. You shared your opinion in a polite way while expressing serious concerns about Tiki. I hope you will find the ideal system for your needs. Most people reading this forum are not 'high level software engineer/architect with 20 years of experience'. They are reading this site to select a CMS or a groupware. I am worried they will be scared off by your (IMHO unfair) comments. For many years, I have read criticisms / concerns / etc about Tiki's design. It won't scale, it will implode, etc, There was a lot of FUD http://en.wikipedia.org/wiki/FUD However, here we are. Tiki is 4 years old. It's a mature, very powerful application, with a large community of contributors, with tons of features and which is used on tens of thousands of websites & Intranets. Of course, there are a lot of things to improve and there will always be. Please see: http://doc.tikiwiki.org/Features to see if Tiki is a good application for your needs. Remember: if you don't need a feature, don't activate it. However, if you need it in the future, it's only a few clicks away. And remember also, Tiki is open source and open development. YOU can participate to its future. Best regards, M ;-) Marc Laporte Project admin Tiki CMS/Groupware

Posted By: Some Call Me Tim on September 12 2006 01:29 am
I'm a high level software engineer/architect with 20 years of experience. I just completed installing and am currently running TikiWiki 1.9.4, and in conclusion, if I had to do it all over again, I would have chosen another CMS. The parts of it that work seem to work well enough, and we will continue using TikiWiki for the immediate future. However, I apologize to the developers who have put many hours of work into this project for what I'm about to say. I honestly think this is a project that has a dead-end code base and would not recommend it to anyone. I wish that someone had warned me how inflexible and brittle the code was before I wasted time setting it up here. It has a lot of stock features that are nice, if you happen to want exactly what it offers and no more. It seems to lack anything like a plug-in architecture. If you need to do anything that isn't in the current feature set, you'll need to hack the main code base yourself, meaning that the next security update patch will be a nightmare. What this means to non-programmers is that only features that get adopted into the main code base are going to be stable--that's why it ships with so many features. It HAS to in order to support them all. Other CMSs can have plug-ins that don't touch main code, so you have more plug-in developers. Here are my specific comments: * Advertised compatibility with Postgres is just wrong. It sorta-kinda works, but things like the MyTiki page and others are completely broken. Based on this, I wouldn't trust claimed compatibility with anything but MySQL. * Modifying the system can only be done through annoying hacks/patches: The plug-in architecture is poor. Trying to be constructive, I'd say that there aren't enough hooks. In order to add search functionality, for instance, I had to modify core source code. In Drupal, e.g., you just create a search hook and it gets called along with the rest. * The architecture in general is poor: Relational databases are meant to have each data item in one place, and then reference it via its index. In the dozens of Tiki tables that reference a user name, it's a text field in each one. This means that there's a massive function (many pages) to change a user's name that must know about each table that references a user name. Not only is this slow, it's dangerous: Adding a new table and forgetting to update this function could get your database into an inconsistent state. It's just a bad practice. * While there seem to be plenty of options I can turn on or off, some features that I don't really need or want are not configurable: In forums, comments always have a 'Vote' and a 'Score' option, which is inappropriate for my uses, for instance. * The 'Integrator' plug-in came with default settings for reading Doxygen files that were just wrong. It looks like the settings were entered into the database wrong--instead of $1 and $2 for parameters, it listed 1 and 2 (undecorated). * Menu configuration is terrible: The preconfigured menu breaks down into 18 slow-to-load pages of options, most of which are disabled when the feature doesn't exist. We aren't really pushing the Tiki CMS to its limits here--small (private) user base, with only a minority of features in use. To have run into this many configuration problems and limitations for our uses speaks volumes for me. What Tiki CMS needs is not a complete rewrite. I mean, why? There are other projects that could better use good developers' time. My next project will be on Drupal, which so far seems elegant and well designed. We'll see how long that lasts. :)

Posted By: idealpragmatist on August 3 2006 02:19 am
Tikiwiki is a very powerful, feature filled wiki based cms, however it will take a while to learn. Tikiwiki 1.9.4 is great for supporting group deliberation in a wiki, it is faily easy to create private group pages and permissions are fully customizable.

Posted By: Marc Laporte on July 11 2006 05:57 am
To Bob, I wish I would read constructive criticism in this forum, something we can realistically accomplish and measure. So here is my constructive criticism to you on how to approach an open source and free project. 'poorly organized admin panel': Yes, I agree the admin panel can be confusing for new users. Can you suggest something specific? Like you should take a look at system X. You should have fewer settings per page, etc 'laughable manuals' : Do you have the slightest idea how many hours countless people donated? Again, please be specific. ex.: The documentation is not up to date. It is missing such or such key feature, etc 350 page manuals laughable? http://sourceforge.net/project/showfiles.php?group_id=64258&package_id=68737 'hosting on a private server with shitty link' Tiki has grown exponentially. The main tikiwiki.org site has over 10 000 Registered users. We have been splitting everything on different sites to improve performance. I wish I would hear people rather say: 'If I end up choosing Tiki as my main CMS, I will offer some professional hosting or I will sponsor it.' 'Not to mention that barely anyone of 20-30 people would respond to my clear and precise questions ond irc channel.' Are you it was clear for others? Did you post to the forums? What time did you come? How long did you stay? Did you ask politely? 'if there's ever a complete rewrite' Do you have any idea how much work a 'complete rewrite' entails? Would you participate? I wish you luck in your quest for the ideal system. The best way to make this a reality is to participate. Best regards, M ;-) Marc Laporte Project admin Tiki CMS/Groupware

Posted By: Bob on June 8 2006 03:37 am
TW has a shitload of features out-of-the box, and beats down any competition on that matter. Yet again, it's tedious to setup because of poorly organized admin panel, not to mention laughable manuals and complete lack of (community) support, and hosting on a private server with shitty link. I like many of the concepts implemented, like _full_ multilinguality (not just localization), blend of all features seen on different cms-es, permission-setting system and many more... However, code is full of junk, (default) styles are the crappiest CSS-es I've ever seen, and are big pain to edit and customize (has one style for diff. things, and several styles for one same thing), some features are buggy, some are just plain ugly and inferior (e.g. forum). I've had to debug and change some pieces of code on my first install, and what a great mish-mash of different coding styles it was! Not to mention that barely anyone of 20-30 people would respond to my clear and precise questions ond irc channel. But like I said, after trying 1.9.2-1.9.3, if there's ever a complete rewrite, which would stick to same concepts but this time with clean, consistent and unclogged code and neat, well-organized styles, I'd be the first to use it in production. See you in v.2.0!!

Posted By: Dazza on March 15 2006 04:04 am
I've been trying to set up Tikiwiki for a while and although TikiWiki has some great features its a very frustrating package to setup. Options and settings are almost hidden. Silly things like case sensitive usernames, and impossible group access rights make it very awkward for many users. Its good and easy to add content once going and you get the hang of its wierd ways, but allow a few weeks and many headaches to set it up. Support is next to zero, if and when their site is running, documents are a bit of a joke! (A big Joke!)

Posted By: Damian Parker on January 16 2006 06:46 am
If your running a TW, make sure its the latest 1.9.2 release, there are some security implications with all older releases. 1.8.x should be upgraded to 1.9.2 at warp speed to be protected. Upgrade details can be found on the UpgradeTo19 page on tikiwiki.org

Posted By: Rohit on December 3 2005 04:09 am
I have installed Wiki days a few days back. If you want it to just work out of the box then that is certainly an impossible expectation. It can take 2-3 days, to get a hang of it, especially if you are new to CMS. The documentation is quite incomplete, and sometimes you may get frustrated by setting a few things up. There is not much of the support possible on IRC . Forums I have yet to try. However inspite of all the user unfriendliness , it is an

Posted By: helpmaster on September 17 2005 02:08 am
Masterpiece of all kind of encyclopaedias. It features advanced inter structure linking, very easy to navigate and to find relevant information.

Posted By: Eric Baenen on September 15 2005 08:38 am
I have set up something like 30 production TikiWiki sites over the past year - most for intranet project collaboration sites, one for a local community site and two (one public, one private) for my family site. TikiWiki is by far the most comprehensive and powerful CMS/Groupware/Collaboration suite I have investigated - and I did pilots with many. It is also one of very few that integrates well with LDAP for authentication - and the use of the Wiki concept throughout makes content development trivial. The design is admittedly database query intensive so you should run it on a decent machine and it does take a little getting use to -- it is so feature rich it can be a little overwhelming - but it is worth it. Once you get the hang of it, you can set up a new funcational TikiWiki site in under 30 minutes - that's with features fully configured. I highly recommend TikiWiki for any groupware, collaboration, or CMS needs.

Posted By: Emo on June 10 2005 12:32 pm
TW looks good and offer many fetures. But it's very slow. I installed TW 1.8.5 on dual PII@350MHz. There is no content in it yet, but one page takes more than 2secs! For compare on same mashine I tested my 'company catalogue' in php which contains hundres thousands companies. Pages which shows this companies by categories, areas etc. are done in less than 0.2secs. It also have many queries (for show category tree, rotating banners etc.). I didn't inspect src of TW, but I bet it has bad BD architecture. I'll give TW chance again in 1.10.

Posted By: ovidio on May 17 2005 04:05 am
Well !! TK might seem rather complicated, but once you got it it's quite simple. Although it doesn't have an extraordinary graphics it's very powerful. The accent is put here on usability. Oh yes ! You have to dive in it

Posted By: Geof on April 21 2005 10:29 am
We have tried many CMS but TW was the best featured CMS. It is not simple to begin with it in admin mode but in user context it is the best one. The #tikiwiki freenode irc channel is full of nice guys who explain nicely tips. The documentation is very impressive.

Posted By: Matt on March 13 2005 11:20 am
Just installed 1.85 a week ago. Up and running on our Linux server with MySQL. I am not a performance guy, so I can't comment yet about that part of TW. However, I will say that if you need a comprehensive suite of back office tools, this app is really neat. It took me some time to navigate TW and find out how to set things up, but I have it somewhat under control. If you simply need a CMS, there may be simpler options. However, if you need a portal with comms., forums, chat, live support, collaberation tools, it is a good package - perhaps aside from the quality of the coding which I can't yet comment on as I have not reviewed it. TW seems to have a fairly large community as well so I hope this bodes well for its future. Thanks to the contrinutors to TW. I like it!

Posted By: Colorado on February 24 2005 02:43 am
Some comments below are misleading - Tiki has so MANY features that if you enable them all then yes, performance is slow. HOWEVER, if you enable the same features as other CMS systems have, then speed/performance is comparable. The TikiWiki.org site has ALL features enabled so it is slower by comparison. Try Tiki with only the same features enables as other CMS's are linited to, and you won't be disappointed. The developer community for TikiWiki is the BEST!!!

Posted By: Webrunner on February 7 2005 08:55 am
Cluttered with features, unfindable options and like others say.. a nightmare for your server and performance. On a dual PIII with 512 megs of memory it generates a load of 2.42 when i had 20 users browsing the site. Hundreds of queries per page is way too much for me. A definate NO, unless you are expecting only few users with a lot of [atience.

Posted By: Oreb Nightchough on December 19 2004 08:46 am
I was all set to give TW a try but, after I spent 15 minutes trying to find the download, I gave up. There was plenty of information on which release to use and the security update but I never did find the actual download. Figure it's not worth the trouble.

Posted By: Damian Parker on December 19 2004 05:06 am
TikiWiki's forums are overgrown from the comments code, they are much needed to be a rewrite. TikiPro does use both the TikiWiki Forum code and phpBB, however TikiWiki is LGPL and phpBB is GPL so the licenses are not compatible. The

Posted By: Damian Parker on December 19 2004 04:33 am
What is wrong with TikiWiki 1.10? Hasnt PHP just released a 4.3.10 ? LOL TikiWiki 2.0 needs and will be a complete rewrite, I know that for a fact, Im a project admin :)

Posted By: caca on November 8 2004 03:28 am
Does anyone know about the forums in TikiWiki? I have installed it and it has many nice features, but I am not finding very much about changing the forums (BBS) part of this Wiki. It doesnt seem like it has many things that can be changed, like from nested to flat. Also is it based on phpBB? I have seen TikiPro which is an offshoot of TikiWiki and clearly uses phpBB as its forum. Also I havent seen many mods or addons to TikiWiki avaialbe

Posted By: Arnaud HERVE on October 25 2004 05:22 am
After having tried version 1.9, I must say my point of view has changed. Tiki is still one of the richest cms around, and still easy to install too, but the administration and user interface have become clearer, I don't notice bugs despite the many many features. There are promising display options, like the header logo choice (footer to come), and very professionnal plans for internationalization. Learning the system can take time, but not more than for other cms. Very satisfying product, talented community. Such a pity their website is so clogged.

Posted By: Arnaud HERVE on October 23 2004 03:12 am
Tiki is certainly one of the richest cms around. Easy to install too. Yet many inconsistencies provoke some apprehension in me: The UI is unbelievably clogged, next version will be called 1.10 (from 1.9) instead of 2.0, and overall there seems to be many bold development underway whereas some basic functions seem not fully optimized or bug free. Very strange animal. Baroque is the word.

Posted By: michael on October 14 2004 03:50 am
Take one look at the code for this thing and you won't want to touch it with a ten foot pole. It is overly slow, mainly I think due to poorly written SQL (and bad architecture in general). A single page view uses *hundreds* of db queries to display. Just go to tikiwiki.org and look at the bottom of any page if you don't believe it. And the feature set is out of control -- so many overlapping features.

Posted By: Brandon on October 12 2004 08:26 am
Tiki seems to be a powerful general application, but the message board forums are really poor and it doesnt seem to have hardly any modifications or a vibrant developer community. Its also SLOW as hell from what I can tell... seems like code bloat galore, perhaps they need a rebuild of the database and queries because this one cant keep up with the demands of a largescale deploy.

Posted By: WallStArb on October 11 2004 07:47 am
Does anyone know about the forums in TikiWiki? I have installed it and it has many nice features, but I am not finding very much about changing the forums (BBS) part of this Wiki. It doesnt seem like it has many things that can be changed, like from nested to flat. Also is it based on phpBB? I have seen TikiPro which is an offshoot of TikiWiki and clearly uses phpBB as its forum. Also I havent seen many mods or addons to TikiWiki avaialbe, and the lack of customized modules seems to be a definite disadvantage.

Posted By: JoetheIntro on October 6 2004 06:33 am
Would anyone prefer this CMS over others. It seems like it has a lot of features, but is it a jack all trades but a master of none!

Posted By: Q on October 5 2004 07:42 am
tiki does NOT install on free.fr....