Tiki 8.1 was released on November 11th, 2011

http://info.tiki.org/article182-Tiki-8-1-Now-Available-End-of-Life-for-Tiki-7-x

For Release notes, see: http://tiki.org/ReleaseNotes8.1#Known_Issues (especially if you are upgrading by copying over all files)

For dev-related notes, please see dev:Tiki8.

(alphabetically sorted)

As the FLOSS Web Application with the most built-in features, a historical challenge with Tiki has been the learning curve associated with having so many preferences (features, settings, options). People tend to want all the features they use but without the overhead of all the features they don't use. Since Tiki covers so many Use Cases and since it's a community-managed projects, it's not feasible to reduce the overall number of features (imagine the endless debates). Paraphrasing Clay Shirky, the solvable problem is not feature overload, it's better filters.

A few versions ago, a preference search engine (used to find features in the admin panel) has made people very happy. Taking this a step further, preferences can now be tagged as basic, advanced, new and experimental, and this permits the admin to filter.

By using the "basic" filter, new admins will see only a small portion of preferences, but the most commonly used one. This will ease the learning curve.

See "Admin Home" for details.

On the Admin: Wiki page, you can use the Move images from wiki_up to the home file gallery button to move all of the files in your img/wiki_up/ directory to the default (home) File Galley.

Tiki updates all wiki pages with {img fileId} syntax (where fileId is the ID of the file in the File Gallery) and deletes each file from the img/wiki_up/ directory.

Note: You should backup your database (or file directory) of your File Gallery and the contents of the img/wiki_up/ directory before using this feature.

See "Wiki Features Tab" for details.

• Updated to support 0.5 version of XML

Connect allows you to communicate what you think about Tiki's features back to the community. (see Jonny or Marc for questions)

See Connect for details.

Added support for version 0.8, including Record/Playback. The Wiki plugin has a new argument to enable recording of the rooms. When made available by BigBlueButton after the meeting, the recordings will be listed below the plugin.

A new AJAX comments interface has been deployed, allowing for lighter page loads and faster moderation.

The new comment interface is also used for tracker comments, which are no longer an independent feature.

Akismet Spam protection is now available for comments.
http://akismet.com/

Daily reports was extended to cover calendar and tracker items, as well as their comments. Moreover, default text from the reports of the message can be currently sent in user language if it that text has been translated in the corresponding language.php file.

Allows to upload a file in file galleries through a URL instead of uploading it from disk. Tiki will pull the file and attach the source as a property on the file. The file can be refreshed periodically from the source. Archives will be created as required.

Cache-control headers are respected to avoid excessive work on the remote host.

"WebODF is a JavaScript library that makes it easy to add Open Document Format (ODF) support to your website and to your mobile or desktop application. It uses HTML and CSS to display ODF documents."
http://webodf.org/

WebODF has been added to Tiki8 as a new feature, called Tiki Docs

Please see: Docs.

Introduced in Tiki7, Draw is much improved in Tiki8. It can be full page or page-sized.

SCORM is a package format for Learning Management Systems. Initial handling of those packages was included, namely the creation of a tracker item based on the meta-data stored in the file to allow for package management. More improvements are expected in the future.

See SCORM tab for details.

Several fixes have been done to the handling of non-English characters in wiki pages (and in the editor in general).

Tiki 8 now features a 100% complete translation to German, thanks to the work of Gregor Adamczyk and others from Tiki's German community.

• Added support for Google Street View

Refactoring which provide various benefits

• Put most used permissions at the top
• Global-only permissions no longer listed when assigning permissions to categories
• Object permissions now include related permissions like comments, modify categories and other permissions that could only be set globally in previous versions

There is a new permission to allow switching between wiki and WYSIWYG modes while editing (tiki_p_edit_switch_mode)

It is to prevent non-tecchie users to switch between the editors and get mixed or unfinished markup in pages if they don't know what they are doing, since the conversion is not perfect.

You can find this permission under "permissions > tiki" (the very last perm in 8.x)

See PluginCustomSearch

It creates jQuery-UI dialogs in wiki syntax.
See PluginDialog

Permits to embed a drawing in a wiki page. Tiki Draw is the integration of SVG-edit starting in Tiki7.

See PluginDraw

This plugin is very similar to both PluginTabs and PluginCarousel in what it does to content, the main difference is both the user interface and what it can display. PluginSlider can handle wiki syntax within itself, it can display text, images, video, flash, basically anything...

See PluginSlider

It displays a timeline

See PluginTimeline

Tracker fields can be enabled/disabled by a tiki site admin. Therefore, new preferences are available to indicate such preference. Some of them are disabled by default, and if you were using them in your profile objects, then you need to define them as new preferences enabled.

Example to be added just below "feature_trackers: y":

trackerfield_file: y
 trackerfield_files: y
 trackerfield_dropdownother: y

Tiki now emits internal events that customizers can hook on to attach special behaviors instead of modifying the code directly. Events are currenltly available in at least wiki pages and tracker items. See blogpost20.

The very first version of Tiki (October 2002) was using Smarty v2.2. Tiki 7 used a newer Smarty version, but is still using Smarty 2.

In November 2011, Tiki8 was released with Smarty 3.

Smarty is a fundamental part of Tiki and in Tiki7, there are over 800 template files using the Smarty format. An upgrade of a software project integrated for over 8 years and covering hundreds of files: this is not to be taken lightly!

Special thanks to Stéphane Casset who led the upgrade and to all the community members that helped out with testing and debugging.

And of course, a big thank you to Monte Ohrt, Uwe Tews and the Smarty community.

Among the benefits, administrators entering Smarty code in user modules or pretty trackers will be able to do the changes without fear. Syntax errors will be caught gracefully and reported.

Please note that Smarty 3 is not fully backward compatible with Smarty 2, so if you are upgrading from a previous Tiki version and you have custom template files you might have to update them manually. Check the list of Smarty 3 known incompatibilities with Smarty 2.

Tiki now provides a series of web services for various components. The JSON services are used internally to handle the AJAX requests, but can also be called externally. Check out the various controllers under lib/core/Services/.

960_16_col.css
http://960.gs/

Include the external token as a class on external links

Tiki now stores the last exact URL of each URL and allow to click in tiki-referer_stats.php to open the URL in a new page.

Before you was able to see :
www.tikiwiki.org 12134 15h25

Now you can click on www.tikiwiki.org and go to the exact last URL inside the site, for example http://www.tikiwiki.org/tiki-index_raw.php?page=foo.

This feature, allows to retrieve the location of your site in the referer, to read the comment about your site in a forum, page etc ...

See Referer Stats for details.

This is done respecting HTTP Accept headers
http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki?view=revision&revision=35006

• PluginCustomSearch

Small adjustments were made to the indexing to better cover the data.

• Relations are now indexed, which allows to filter based on data in the new tracker relations field, semantic links, user favorites
• When using the files tracker field type, the content of the attached files are indexed with the tracker item
• Tracker fields are now indexed differently based on the field type
• Forum posts and replies are now indexed independently
• Comment count is indexed with the object

Results for the same query are cached internally until the index is modified, speeding up frequent requests and pagination.

The total amount of results is now limited to a configured value. The full amount of results is provided as an estimate, refined search is required to access all results.

The Staging and Approval feature was removed from the codebase after being replaced by Revision approval, Flagged Revisions in the previous version. Users of staging and approval should approve or reject all of the content before upgrading and set-up flagged revision approval after upgrade. If not done before the upgrade, the staging pages will be left as-is to be handled manually.

In addition to specifying the HTTP proxy host and port, the proxy username and password can now be specified in the configuration.

The administrator of a site can now specify credentials to use when accessing a remote HTTP source. This allows for any file access on a given domain to be provided with credentials. For example, fetching files from a URL in file galleries and RSS feeds benefit from this feature.

The configurations are accessible from Admin DSN.

Previous problems with file loading under IIS are resolved (when the URL Rewrite module is not installed). The SEFURL should now work OK on IIS. The SEFURL panel now also warns if the web.config file is outdated.

Tiki now offers as an experimental option to install in InnoDB tables, rather than MyISAM tables. InnoDB uses row level locking which may improve performance for some sites. It is also "crash proof". With InnoDB, manual fixing of tables should be a thing of the past. This implementation does not yet use the full power of InnoDB (foreign keys and transactions).

Check the performance admin panel

• System Configuration

• All tables are low adapted to deal with IPv6

Allows to clone a tracker from an other instance and replicate the data. Locally added items can be pushed to the source and the data can be reloaded on demand.

For more information, see Tracker Synchronization.

The administration for tracker fields was completely rewritten to improve user experience.

New features include:

• Drag & Drop sorting of fields
• Some properties are editable directly from the list
• Dialog to add new fields with automatic list refreshing
• Editing field options is done via separate fields, providing for hints and value selectors when available.

Moreover, tracker fields can now be enabled/disabled by a tiki site admin. Therefore, new preferences are available to indicate such choice through the Tracker Admin panel.

Some of the tracker fields are disabled by default, and if you were using them in your profile objects, then you need to define their corresponding preferences to have them enabled in order to upgrade your profiles to work with Tiki 8.

For more information, see the section Profiles in this page.

Complete redesign of the interface to organize the options in a logical way.

New tracker field allowing to upload files into file galleries and to attach them to the tracker item. The content of the attached files will be indexed along with the tracker item in the Search and List from Unified Index.

The new field type makes extensive use of HTML5 to allow multiple file upload through the browse controls or through drag & drop. Upload progress is also provided for each file as they are sent.

New field type to link with other objects in tiki using a qualifier. Those relations are being indexed in unified search and also accessible through PluginRelations.

See Relations Tracker Field

New field type allowing users to select multiple values out of a selected set of options, similar to dropdown.

The handling of tracker permissions was altered to provide more predictable results. The permissions and configrations remain the same, but the interpretation order may now be slightly altered.

Additionally, tracker items will also obtain permissions from categories assigned to them. The complete check order for item permissions looks like this:

1. Ownership related permissions
2. Item permissions coming from categories
3. Tracker permissions assigned on the tracker itself
4. Tracker permissions assigned to the tracker's categories
5. Global permissions

Following these, per-field rules are also checked, based on the visibility, visible by and editable by configurations. The following principles apply:

• You can't view a field unless you can view the item
• You can't edit a field unless you can edit the item
• You can't edit a field unless you can view the field

Dropdown, Multiselect, Dropdown with other and radiobuttons now allow to define a label other than the value.

Example: 1=1 - Low priority,2,3,3,4,5=5 - High priority
Tiki will store the numeric values only, labels will only appear in the input field or when rendering the value.

Because the 3 is duplicate, it will be selected by default (not a new feature).

See: tiki-tracker_reports.php

For more information, see Tracker Reports.

Allow users to mark their favorite objects

Besides reading the general Upgrade notes, keep in mind also that Tiki7 introduced several major changes from prior versions. If you are upgrading from an earlier version, you are encouraged to read first the pages describing the changes introduced in earlier versions of Tiki, such as:

• Tiki7, especially http://doc.tiki.org/Tiki7#Upgrade_notes
• Tiki6
• Tiki5
• Tiki4
• Tiki3

If you were using trackers in your Tiki configuration profiles, beware of the changes in the tracker fields. See the section Profiles earlier in this page.

Remember these steps if you are upgrading from a previous version up to 8.

1. Read the general Upgrade notes, if you haven't done so in the last few years.
2. Remember to run setup.sh again (if you have console access).
3. Beware of changes in modules and their management:
   http://dev.tiki.org/Modules+Revamp
4. Check these two pages for notes specific on upgrading your theme style:
   • https://themes.tiki.org/Upgrading
   • https://themes.tiki.org/Theme+header+modules
   
   Keep in mind that your Custom site header might be gone, in which case you'll need to manually re-do it using module management.
   
   In other cases, custom top bar code or other custom sections you had coded in Admin Home > Look & Feel > General Layout Options might be misplaced. If so, go to Admin > Modules and set the proper order of the modules (see Theme Header Modules for more information on the proper order for header modules).
5. You might need to re-approve some of your plugin calls.
   Go to http://example.org/tiki-plugins.php as admin and approve them all (after revision, if needed, as always)

49 pages link to Tiki8

• Items List and Item Link Tracker Fields
• Smarty Templates
• Documentation
• InnoDB
• Areas
• jQuery
• Tiki8
• Tiki9
• System Configuration
• PluginCustomSearch
• PluginTimeline
• PluginCarousel
• OpenStreetMap,fr
• Protection contre le Spam
• Spam Protection
• PluginComment
• Relations Tracker Field
• PluginGalleriffic
• Maps General information
• Files Tracker Field
• PluginList advanced output control block
• PluginFont
• PluginFavorite
• PluginCode
• PluginDialog
• FullCalendar
• Numeric Tracker Field
• PluginRelations
• PluginDraw
• Banning
• Insérer des images
• 설명서
• 사용자 트래커
• 文档
• Dokumentation
• 시스템 구성
• 스팸 방지
• 빅블루버튼 (BigBlueButton)
• Code 플러그인
• 요구 사항
• PluginPerspective
• PluginVotings
• Daily Reports
• 트래커 동기화
• 티키9
• Docs
• WebDAV access to Wiki Pages
• Connect
• AddFreetag 플러그인

Tiki8.0 | TikiWiki8 | TikiWiki8.0 | TikiWiki 8.0 | TikiWiki 8