History: ReleaseNotes20
Preview of version: 21
TikiWiki 2.0 (previously known as 1.10) was released in August 2008
Table of contents
What's new in 2.0?
1.9.x to 2.0 migration tips
Category Permissions
Category permissions have changed significantly in 1.10. Most notably in order to edit content in categories a user needs tiki_p_edit_categorized. This permission needs to be manually assigned to groups in Category Admin and Groups Management individually.
If you understand the impact of the following Category Perms MySQL queries you may use them to facilitate your upgrade. However note that these queries give users that previously had the ability to view content in categories to edit the content as well. This may not be what you intend. The safe way is to configure permissions manually.
Also if you had upgraded using the Tiki installer then users that previously had the ability to view content that is categorized will continue to have them. If you however upgraded by manually running 1.9to2.0.sql there are some queries here that you may have to run Category Perms MySQL queries.
Trackers
- Descriptions no longer accept html but can be wiki parsed
- Field type: user selector options have changed. You need to reset them according to the new doc. (or maybe just a bug)
Customized templates
- If you customized your templates you should remake them.
- Even with bundled themes you will notice some visual changes
- You may want to change "Preference syntax" in tiki-admin.php?page=general to 1.9.x to use old variable names.
1.10.x to 2.0 migration tips
If you were using 1.10 before (from CVS SVN or Beta) you should look out for:
Security
- Joshua Morin reported several issues
- Jesús Olmos at Internet Security Auditors reported a leak which could be used to disclose path and PHP configuration.
- Special thanks to Philippe Gamache & Damien Seguy for their advice
Edit CSS and Edit Templates
Many users do not realize that these features that provide the ability to edit files that are part of the TikiWiki installation from the web can be a security risk if permission to use these features are given to non-admin users, and that editing of local files on the server is inherently risky. Pending further improvements in version 2.1 and 3.0, changes in this version 2.0 have added input sanitization for many strings that are deemed risky — making it likely that certain content cannot be entered through these features. The workaround is to edit the files on the server directly.