Table of contents | |
Who worked on this? | |
Nelson Ko acted as release manager and Louis-Philippe Huberdeau handled the packaging. |
Alphabetical list of contributors | |
|
What's new in 2.0? | |
Or you can read the general overview of new features:
|
1.9.x to 2.0 migration tips | |
|
Read the installer instructions carefully to know which script to run | |
The tiki_1.8to1.9.sql will bring your database up to the latest version of the 1.9 series and then the tiki_1.9to2.0.sql script will bring you from the 1.9 database to the 2.0 database schema. |
PHP memory requirements | |
|
Category Permissions | |
A database administrator can consider using the information in Category Perms MySQL queries to facilitate an 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 | |
|
Customized templates | |
|
Security | |
|
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. |