Version 2.0.13 (2005-11-10)
This is a release containing minor bugfixes and improvements
in preparation for the 2.1.beta series.
Wiki administrators should note that after this release PmWiki
will default to having WikiWords disabled. To make sure
WikiWords are enabled, use $LinkWikiWords = 1; in
the local/config.php file.
Version 2.0.12 (19-Oct-2005)
This release cleans up problems with page validation for page links
containing query fragments and ampersands, changes PmWiki to use a
PHP "return" statement instead of "exit", and fixes a warning in
scripts/transition.php.
Version 2.0.11 (17-Oct-2005)
This release fixes a couple of important bugs and adds some new
features to PmWiki.
Most importantly, this release fixes bug with ?action=attr
affecting the page history.
For sites using LDAP authentication with authuser.php, PmWiki
now provides $AuthLDAPBindDN and $AuthLDAPBindPassword variables
to specify the binding to be used for searching. It also works
around a PHP oddity that causes users to appear authenticated
when an empty password is provided. Authuser.php also now
handles straight md5 password encryptions (commonly used by
MySQL databases).
The core now includes the (:linebreaks:) markup
(from Cookbook:LineBreaks), which causes text on separate
lines in the markup to appear as separate lines in the output
(i.e., no auto-joining of one line to the previous one).
There have been some internal changes designed to provide
better support for leading-whitespace rules (more details on
this in a future release).
The core now provides an (:if date:) markup to display
text only if the current day is within a range of supplied
dates.
Version 2.0.10 (29-Sep-2005)
Version 2.0.9 (28-Sep-2005)
This release fixes an oversight in xlpage-utf-8.php that failed to uppercase ASCII letters when mb_strtoupper isn't present.
Version 2.0.8 (27-Sep-2005)
This release simply adds the capability to use quotes to enter
pass phrases (passwords containing spaces) using ?action=attr,
and fixes a bug with displaying the name instead of the title in
the default print skin.
Version 2.0.7 (26-Sep-2005)
This version changes the xlpage-utf-8.php case conversion slightly
to use a more direct conversion table, and completed the table
for more characters in the utf-8 set.
This release also fixes the $VersionNum variable that was supposed to
appear in 2.0.6.
An accesskey shortcut (ak_textedit) is being added to the edit form
text area.
Lastly, this release adds a timelimit to the generation of .linkindex,
to avoid long page times when generating the .linkindex.
Version 2.0.6 (16-Sep-2005)
In this release, we provide quite a few more updates for sites that
want or need to use utf-8 encoding, fix a large number of utf-8
related bugs, introduce better handling of author cookies, and
better support for keeping track of version releases.
The biggest change is to the xlpage-utf-8.php recipe, which has
been substantially rewritten from the previous version. This new
version of xlpage-utf-8.php no longer depends on the
mb_strtoupper()
function, which seems to be not available in many PHP installations.
The new version of xlpage-utf-8.php uses mb_strtoupper() if it's
available, but if not available then it manually performs case
conversions from a Unicode table that is directly encoded in the
script. At present this table only understands case conversions
for Western European (Latin-1 or ISO-8859-1) and Cyrillic characters,
we'll want to expand the table to support other language character
sets as needed. Just contact me on the listserv if a particular
character isn't yet supported.
In addition to the above, author names and cookies in utf-8 environments
now work again, and link suffixes containing non-ASCII characters work
again also.
The GUI button handling in IE has been greatly improved; text selection
in IE now works as you would expect it to work when a gui button is
pressed. Possibly still no hope for Mac Safari browsers, unfortunately...
A $CookiePrefix variable has been introduced; a wiki administrator
can set $CookiePrefix to prevent PmWiki's cookies from interfering with
cookies set from other applications under the same domain name.
Some XHTML validation issues surrounding the use of