This release contains a number of relatively minor bugfixes (see the Change Log), and it also restores the $Wiki Word Count? functionality from PmWiki 1 in which the wiki administrator can limit the number of conversions for each Wiki Word.
The sample-config.php file has been updated with more comments and suggestions for customizations.
Finally, this release increases the default value of $Max Includes? to 50 (and provides better documentation of the $Max Includes? variable).
These releases fix a number of bugs introduced by the changes in 2.0.beta3. Users of 2.0.beta3 are encouraged to upgrade directly to this release.
This release provides a simple version of the (:attachlist:) markup (different sorting orders are not available yet as the syntax is likely to change), as well as fixes the PmWiki.Edit Quick Reference and PmWiki.Upload Quick Reference pages. It also provides default pages to lock passwords in the Main and PmWiki groups and adds uppercase versions for “.GIF”, “.JPG”, and “.PNG” files.
Internally, this release also changes the edit page sequence to use the $_POST autoglobal instead of $_REQUEST (i.e., posting edits is only allowed via method=‘post’ and not via query string parameters).
This release fixes the bug that caused $Page Template Fmt? to no longer work in pmwiki-2.0.beta1.
This release marks PmWiki 2.0 as entering “beta” status, as it finally begins moving towards official release. The major change for this release is in the skins code — previous versions of PmWiki used $Page Template Fmt? to specify the location of the template file to be used; newer versions now use the $Skin variable to specify the location of the skins directory (in pub/skins/) that contains the skin template file, php configuration script, and other files.
In general, if you previously had $Page Template Fmt? set to “pub/skins/myskin/myskin.tmpl”, then you now simply set $Skin=‘myskin’; to get things to work. See PmWiki.Layout Basics for more details.
These are the release notes for the development releases of PmWiki 2.0.
First, this is definitely still in the development stages, so many things are likely to change between now and the official releases.
Second, at present there’s not a good way to upgrade from PmWiki 1.0 to PmWiki 2.0, although upgrade support is expected to arrive in future (development) releases. So, you can use this version just to see the new developments and gain some experience, but migrating from 1.0 to this version is still likely to be a bit of a chore.
Bugs and other requests can be reported to the PmWiki Issue Tracking System at http://www.pmwiki.org/pmwiki2/pmwiki.php/PITS. Any help in testing, development, and/or documentation is greatly appreciated.