Major Features Missing In TikiWiki

on 05 Dec. 07 18:15 UTC, by dthacker

Task Juggler is a flat file based project management system that currently has a QT interface in KDE. Would it be candidate for a tiki based interface?

dthacker

on 07 Dec. 07 03:02 UTC, by BillMac

I have found that, if I want to find something on tw.o sites, I should disregard TW's search feature and use Dogpile to look things up. The TW search capability is so weak that it is almost "a missing feature." At the very least, "TermA TermB" searches should be "termA AND termB" not "termA OR termB." The plus/minus markers are fine if you're in the know, but they don't work well either. Using the category/group filters renders a whole different set of answers; not GOOD answers, just different. Without those filters, unauthorized users see parts of pages they are not supposed to see at all. Not a missing feature, a broken feature.

Gosh, I hate to be so negative.

Bill

on 07 Jan. 08 21:28 UTC, by Vranicoff

This page caught my eye while I was looking for something else and I htought I might say something regarding marclaporte's comments about and API and application integration. I have long considered trying to integrate several applications into TikiWiki. One approach is to modify existing application to be included through the "mods" process. The biggest hurdle I see is to replace the existing applications authentication with the Tiki authentication creating a single sign on for use of the integrated application. This problem and the need to have access to the authorizations structure once authenticated or even to understand Tiki state requires a well defined API or at least documentation of what variables and functions are used to achieve these tasks and how they are used. Also of great use would be a definition of baseline CSS selectors to assist bringing the application look and feel in line to the Tiki once integrated.

Example applications:
*Outreach Project Tool (OPT)
*OSCommerce
*WebCalendar (I do realize Tiki already has calendaring)

on 03 Feb. 08 21:18 UTC, by marclaporte

Hi Vranicoff,

Thanks for your message.

About Single Sign On / shared user base: TikiWiki supports about 10 external authentication services (LDAP, Active Directory, PAM, Auth, HTTP, CAS, IMAP, Shibboleth, OpenID, etc) so the simplest is that the other application supports one of these and just use that.

Tiki also has InterTiki which permits sharing credentials (groups, user settings, etc) amongst TikiWiki powered sites. This could be implemented in the another app. TikiWiki can be either the slave or the master (depending on where you want the master userbase to be)

Look & feel: it could be pretty tricky depending to which point the other app is themeable or not. Since TikiWiki is a CMS, it's designed to be themeable. This may not be the case with genealogy software for example. The shopping carts will be themeable though.

WebCalendar and Outreach Project Tool (OPT) -> IMHO, too much feature overlap to make it worth it. It's less work to add/fix whatever is missing in TikiWiki and/or to create data migration tools than to try to maintain some glueware.

A bridge with OSCommerce or ZenCart would be most welcome! This is a totally different feature-set.

But in any case, do these apps integrate well with any existing CMS/Groupware/frameworks? I mean, is there an example that OSCommerce integrates with Postnuke because of a "well-defined API for building applications on top of, or integrating application". A good example is: CiviCRM has a port for Joomla and another for Drupal. What I want to hear is that "ZenCart" or "OSCommerce" (or something which brings totally new functionality to TikiWiki) has glueware with Drupal/Postnuke/Xoops/Joomla/etc and if we did things differently, we could too.

I am not against the principle. I just want to make sure that any time invested here will be worth it. On the wishlist, we have nearly 300 open or pending feature requests and over 300 open or pending bugs.

Best regards,

M ;-)

Rating	Subject	Priority	Category	Created
(3)	Send direct message via tiki-user_information.php	9 high	Feature request	2009-02
(3)	Tiki trackers for issue tracker / help desk -> customer support requests (requests are private)	8	Documentation (or Advocacy) Feature request	2007-08
(4)	Social Bookmarking any content (ex.: digg this) (add the patch to the main code base)	8	Feature request	2007-12
(2)	Site Map for visitors and search engines (Sitemap Protocol)	8	Feature request	2008-03
(2)	Community/Customer/Constituent Relationship Management system (CRM)	8	Feature request	2008-06
(3)	Shopping Cart / ecommerce / online orders / marketplace / classified ads / rental management	8	Feature request	2008-06
(1)	RFE: admin interface 4 template message emailed to new users to a group (registered, or others)	8	Community projects Feature request	2009-03
(4)	Tiki WikiFarm / Native multi-site / multi-domain handling	7	Feature request	2007-12
(3)	Theme Generator: automated production of a custom css style from a photo / logo	7	Feature request	2008-02
(2)	Make TikiWiki more viral	7	Community projects Feature request	2008-03
(2)	Resource Checkout System and rental pool (to reserve rooms, books, cars, etc).	7	Feature request	2008-05
(4)	Image Manipulation (image cropping, color changing, etc.)	7	Feature request	2008-05
(1)	Interface with SVN (like Trac SVN browser)	7	Community projects Feature request	2008-08
(1)	Add status update and support the open microblogging specification	7	Feature request	2009-01
(2)	Announcements: There should be an easier way for ppl to stay up to date	7	Feature request	2009-06
(1)	Allow Tiki to use virtual currency servers powered by CCLite	7	Feature request	2010-01
(7)	PayPal Shopping Cart Integration	6	Feature request	2006-05
(3)	Social Networking	6	Community projects Feature request	2008-06
(3)	Project Management enhancements (ex.: with Gantt chart))	6	Feature request	2008-06
(1)	Classifieds System / Job board	5	Feature request	2005-06
(2)	Add support for all relevant microformats	5	Feature request	2008-02
(4)	Import/sync from RSS/ical and not just show	5	Feature request	2008-03
(3)	Using desktop mail client (ex.: Thunderbird) to reach Tiki contacts, groups or newsletter	5	Feature request	2008-05
(1)	Timeline viewer	5	Feature request	2008-12
(1)	Email a periodic digest (report) of a tracker activity (new open, and changed to pending or closed)	5	Feature request	2010-01
(3)	TikiBountySystem	4	Community projects Feature request	2005-07
(1)	USB key version of Tiki	4	Community projects Feature request	2007-07
(3)	Support for the Wiki creole markup (syntax)	4	Feature request	2008-05
(0)	Mollom spam filtering	4	Feature request	2009-04
(1)	Managing XML in TikiWiki for re-use by external apps	3	Feature request	2007-11
(3)	Offline TikiWiki: add a way to save/view tikiwiki content offline	3	Feature request	2007-11
(4)	Timesheet with time tracking (stopwatch)	3	Feature request	2008-03
(0)	Better support for external search technologies like Sphinx, Lucene (Solr), Google Site Search, etc.	3	Feature request	2009-08
(2)	Orgchart plugin which works with orgapp	2	Feature request	2006-01
(2)	Integrating fotonotes or wikigraphe or DOM Image Annotation to the Image gallery	2	Feature request	2006-10
(3)	Convert PhpGedView software into a Tiki module	2	Feature request	2007-09
(1)	In / out board	2	Feature request	2008-03
(4)	Bibliography management system (references)	2	Feature request	2008-05
(1)	Password manager	2	Feature request	2009-07
(1)	Flat Files backend instead of DB (maybe ADOdb could do this?)	1 low	Feature request	2008-05

Major Features Missing In TikiWiki

Major features totally missing

Major features missing from main code base, but available with 3rd party mods or workarounds

Incomplete features

Sidebar

Main Menu

Sidebar

To register

Search a Wiki Page

Search Tracker Items Subject

Keywords

Last Changed Items

Last Comments

Last Changed Pages