This version has a number of relatively minor changes.
First, the $UrlLinkFmt variable has been modified so that links to external urls automatically have a rel='nofollow' attribute added to them, to help combat wiki spam as described in http://www.google.com/googleblog/2005/01/preventing-comment-spam.html. Site administrators can customize $UrlLinkFmt and $UnapprovedLinkFmt to supply or omit rel='nofollow' as appropriate.
The algorithm for creating page names from [[free links]] has been modified slightly. First, letters following a hyphen are no longer automatically capitalized, thus [[page-link]] refers to a page named "Page-link" and not "Page-Link". This is more compatible with version 1's naming syntax. Also, single quotes don't promote the following letter to uppercase, thus [[John's page]] now links to JohnsPage and not JohnSPage.
Sites that want to keep PmWiki 2's prior behavior can do so with the following:
$PageNameChars = '-[:alnum:]';
$MakePageNamePatterns = array(
"/[^$PageNameChars]+/" => ' ',
"/(\\b\\w)/e" => "strtoupper('$1')",
"/ /" => '');
The localmap.txt InterMap file can now contain comments (denoted by leading '#' in the file).
Headings (!! markup) can now have block wikistyles.
More information is available in the PmWiki.ChangeLog.
PmWiki uses PHP's sessions for tracking passwords and page authorizations; however, if a session times out (or is otherwise lost) while an author is in the middle of editing a password-protected page, the author's edits may be lost when re-prompted for the password. This release fixes this problem by preserving the edit text and other posted form variables when prompting for a password.
This release makes improvements to the gui buttons, fixes some bugs, and minor other improvements and changes.
Alternate text is now valid inside of WikiTrails; i.e., one can use <<|[[TrailPage | alternate text]]|>> to change the text of the link to the trailpage.
The GUI button module has a number of changes.
This release also eliminates the <p>...</p> tags that were being generated around markup lines that contained other HTML block markups (e.g., search results, page listings, forms). As a result, these pages are now valid HTML and pass the W3C validator.
$HTMLHeaderFmt has been changed so that skin designers can completely turn off the inline-styles mechanism used by PmWiki and other cookbook modules. To disable the inline styles, use $HTMLHeaderFmt['styles'] = ''; .
Finally, this release fixes a call to setlocale() which was supposed to only return the current locale but instead was causing the locale to change.
This release simply makes some minor bug fixes to wikistyles (colors set in wikistyles extend to anchor tags), arrays of default passwords, and advanced table handling.
The major feature of this release is the addition of the graphical buttons in the edit page. By default this feature is disabled -- to enable it, use the following in config.php.
$EnableGUIButtons = 1;
If your site customizes the $PageEditFmt variable, then note that the buttons are placed at the end of the $EditMessageFmt and that the <textarea> needs to have id='edit' in order for the buttons to work.
The rss.php script has also been improved -- it now automatically translates named character entities (from HTML 4) into their numeric equivalents. This eliminates a lot of feed validation errors and problems in specific RSS feed consumers.
This release adds a $Titlespaced variable and {$Titlespaced} markup; $Titlespaced is replaced by either a page's title (if defined by the (:title:) directive) or by the spaced version of the page's name.
Finally, a number of WikiStyles bugs have been fixed.
This release introduces a number of relatively minor optimizations and improvements, summarized below. If you don't understand what any of these mean, they probably don't affect you. :-)
$PageEditFmt now includes id='text' to make for easier styling/referencing.
This release fixes a bug introduced in 2.0.beta7 that prevented the refcount.php (for ?action=refcount) from generating links correctly. It also cleans up the handling of wikistyles and %-in-urls (which is what 2.0.beta7 was supposed to fix).
In general, all sites using the 2.0.betaXX series are recommended to upgrade to this latest release.
This release adds a number of <div> tags and identifiers around the various forms that PmWiki produces (e.g., uploads, search results, attribute pages, etc.). This makes such forms easier to style in CSS.
In addition, this release adds some functionality to the urlapprove.php script to limit the number of unapproved urls that can be saved in a page (helps to combat wikispam).
Finally the release adds the (:description:) markup for generating <meta name='description' ... /> tags in the output. (:description:) may also get used for other features later on (e.g., excerpts in search results, etc.).
This release primarily cleans up a number of items in the handling of uploads:
(:attachlist:) automatically adds "replace-attachment" links (denoted by triangles) to the items in the list
This release also changes the StopWatch() function (used internally for benchmarking/timing PmWiki performance) to only have an effect when $EnableStopWatch is set to 1 (wall clock timings only) or 2 (wall clock and user-process timings).
This release makes some substantial improvements in the installation procedure. First, the installation steps have been simplified, and PmWiki provides accurate instructions when it encounters a PHP "safe_mode" environment.
The release also provides better handling of the '.flock' file -- if PmWiki discovers it cannot open an existing .flock file for writing, it removes the file and tries again rather than complaining about it. This makes the system more robust when page directories are going through backup+restore.
This release provides some very minor bugfixes to the [[target |#]] markup, to the appearance of $...variables in documentation, and extends uploads.php to be able to work better with url rewriting.
This release makes a number of reasonably significant changes. First and
foremost, it changes the ?pagename= uri syntax to be ?n=, and
installation now defaults to $EnablePathInfo = 0; to make better
compatibility.
Sites which wish to continue using the .../Main/HomePage form of uri
instead of ?n=Main.HomePage should set $EnablePathInfo = 1 in
config.php.
This release also fixes a probable bug in the handling of author names which was causing spaces to be incorrectly removed.
2.0.beta8 includes features for advanced CSS styling of simple tables
via the $TableRowAttrFmt and $TableCellAttrFmt variables, more description
will be forthcoming in a Cookbook recipe.
Also, this release includes vastly improved support for UTF-8 sites,
including the ability to have UTF-8 characters in pagenames and
[[utf-8 links]]. We're still working out the details to be
able to support UTF-8 wikiwords -- PHP's functions don't provide
good support for this. See scripts/xlpage-utf-8.php for more
information on UTF-8.
Finally, the Q: and A: markups are back, and a few other minor bug fixes and documentation improvements have been included.
This release has a number of improvements and changes to it. First, this release provides a scripts/xlpage-utf-8.php file, which adapts PmWiki to be able to work somewhat with utf-8 characters in pagenames. Since PHP's preg_* functions seem to be unable to detect UTF-8 alphanumeric characters, the trade-off at the moment is that WikiWord links are limited to the ASCII character set. We're working on ways to get around this restriction, however.
The xlpage-utf-8.php script can be automatically loaded by any XLPage translation that specifies 'xlpage-i18n' => 'utf-8'.
This release also:
[[target |#]])
$DefaultPageTextFmt (note this may change again)
This release contains a number of relatively minor bugfixes (see the ChangeLog), and it also restores the $WikiWordCount functionality from PmWiki 1 in which the wiki administrator can limit the number of conversions for each WikiWord.
The sample-config.php file has been updated with more comments and suggestions for customizations.
Finally, this release increases the default value of $MaxIncludes to 50 (and provides better documentation of the $MaxIncludes 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.EditQuickReference and PmWiki.UploadQuickReference 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 $PageTemplateFmt 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 $PageTemplateFmt 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 $PageTemplateFmt set to "pub/skins/myskin/myskin.tmpl", then you now simply set $Skin='myskin'; to get things to work. See PmWiki.LayoutBasics 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/wiki/PITS/PITS. Any help in testing, development, and/or documentation is greatly appreciated.