Tiki 5.0 Release Notes
This document includes important information about Tiki 5.0. Please review this information when installing (or upgrading to) this release.
For Tiki support, please use the forums.
Quick links: Changelog | Tiki5 (doc) | Tiki5 (dev) | Upgrade | Roadmap
Table of contents
Introduction to upgraders from earlier versions
If you are migrating to Tiki5 from Tiki versions earlier than Tiki4, you are encouraged to read first the pages describing the changes introduced in earlier versions of Tiki, such as:
as well as the page linking to the resources related with Upgrades
If this is your first installation ever of Tiki, welcome to Tiki Community! You'll find details about the installation here:
If you are planning to Upgrade from a Tiki version earlier than Tiki5.1, or you have never fixed the potential encoding issue in your database, please follow these 3 steps once:
http://doc.tiki.org/Upgrade#Fix_the_encoding_issue
New features
Tiki 5 includes several new features (including shopping cart, workspaces, and perspectives) as well as hundreds of fixes and enhancements. Refer to http://doc.tiki.org/Tiki5 for complete documentation on TIki 5 release.
Branding and Name Change
Refer to http://branding.tiki.org for complete information.
Category Permissions
Category permissions have been dramatically revamped and improved since version 3. When upgrading to version 5.0 from version 3.x (or earlier), your permissions may not migrate properly. You should review the category permissions and reconfigure them, if necessary.
Refer to http://doc.tiki.org/permission for complete information on Tiki permissions.
Known Issues
Installation Fails on PHP 5.3.0
When installing Tiki5 on PHP 5.3.0, installation may fail with the following message:
Fatal error: Undefined class constant 'MYSQL_ATTR_INIT_COMMAND'
This is due to a known bug with PHP 5.3.0. To install Tiki5, use PHP 5.2 or 5.3.1 instead.
Can't connect to the database
Same as ReleaseNotes40, because PDO is not detected, add the following statement to the end of your ../db/local.php file, before the ?>:
$api_tiki='adodb';
Loss of Admin Privileges
When upgrading to version 4 or above a Tiki site started on a Tiki version older than 3, you may experience Permission Denied messages for some features, even when logged in as the administrator (Admin) user. If your Admin account has lost permissions, you can easily recover them.
- After completing the upgrade, re-run the Tiki installer (tiki-install.php).
- Go directly to Step 7. Configure the General Settings.
- At the bottom of the page, in the Upgrade Fix area, enter the name of your administrator account. The default name is admin.
- Click Continue.
Tiki will:
- Create a new Admins user group.
- Grant tiki_p_admin to the group, if missing
- Add the specified administrator account to the group.
Database Encoding Issues
In some instances, after upgrading to Tiki 5 your wiki pages may show odd characters or demonstrate other encoding issues. To resolve this problem, edit your ../db/local.php file by commenting out the $client_charset line as follows:
// $client_charset='latin1';
Corrupted file uploads
In some server configurations, even if you do not experience strange character display, you may corrupt the file you upload in the database. If you have file uploaded in the database (in file gallery, tracker, wiki...) check that a new uploaded file can be downloaded with no problem.
It is a problem do the same thing than above: comment _$client_charset__ line in db/local.php. It will not affect file already uploaded.
A better and definitive solution for most (if not all) configuration setups is upgrading to the latest version 5.x, and esure that you have run once the three steps indicated in the documentation about upgrading:
http://doc.tiki.org/Upgrade#Fix_the_encoding_issue
An alternative option might be to keep the potential problem (related to encoding character sets) that you might have in your database, and change the settings in your Tiki so that files uploaded (file galleries, image galleries, attachments, etc.) do upload to file system instead of to the database. Applying the proper fix explained above is the suggested option, of course.
Installer
Installer throws up an ugly error message if you enter invalid DB connection info. (instead of asking you to try again)
Will be fixed in 5.1