Branch20Beta

TikiWiki 2.0 is now undergoing beta testing in preparation for release. The current version being tested is RC2. 20Beta2Plan is now up.

Please help in the testing, and file any bugs using the regular bug tracker here (but remember to check "Release20" under Related Project").

What's new in 2.0?

Read Tikiwiki 2.0

Major known issues

The following are major known issues that you should take note of before installing the beta 1 package:

Back up your database and your files before upgrading

• It is not possible to downgrade back to 1.9 after upgrading to 2.0

The installer/upgrade script is still being streamlined.

• Regardless of what it says on the upgrade script, if you are upgrading from the non-latest stable version of 1.9, you may have to run the tiki-1.8to1.9.sql upgrade script before upgrading to 2.0 using the tiki-1.9to2.0.sql script. See bug report
  • The 2.0 installer states this information correctly.

Upgrading from 1.9 requires the use of the install/upgrade script

• The install/upgrade script adds group and category permissions that are necessary to ensure that users can still access the categories they did before.
• Manually running the tiki_1.9to2.0.sql script is not sufficient unless you manually add these new group and category perms to groups. Refer to this

Email notifications may not be preserved

• Email notifications may not be preserved on upgrade so if you need to keep email notifications, do not upgrade until this issue is sorted out. Update (April 10th): Forum e-mail notifications are working again in current svn releases, but notifications from trackers aren't.

Themes are still in the process of being prepared for 2.0

• Themes meant for 1.9 may not work in 2.0. The following may help to workaround but working around defeats the purpose of the beta testing/modifying themes to support 2.0.
• Other than tikineat.css and tikinewt.css, themes may not reflect the full functionality of 2.0. Features may appear to be missing when using other themes.

Other known issues

Refer to Release20 tagged bugs

Perhaps you are asking if you should be using 2.0?

• Yes, on your development (but not production) server, so that you can prepare for an eventual upgrade, to take advantage of the new features available.
• Yes, if you are starting a new site, and you have the technical ability and time to spend to keep upgrading throughout the beta process, and if the site is non-mission critical.
• Yes, if you want to start modifying any custom themes that you are using to support 2.0. But as themes from 1.9 may not work in 2.0, please do this on a development (and not production) site.
• No, not on your current production sites that are running 1.9 unless you have tested it on your development site first and decide that it is OK to upgrade.
• No, if you do not have the technical ability and time to spend to keep upgrading throughout the beta process

How to get the beta package

You can get the latest beta release from Sourceforge, or a nightly tarball, or the latest build of the branch via SVN. Refer to SVN Usage for more information.

You can also test Tiki 2 on a pre-packaged .ISO, either burning a CD with it or running it through Virtual Machine softwares. More information: TikiLiveCD.