Endangered features

Antoine de Saint Exupéry wrote:
perfection is finally attained not when there is no longer anything to add, but when there is no longer anything to take away

In almost each version of Tiki, some lesser used/maintained features are generally removed.

Looking in the future:

Features that are more or less unmaintained, or that the improvement of other features are making them redundant.

The goal is not to remove features. The goal is to have great functionality while keeping a maintainable code base. We must also keep in pace with the evolution of the web.

Sometimes, features evolve to a point where one makes the others one redundant. Migrating data in this context is always a big concern.

There is also a discussion about how to reduce disk space.

Dead services or sites

(Site deaths are when sites go offline, taking their content and permalinks with them, and breaking the web accordingly - http://indiewebcamp.com/site-deaths.)

Decided to be removed

Just need person to do it and a migration path

    • "The idea is to make the image galleries redundant, then obsolete, then nonexistant."

      Following the 2014-11-06 BBB meeting, Jyhem did a search of everything Image Galleries offer which is not in File Galleries.
      That was done on Tiki12, after checking that Image galleries are not broken in Tiki13. They are not, except the default display looks horribly old, which power users easily overcome with a custom tpl.

      • On the general images gallery configuration, configurations File galleries don't have:
        • Rankings:
        • Comments:
        • Uses Slideshow:

        • Uploaded image names must match regex:
        • Uploaded image names cannot match regex:

      • Display image information in a mouseover box:
        • No
        • Yes
        • yes, and don't display that information under the image

      • Use default max rows, images per row, thumbnails size and scale size for all galleries (set values below)
        • Max Rows per page: Default: 10
        • Images per row: Default: 6
        • Thumbnails size X: Pixels Default: 80
        • Thumbnails size Y: Pixels Default: 80
        • Default scale size:

      • Default number of comments per page:
      • Comments default ordering

      When creating a gallery, configurations File galleries don't have:

      • Max Rows per page: Default: 10
      • Images per row: Default: 6
      • Thumbnails size X: Default: 80
      • Thumbnails size Y: Default: 80

      • Fields to show during browsing the gallery:
        • XY-Size
        • Filesize
        • Gallery Image (the image used as folder image for the gallery): First image/first uploaded image/random/last image/last uploaded image
        • Available scales: ???
        • Add scaled images with bounding box of square size: ???

      • When uploading a file, what does not exist in file galleries
        • Thumbnail (optional, overrides automatic thumbnail generation):
      • Viewing image: previous/next buttons
      • images can be moved from image gal to another image gal

      • Viewing gallery:
        • Rebuild Thumbnails

      • Edit image: images can be moved from image gal to another image gal

      • I thought there was some feature allowing to turn images but I could not find it (maybe it existed in Tiki 3 and was already lost, or it's a hard to find feature, or it depends on imagemagick being installed)
    • Not sure how feasible a fully automatic and safe migration script is but it has been deprecated for several versions now and i think all efforts should be focused on making fgals better
      • Beginning of a migrations script has been committed to devtools in r61916 — Robert has a script that he used for manual migration--

  • Wiki 3D: Morcego 3D network browser is a java applet which was the best way to do this in 2004. removed by Nelson for tiki 15
    Now, it's time to replace with an HTML5 solution.
  • Allow HTML in Menus (prefs menus_item_names_raw_teaser and menus_item_names_raw) done for 15.x Jonny Bradley
    Was a bad feature and silly double prefs, and not needed as wiki syntax can be used in menu labels instead.

Candidates for removals for Tiki 20

  • PluginChartJS duplicates Plot.ly, doesn't use PluginList and doesn't work with mPDF. And developer no longer active. Marc Laporte
  • Addons
    • And do more in profiles, themes and _custom php directory, and add an API
  • feature_invoice. I haven't used it but it links to (Mod-tinvoice), which says its dead code and should not be used. If the documentation is wrong then let's update that and remove from this list. Otherwise, it seems to be a good candidate for code that was never finished. drsassafras

Candidates for removals for Tiki 19

Post-LTS is a good time for a clean-up

  • PluginDBreport: unmaintained, developer long gone, can (all?) be done with PluginList or PluginTrackerList
  • Tiki's "powered by" icons (https://doc.tiki.org/module-poweredby) are visually retro/unreadable and informationally trivial (is it really important to say Tiki runs on PHP or uses Smarty templates?). If this "feature" is continued, maybe the display could be more like the footer area at http://wikisuite.org/Software (larger icons that highlight more significant software), or there could be a "powered by" link in the footer that directs to a page listing/describing Tiki's main libraries, etc.
  • Lucene Unified Index Engine
    Zend Lucene is deprecated and unsupported and our implementation has been broken for many versions.

Candidates for removals for Tiki 17?

  • Integrator: Perhaps can be replaced by PhantomJS and CasperJS? Marc Laporte
    Integrator should NOT be removed. We just had a UseCase, where we quite easily added a Doxygen Repository and a phdoc repository into Tiki16. I will update the docs and if and when available in Tiki I will test PhantomJS and CasperJS Torsten Fabricius
    • I do not see PhantomJS and CasperJS as much implemented in Tiki (is it at all?) and sorted in a way that it could any replace Integrator. Maybe in the log run for Tiki 18 or 19, but then we need testing and documentation first!
      And it works on shared hosting out of the box Torsten Fabricius
  • WebHelp: Perhaps can be replaced by mPDF export? Marc Laporte
    • I don't see how this could be replaced by mPDF when WebHelp generates set of HTML pages and mPDF generates a PDF? luciash d' being
    • It should be something able to export the wiki pages structure (could be just a perspective maybe online and export to static HTML pages for offline use) to have simple layout with ToC on the left (right for RTL) side and wiki page content on the other side... essentially something like https://reasonml.github.io/docs/en/quickstart-javascript.html ( which is generated by MIT licensed Docusaurus btw: https://github.com/facebook/docusaurus ) luciash d' being
  • jCapture: Can you propose an alternative? Marc Laporte
  • Remove PluginJabber Done: PluginJabber was removed. Started in Tiki17 (pop up mode) XMPP and improved in Tiki19 (full page mode) PluginXMPP thanks to ConverseJS.
  • Filesystem Dumps Wiki Dumps

Tiki 17 Talk

  • With no further discussion, no votes against, and a few votes for, I will move feature_iepngfix & wikiLingo to approved removal features soon. drsassafras
  • Is there currently a mPDF feature that can replace whelp? drsassafras
    • Not exactly, but it covers the same general need of having an offline copy of the content. In PDF instead of HTML. Marc Laporte
    • I did not (yet) find a documentation of how to print wiki structures with mPDF. Afaik that should work already, but needs at least basic documentation. If not yet implemented, it would be nice and could then imho replace whelp!? Torsten Fabricius
    • it is not imho only about getting the pages as an offline format. you can have web help / manuals online too luciash d' being
  • jCapture is not working on any modern browser. I don't know of a replacement but it looks really bad having features that cant work on modern browsers integrated into tiki. drsassafras
  • I added filesystem dumps to candidate removal. Its a more buggy than whelp and has similar functionality. drsassafras
    • so pref feature_dump in tiki-admin.php?page=wiki I don't use. I did a quick test. Seems to work. I don't know what should be done. Is anyone using this? Is this the right implementation? Marc Laporte


This should move to own page as cleanup and remove a feature / code is not the same: Cleanup

  • Remove current calendar templates and converge on FullCalendar
  • File gallery HTML interface vs elFinder: can we keep just elFinder? Marc Laporte
    • nope, -1 from me (elFinder uses obsolete jQuery-UI which should be replaced by Bootstrap imho) and the UI is highly not easy to work with :-( luciash d' being
    • -1 from me as well (Torsten), as in my experience elFinder is only useful at all sometimes and it is (at least for me and most of my users) usually more productive to work with the old legacy screen (especially the list-mode) Torsten Fabricius
    • -1 I don't like that elFinder is so non-native-Tiki in regard to visual appearance and behavior. It's possible to override some of the elFinder CSS but not all, and takes a lot of work and adds CSS bulk. If there was a "functional CSS only" option for the elFinder source, that didn't impose its own design ideas, I'd be much happier. But this is true for a number of libraries. Also I like Tiki's admin/browse/page view options. Gary Cunningham-Lee
  • We should get rid of "Use legacy tracker insertion screen" Preference name: tracker_legacy_insert but new interface requires a few improvements (ex.: full page view)
    • We should not. I would hate to see that go and rely on the modals dialog only way (which is much more buggy, sorry). It is imho so much quicker to switch to the Edit tab than waiting to load the edit dialog and have no reference of what I have on the view tab when I need to quickly check how it shows up or want to react the comments luciash d' being
    • -1 from me as well (Torsten), as the legacy tracker insertion screen saves my live or keeps me productive ever so often. We are starting to use Trackers for conference booking now (after recent registration and paper management) and we need a reliable fall-back. Torsten Fabricius
    • -1 I find the legacy (tabbed) insertion screen faster to use and appreciate being able to switch back and forth between tabs in some cases. The larger size for the form is also useful sometimes. Gary Cunningham-Lee
  • Delete the various obsolete mods from http://svn.code.sf.net/p/tikiwiki/code/mods/trunk/
  • Merge tiki-admin.php?page=gmap into tiki-admin.php?page=maps done
  • https://sourceforge.net/p/tikiwiki/code/HEAD/tree/trunk/templates/plugins/plugin-topfriends.tpl should be at the same place as other plugin templates Was removed because it was broken, and not a good implementation
    • is it still removed and not working, or is it back, then it should indeed be in the logical right place Torsten Fabricius
  • Move inline plugins from a pref to a param
  • fix typos in code:
    • attachements -> attachments
    • and dependancy -> dependency
  • Merge tiki-admin_security.php into tiki-admin.php?page=security
  • smarty_function_trackerheader was really made redundant after the Tracker revamp. 2 uses remain (which do nothing) so should be removed for Tiki15
    • is that done in the meantime? We are at Tiki 18 now. Torsten Fabricius


  • Feature home page (home_blog, etc.) and corresponding code in menu manager
  • Live Support

Move out of mods into main code base

Perhaps distribute via Composer or Profiles?
Small things like PluginPerm should be in main code base done

  • Review all mods and decide what should be added to BRANCH-1-10 Tiki5
  • PluginR (Xavi) Done by Jean-Marc Libs
  • A solution should be found for themes
    • I find it appropriate when theme files/folders have to be uploaded to the server directly - this is organised so easily - simple copy/paste
      Theme setting/preferences that correspond to the theme files or additional Theme related content can be added by using Profiles, where the Theme provider shall make sure, that applying the themes profile would not brake existing websites.
      Theme files/folder from providers websites and the Tiki Themes Marketplace could be linked with the Tiki Profile website (or the providers profile).
      Theme providers should be encouraged to license their work in a way, that files and profiles can be republished on tiki.org in case the providers site(s) fade away
      Torsten Fabricius


Future not looking bright

  • Zend Search Lucene was never released in 2.0 and it looks like it never will. As Tiki prepares to move to Zend Framework 3.x, unless there is a new release, I think we should remove at the latest after Tiki 18.x LTS and focus on Elasticseach and MySQL/MariaDB. It is super easy to install Elasticsearch as per: http://wikisuite.org/How-to-install-Elasticsearch-on-ClearOS Cost on Linode is USD$20 per month for 4 gigs of RAM, and there are multiple hosted Elasticsearch options. Marc Laporte
    • TNTSearch could be an interesting alternative, but in this case, we should revamp search handling to offer an abstraction layer to TNTSearch, Elasticsearch, MySQL Full-Text Search, and any others in the future.


  • What is status / future with Jison Parser, given wikiLingo
    • Should be removed before Tiki 16.x imho - no longer maintained as was never finished Jonny Bradley
  • Should we remove direct link with Mapserver and replace with an abstraction layer? -> Maps
    • Yes, started in Tiki7
    • Removed for Tiki 15
  • Can/Should we merge PluginFlash and PluginMediaPlayer?
  • PCLZip: still needed?
  • Should Smarty Debug replace Debugger Console?
    • No, they offer different functionality
  • Should article submissions be removed and data merged, now that we have published/unpublished status?

* Since we are no longer support IE6, should we get rid of feature_iepngfix ? was removed

Candidates for renaming

  • Minichat -> Chat
  • Freetags -> Tags? (done by chibaguy for Tiki 14, thanks)
  • cms (which is a legacy system name) -> articles
  • Any feature or module that includes "new" -> something more descriptive
    • modules/mod-func-calendar_new.php

Superceded (or could be with some work!)

Short term

Proposal to deprecate the following items in 5.x and fully remove in 6.0:

  • Admin: Site Ad — migrate to banners
    • Shouldn't this be a module?
  • Clean up old/replaced modules

Medium term

Long term

To merge

Idea to merge

Maybe too much work

Blog and Articles Articles in a workspace could be like current blogs

Already removed

Update 2015 for Tiki 15

  • JS Calendar -> jQuery
    • Half done - need to handle time before we can totally remove it.
    • LP did it last week Jonny Bradley
  • Custom Home (totally pointless?) Jonny Bradley
  • XAJAX last update 2008-08 What should be our strategy?
  • All used code is gone, but some comments should be cleaned up for Tiki 11 Jonny Bradley
  • remove Babel Fish link module (doesn't work) and just keep the logo one (which works), thus delete feature_babelfish_links and module babelfish_links because 1-broken 2-unmaintained 3-uglier than babelfish_logo 4- less languages than babelfish_logo Jonny Bradley



The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

Accessibility (WAI & 508)
Articles & Submissions
BigBlueButton audio/video/chat/screensharing
Browser Compatibility
Communication Center
Contacts Address book
Contact us
Content template
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Debugger Console
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Dynamic Content
Dynamic Variable
External Authentication
Featured links
Feeds (RSS)
File Gallery
Friendship Network (Community)
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Inter-User Messages
Kaltura video management
Live Support
Logs (system & action)
Lost edit protection
Meta Tag
Missing features
Visual Mapping
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Performance Speed / Load / Compression / Cache
Revision Approval
Search engine optimization (SEO)
Semantic links
Shopping Cart
Site Identity
Smarty Template
Social Networking
Spam protection (Anti-bot CATPCHA)
Staging and Approval
Syntax Highlighter (Codemirror)
Tell a Friend, alert + Social Bookmarking
Terms and Conditions
Token Access
Toolbar (Quicktags)
User Administration
User Files
User Menu
Webmail and Groupmail
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives

Useful Tools