# Release Notes

## Version 2.2.134 (2020-11-30)

This is a documentation update version.

## Version 2.2.122 (2019-11-19)

Version 2.2.121 was released by mistake and contained some experimental code that was meant to be tested first.

## Version 2.2.64 (2014-05-08)

This version adds the "{(mod)}" markup expression for modulo/remainder calculations, and the "tel:" and "geo:" URI schemes which, on compatible devices like smartphones, allow the creation of links to dial telephone numbers and open map/location applications.

The SysMergePassthru switch was added, if enabled, it allows the "Simultaneous Edits" conflict resolution to use the passthru() function instead of popen(). The documentation was updated. ## Version 2.2.63 (2014-04-05) This version allows for form elements to have custom attributes containing a dash in the attribute names and enables the attributes 'required', 'placeholder' and 'autocomplete' for forms. A minor bug with pagelist {RequestVariables} appearing on some installations was fixed. The documentation was updated. ## Version 2.2.62 (2014-02-28) This version adds the variable EnableTableAutoValignTop which allows to make advanced tables compatible with . For developers, a fourth argument template was added to the Markup_e() function, and a callback template 'return' was added. The documentation was updated. ## Version 2.2.61 (2014-01-31) This version removes unnecessary snippets of code and adds the variable TableCellAlignFmt which allows to make simple tables compatible with . The documentation was updated. ## Version 2.2.60 (2014-01-12) This version reverts the changes to the pmwiki.css file made in 2.2.59. ## Version 2.2.59 (2014-01-11) This version has an improvement for Blocklist when multiple text fields are posted. A bug with some nested markup conditionals was fixed. The default skin switched font sizes from points (fixed) to percents (relative). A couple of other minor bugs were fixed and the documentation was updated. ## Version 2.2.58 (2013-12-25) This version enables customization of (:input auth_form:), and fixes a couple of minor bugs. The documentation was updated. ## Version 2.2.57 (2013-11-03) This version enables the use of the Attach: link format in the (:attachlist:) directive. The documentation was updated. ## Version 2.2.56 (2013-09-30) This version aims to fix a PHP 5.5 compatibility issue with a deprecated feature of the preg_replace() function. The () class now detects and works around a bug with the iconv() function, and the documentation was updated. ## Version 2.2.55 (2013-09-16) This version adds the variable EnableDraftAtomicDiff. If enabled, publishing from a draft version will clear the history of intermediate draft edits, and the published version will contain a single combined diff from the previous published version. The documentation was updated. ## Version 2.2.54 (2013-08-13) This version fixes a bug when old versions are restored from draft pages. The documentation was updated. ## Version 2.2.53 (2013-07-08) This version enables a message to be shown when a post is blocked because of too many unapproved links. The documentation was updated. ## Version 2.2.52 (2013-06-08) This version hides warnings about a deprecated feature in PHP 5.5 installations (preg_replace with /e eval flag). Three new upload extensions were added: docx, pptx and xlsx produced by recent versions of some office suites. The documentation was updated. ## Version 2.2.51 (2013-05-08) This version updates the addresses for the remote blocklists. A minor XSS vulnerability for open wikis, which was discovered today, was fixed. The documentation was updated. ## Version 2.2.50 (2013-04-08) This release only updates the documentation to the latest state on pmwiki.org. ## Version 2.2.49 (2013-03-09) This version adds an array UploadBlacklist containing forbidden strings of an uploaded filename (case insensitive). Some Apache installations try to execute a file which has ".php", ".pl" or ".cgi" anywhere in the filename, for example, "test.php.txt" may be executed. To disallow such files to be uploaded via the PmWiki interface, add to config.php such a line:  UploadBlacklist = array('.php', '.pl', '.cgi', '.py', '.shtm', '.phtm', '.pcgi', '.asp', '.jsp', '.sh');  The documentation was updated. ## Version 2.2.48 (2013-02-11) This version fixes a bug introduced yesterday with some links. ## Version 2.2.47 (2013-02-10) This version enables tooltip titles in links to anchors in the same page, and the documentation was updated. ## Version 2.2.46 (2013-01-07) This version adds UploadPermAdd and UploadPermSet variables, and the documentation was updated. If your wiki has uploads enabled, it is recommended to set the variable UploadPermAdd to 0. The UploadPermAdd variable sets additional unix permissions applied to newly uploaded files, and should be 0 (recommended as of 2013). If uploaded files cannot be downloaded and displayed on the website, for example with the error 403 Forbidden, set this value to 0444 (core setting, default since 2004).  UploadPermAdd = 0; # recommended  The UploadPermSet variable unconditionally sets the file permissions on newly uploaded files. Only advanced administrators should use it. ## Version 2.2.45 (2012-12-02) This version fixes some PHP notices appearing on some installations. The documentation was updated. ## Version 2.2.44 (2012-10-21) This version improves the display of consecutive whitespaces in page histories, and fixes the definition of PageTextVariables containing a dash. The documentation was updated. ## Version 2.2.43 (2012-09-20) This version makes it possible to use HTML attribute names that contain dashes, and removes a warning when editing and previewing Site.EditForm. The documentation was updated. ## Version 2.2.42 (2012-08-20) This version provides a workaround for cases when a wiki page contains a character nonexistent in the active encoding. The documentation was updated. ## Version 2.2.41 (2012-08-12) This version changes the internal KeepToken separator to be compatible with more encodings. The documentation was updated. ## Version 2.2.40 (2012-07-21) This version provides a helper function replacing htmlspecialchars() and compatible with PHP 5.4. The documentation was updated. ## Version 2.2.39 (2012-06-25) This version provides a fix for links to attachments containing international characters. The documentation was updated. ## Version 2.2.38 (2012-05-21) This version fixes a "parameter count" warning which appeared on some websites. ## Version 2.2.37 (2012-05-01) This version provides a workaround for installations with broken iconv() function, while optimizing the recode function. This should fix the "Unable to retrieve edit form" problem in some wikis. Dots in sections are now better supported, PageVariables are expanded in template defaults, and the documentation is updated. ## Version 2.2.36 (2011-12-28) This version fixes the recode function to try to recover Windows-1252 characters in ISO-8859-1 files. A new variable EnableOldCharset enables the page["=oldcharset"] entry which will be used in the future. A couple of minor bugs were fixed and the documentation was updated. ## Version 2.2.35 (2011-11-11) This release fixes a critical PHP injection vulnerability, reported today by Egidio Romano. PmWiki versions 2.2.X, 2.1.X, 2.0.X and 2.0.beta33 and newer are vulnerable. When you upgrade, please read carefully the Release notes for all PmWiki versions since yours. If you cannot upgrade, it is recommended to disable Searches at the earliest opportunity (even if your wiki skin doesn't have a search form). Add to config.php such a line:  if (action == 'search') action = 'browse';  If your old version wiki allows editing by not entirely trusted visitors, even on limited pages like a WikiSandbox, you should also disable PageLists. Add to config.php this line:  EnablePageList = 0;  This version has an important change for international wikis: the () function no longer loads encoding scripts such as xlpage-utf-8.php. When you upgrade, you need to include those scripts from config.php, before calling ():  include_once("scripts/xlpage-utf-8.php"); # if your wiki uses UTF-8 XLPage?('bg','PmWikiBg.XLPage?');  All links can now have tooltip titles. Previously, only images and external links could have tooltip titles, now this feature is enabled for internal links. To set a tooltip title, add it in quotes after the link address:  [[Main.HomePage"This is a tooltip title"]] [[Main.HomePage"This is a tooltip title"|Home]] [[http://www.pmwiki.org"Home of PmWiki"]] Attach:image.jpg"Tooltip title of the image"  The following new upload extensions were added: svg, xcf, ogg, flac, ogv, mp4, webm, odg, epub. A couple of minor optimizations were added (MarkupExpressions and rendering of page history) and the documentation was updated. ## Version 2.2.34 (2011-10-10) This version resets the timestamps of the default pages Site(Admin).AuthUser which are expected in case of upgrades from the versions 2.1.*. Core MarkupExpressions which manipulate strings should now work better with international characters. The documentation was updated to its latest state from pmwiki.org. ## Version 2.2.33 (2011-09-23) This version fixes a security bug introduced in 2.2.32 which left the groups Site and SiteAdmin open for reading and editing because the pages Site.GroupAttributes and SiteAdmin.GroupAttributes didn't have all necessary attributes. All wikis running 2.2.32 should upgrade. If you cannot immediately upgrade, you can set the attributes from your wiki: • open the attributes page [[SiteAdmin.GroupAttributes?action=attr]] and set a "read" and an "edit" password,  @lock  is recommended. • open the attributes page [[Site.GroupAttributes?action=attr]] and set an "edit" password,  @lock  is recommended. Do not set a "read" password here. The release also fixes the refcount.php script to produce valid HTML, and updates intermap.txt entries PITS: and Wikipedia: to point to their current locations. ## Version 2.2.32 (2011-09-18) This is the first version shipping with the core documentation in the UTF-8 encoding. PmWiki will automatically convert it on the fly for wikis using an older encoding. It is recommended that all new PmWiki installations enable UTF-8. Migration of existing wikis from an older encoding to UTF-8 shouldn't be rushed: it is not trivial and will be documented in the future. A required HTML xmlns attribute was added to the print skin template. The history rendering is now faster when many lines are added or removed. Note: Due to a manipulation error, a version 2.2.31 was created before it was ready for a release. ## Version 2.2.30 (2011-08-13) This version fixes a Charset definition in international iso-8859-*.php files. This will help for a future transition to UTF-8. A variable EnableRangeMatchUTF8 was added, set it to 1 to enable range matches of pagenames in UTF-8 like [A-D]. Previously the range matches were always enabled in UTF-8, but we found out that on some installations this feature breaks all pagelists, even those without range matches. In case the feature worked for you, you can re-enable it. ## Version 2.2.29 (2011-07-24) This release fixes Attach links that were broken with the Path fix in 2.2.28 earlier today. ## Version 2.2.28 (2011-07-24) This release fixes 2 potential XSS vulnerabilities and a bug with Path: links. ## Version 2.2.27 (2011-06-19) This release fixes a validation bug on pages after a redirection. A new block %justify% was added, allowing left and right aligned text. The page history now accepts a URL parameter ?nodiff=1 which hides the rendering of edit differences, showing only timestamps, authors, summaries and "Restore" links; it allows to restore a vandalized page with a huge contents or history which otherwise would break the memory or time limits of the server. ## Version 2.2.26 (2011-05-21) This release fixes a redundant removal of link hashes from WikiTrails, and updates the documentation to the most recent version from PmWiki.org. ## Version 2.2.25 (2011-03-22) This release only updates the documentation to the latest state on pmwiki.org. ## Version 2.2.24 (2011-02-15) This version reverts the way existing PageVariables are processed, like version 2.2.21 or earlier, but it adds a special variable authpage which can be used in definitions. It is the same as the page array, but exists only if the visitor has read permissions. For example, an administrator can set to config.php:  FmtPV['LastModifiedSummary'] = '@authpage["csum"]'; # instead of '@page["csum"]'  Then, the edit summary metadata will only be available if the user has read permissions. ## Version 2.2.23 (2011-01-25) This version sets the default value of EnablePageVarAuth to 0 until we investigate a reported problem with authentication. ## Version 2.2.22 (2011-01-16) This version adds the variable EnableXLPageScriptLoad which, if set to 0, will prevent authors to load scripts from and to accidentally change the encoding of the wiki. If you use it, make sure you include the required files, eg. xlpage-utf-8.php from local config files. PageVariables should now respect authentications: without read permissions, the title, description, change summary, author of a protected page are unavailable. PageVariables that are computed without reading the page are still available (eg. Group, Namespaced, Version etc.). Administrators can revert the previous behavior by adding to config.php such a line:  EnablePageVarAuth = 0;  ## Version 2.2.21 (2010-12-14) Due to a mis-configuration of a local svn repository, some of the changes intended for 2.2.20 didn't make it in the correct branch. This release corrects this. ## Version 2.2.20 (2010-12-14) This version fixes a potential XSS vulnerability, reported today. An AuthUser bug with excluding users from authgroups was fixed. A new InterMap prefix : was added, it leads to the Localization section on PmWiki.org and should help the work of translators. A couple of other minor bugs were fixed and the documentation was updated. ## Version 2.2.19 (2010-11-10) This is a documentation-update release. ## Version 2.2.18 (2010-09-04) This version fixes 3 minor bugs, and updates the documentation. ## Version 2.2.17 (2010-06-20) This version adds a variable PostConfig containing functions and scripts to be loaded after stdconfig.php. Tabindex was added as a valid form field attribute. Protected downloads now respect existing browser caches. AuthUser now allows more flexible cookbook recipe integration. A couple of bugs were fixed and the documentation was updated. ## Version 2.2.16 (2010-05-10) This version fixes a bug with parsing html attributes which could allow XSS injection. Wikis allowing unprotected editing are encouraged to upgrade. A bug with the "center" button of the GUI edit toolbar was corrected. The "exists" conditional now accepts wildcards, for example:  (:if exists Main.*:)There are pages in the Main group (:if:)  The documentation was updated. ## Version 2.2.15 (2010-03-27) This version adds some minor bugfixes and optimizations notably a bug with (:template none:) introduced in the last version 2.2.14. ## Version 2.2.14 (2010-02-27) This release corrects inline styles for links. Undefined include/template  {variables}  are now removed from the included section, like Page(Text)Variables, and can be used in conditional expressions. If needed, this change can be reverted by adding to config.php such a line: EnableUndefinedTemplateVars = 1; # keep and display unset {$$variables}  templates now accept the sections  !first  and  !last  for markup to appear for every page in list except the first or last one. "Title" attributes were added to external links. You can have tooltip titles on external links, including InterMap and attachments, by adding the link title in double quotes after the URL:  [[http://www.pmwiki.org"Home of PmWiki"| External link]]  For international wikis, PmWiki now automatically translates the titles of technical pages like or RecentChanges -- just define these strings as usual in , for example, in French:  'AllRecentChanges?' => 'Tous les changements récents',  Some minor optimizations were done and the documentation was updated. ## Version 2.2.13 (2010-02-21) This release fixes a bug with DiffKeepNum introduced in 2.2.10 -- the count of revisions was incorrect and a page could drop more revisions than it should. The page history layout was modified with a rough consensus in the community. The history now defaults to "source" view with word-level highlighting of the differences. Authors can see the changes in rendered output by clicking on the link "Show changes to output". Admins can switch back the default by adding such a line to config.php:  DiffShow['source'] = (@_REQUEST['source']=='y')?'y':'n';  To disable word-level highlighting and show plain text changes:  EnableDiffInline = 0;  In the page history rendering, a few minor bugs were fixed and the code was slightly optimized. The documentation was updated. ## Version 2.2.12 (2010-02-17) This release adds simple word-level highlighting of differences in the page history, when "Show changes to markup" is selected. To enable the feature, add to config.php such a line:  EnableDiffInline = 1;  This feature is like what the recipe provides, but not exactly the same, and the implementation is simpler. It is enabled on PmWiki.org and can be improved -- your comments are welcome. ## Version 2.2.11 (2010-02-14) This release adds two new table directives for header cells, (:head:) and (:headnr:). They work the same way as (:cell:) and (:cellnr:) except that create <th> instead of <td> html tags. The pagerev.php script was refactored into separate functions to allow easier integration of recipes displaying the page history. A couple of minor bugs were fixed and the documentation was updated. ## Version 2.2.9, 2.2.10 (2010-01-17) Most important in this release is the official change of EnableRelativePageVars to 1. The change is about how {Variable} in included pages is understood by PmWiki. So, if your wiki relies on page variables from included pages, and doesn't have EnableRelativePageVars set to 1, after upgrading to 2.2.9, you can revert to the previous behavior by adding to config.php such a line:  EnableRelativePageVars = 0;  More information about page variables can be found at:  http://www.pmwiki.org/wiki/PmWiki/PageVariables  This release adds a new variable EnablePageTitlePriority which defines how to treat multiple (:title..:) directives. If set to 1, the first title directive will be used, and if a page defines a title, directives from included pages cannot override it. PmWiki default is 0, for years, the last title directive was used (it could come from an included page or GroupFooter). This release also adds a new variable DiffKeepNum, specifying the minimum number (default 20) of edits that will be kept even if some of them are older than the limit of DiffKeepDays. A number of bugs were fixed and the documentation was updated. ## Version 2.2.8 (2009-12-07) This release fixes another PHP 5.3 compatibility issue with conditional markup. The Author field now handles apostrophes correctly. The documentation was updated. ## Version 2.2.7 (2009-11-08) This release fixes most PHP 5.3 compatibility issues. Unfortunately some specific builds for Windows may still have problems, which are unrelated to PmWiki. Notably, on Windows, all passwords need to be 4 characters or longer. Upload names with spaces are now correctly quoted. The documentation was updated. ## Version 2.2.6 (2009-10-04) With this release it is now possible to display recently uploaded files to the RecentChanges pages -- if you have been using the recipe, please uninstall it and follow the instructions at http://www.pmwiki.org/wiki/Cookbook/RecentUploadsLog. The release also introduces MakeUploadNamePatterns to allow custom filename normalization for attachements. It is now possible to replace PageListFilters and FPLTemplateFunctions with custom functions. Notify should now work in safe_mode. Some bugs were fixed, among which one with conditional markup with dates. The documentation was updated. ## Version 2.2.5 (2009-08-25) This release adds a new markup for Pagelist templates, (:template none:) which allows a message to be set when the search found no pages. The () function was broken into configurable sub-parts to allow development hooks. A number of bugs were fixed, and the documentation was updated. ## Version 2.2.4 (2009-07-16) This release fixes a bug introduced earlier today with HTML entities in . ## Version 2.2.3 (2009-07-16) This release fixes six potential XSS vulnerabilities, reported by Michael Engelke. The vulnerabilities may affect wikis open for editing and may allow the injection of external in their pages. Public open wikis should upgrade. A new variable EnableUploadGroupAuth was added; if set to 1, it allows password-protected uploads to be checked against the Group password. It is now possible to use  @_site_edit, @_site_read, @_site_admin or  @_site_upload  global passwords in pages. A number of other small bugs were fixed, and the documentation was updated. ## Version 2.2.2 (2009-06-21) The major news in this release is a fix of an AuthUser vulnerability. The vulnerability affects only wikis that (1) rely on the AuthUser core module for User:Password authentication, -AND- (2) where the PHP installation runs with the variable "magic_quotes_gpc" disabled. All PmWiki 2.1.x versions from pmwiki-2.1.beta6 on, all 2.2.betaX, 2.2.0, and 2.2.1 are affected. The PmWiki SiteAnalyzer? can detect if your wiki needs to upgrade:  http://www.pmwiki.org/wiki/PmWiki/SiteAnalyzer  If your wiki is vulnerable, you should do one of the following at the earliest opportunity: • Upgrade to a version of PmWiki at least 2.2.2 or greater. • Turn on magic_quotes_gpc in the php.ini file or in a .htaccess file. Alternatively, you can temporarily disable AuthUser until you upgrade. Note that even if your wiki does not have the AuthUser vulnerability at the moment, you are strongly encouraged to upgrade to PmWiki version 2.2.2 or later, as some future configuration of your hosting server might put you at risk. This release also comes with minor updates in the local documentation; fixes were applied for international wikis - notably global variables in xlpage-utf-8.php and a new variable EnableNotifySubjectEncode, which allows e-mail clients to correctly display the Subject header; and a number of other small bugs were fixed. ## Version 2.2.1 (2009-03-28) This release comes with an updated local documentation; wiki trails now work cross-group; guiedit.php now produces valid HTML, and other small bugs were fixed. We also added EnableRedirectQuiet, which allows redirects to take place without any mention of "redirected from page ....". ## Version 2.2.0 (2009-01-18) This is a summary of changes from 2.1.x to 2.2.0. • Several pages that were formerly in the Site.* group are now in a separate SiteAdmin.* group, which is read-restricted by default. The affected pages include Site.AuthUser, , , Site.Blocklist, and . If upgrading from an earlier version of PmWiki, PmWiki will prompt to automatically copy these pages to their new location if needed. If a site wishes to continue using the old Site.* group for these pages, simply set when carrying out this upgrade inspect your config files for lines such as BlocklistDownload['Site.Blocklist-PmWiki'] = array('format' => 'pmwiki'); as you may wish to fix then, eg BlocklistDownload[SiteAdminGroup . '.Blocklist-PmWiki'] = array('format' => 'pmwiki'); • Important Change in Passwords in PmWiki 2.2 indicating that the group can be edited even if a site password is set will be done by "@nopass" prior it was done by "nopass" When migrating a wiki you will have to manually modify the permission or by a script replace in all the page concerned passwdread=nopass: by passwdread=@nopass (see PITS:00961) --isidor • It's now easy to disable the rule that causes lines with leading spaces to be treated as preformatted text -- simply set EnableWSPre=0; to disable this rule. Important: There is ongoing discussion that the leading whitespace rule may be disabled by default in a future versions of PmWiki. If you want to make sure that the rule will continue to work in future upgrades, set EnableWSPre=1; in local/config.php. • The ROSPatterns variable has changed somewhat -- replacement strings are no longer automatically passed through FmtPageName() prior to substitution (i.e., it must now be done explicitly). • Page variables and page links inside of (:include:) pages are now treated as relative to the included page, instead of the currently browsed page. In short, the idea is that links and page variables should be evaluated with respect to the page in which they are written, as opposed to the page in which they appear. This seems to be more in line with what authors expect. There are a number of important ramifications of this change: • We now have a new {*var} form of page variable, which always refers to "the currently displayed page". Pages such as Site.PageActions and Site.EditForm that are designed to work on "the currently browsed page" should generally switch to using {*FullName} instead of {FullName}. • The EnableRelativePageLinks and EnableRelativePageVars settings control the treatment of links and page variables in included pages. However, to minimize disruption to existing sites, EnableRelativePageVars defaults to disabled. This will give existing sites an opportunity to convert any absolute {var} references to be {*var} instead. • Eventually EnableRelativePageVars will be enabled by default, so we highly recommend setting EnableRelativePageVars = 1; in local/config.php to see how a site will react to the new interpretation. Administrators should especially check any customized versions of the following: SideBar pages with ?action= links for the current page Page lists that refer to the current group or page, etc in sidebars, headers, and footers • The (:include:) directive now has a basepage= option whereby an author can explicitly specify the page upon which relative links and page variables should be based. If no basepage= option is specified, the included page is assumed to be the base. • Sites that want to retain the pre-2.2 behavior of (:include:) and other items can set Transition['version'] = 2001900; to automatically retain the 2.1.x defaults. • Text inserted via (:include:) can contain "immediate substitutions" of the form {$$option} -- these are substituted with the value of any options provided to the include directive.
• PmWiki now recognizes when it is being accessed via "https:" and switches its internal links appropriately. This can be overridden by explicitly setting $ScriptUrl and $PubDirUrl.
• A new $EnableLinkPageRelative option allows PmWiki to generate relative urls for page links instead of absolute urls. • Draft handling capabilities have been greatly improved. When $EnableDrafts is set, then the "Save" button is relabeled to "Publish" and a "Save draft" button appears. In addition, an $EnablePublishAttr configuration variable adds a new "publish" authorization level to distinguish editing from publishing. See PmWiki:Drafts for more details. • There is a new {$:var} "page text variable" available that is able to grab text excerpts out of markup content. For example, {SomePage$:Xyz} will be replaced by a definition of "Xyz" in . Page text variables can be defined using definition markup, a line beginning with the variable name and a colon, or a special directive form (that doesn't display anything on output): :Xyz: some value # definition list form Xyz: some value # colon form (:Xyz: some value:) # directive form  • The (:pagelist:) command can now filter pages based on the contents of page variables and/or page text variables. For example, the following directive displays only those pages that have an "Xyz" page text variable with "some value": (:pagelist$:Xyz="some value":)
Wildcards also work here, thus the following pagelist command lists pages where the page's title starts with the letter "a":
(:pagelist $Title=A* :) • The if= option to (:pagelist) can be used to filter pages based on conditional markup: (:pagelist if="auth upload {=$FullName}":) pages with upload permission
(:pagelist if="date today.. {=$Name}":) pages with names that are dates later than today • Spaces no longer separate wildcard patterns -- use commas. (Most people have been doing this already.) • Because page variables are now "relative", the {$PageCount}, {$GroupCount}, {$GroupPageCount} variables used in pagelist templates are now {$$PageCount}, {$$GroupCount}, {$$GroupPageCount}. • One can now use {$$option} in a pagelist template to obtain the value of any 'option=' provided to the (:pagelist:) command.
• The (:pagelist:) directive no longer accepts parameters from urls or forms by default. In order to have it accept such parameters (which was the default in 2.1 and earlier), add a request=1 option to the (:pagelist:) directive.
• The count= option to pagelists now accepts negative values to count from the end of the list. Thus count=5 returns the the first five pages in the list, and count=-5 returns the last five pages in the list. In addition, ranges of pages may be specified, as in count=10..19 or count=-10..-5.
• Pagelist templates may have special (:template first ...:) and (:template last ...:) sections to specify output for the first or last page in the list or a group. There's also a (:template defaults ...:) to allow a template to specify default options.
• PmWiki comes with an ability to cache the results of certain (:pagelist:) directives, to speed up processing on subsequent visits to the page. To enable this feature, set $PageListCacheDir to the name of a writable directory (e.g., work.d/). • The (:if ...:) conditional markup now also understands (:elseif ...:) and (:else:). In addition, markup can nest conditionals by placing digits after if/elseif/else, as in (:if1 ...), (:elseif1 ...:), (:else1:), etc. • The (:if date ...:) conditional markup can now perform date comparisons for dates other than the current date and time. • WikiTrails can now specify #anchor identifiers to use only sections of pages as a trail. • A new (:if ontrail ...:) condition allows testing if a page is listed on a trail. • The extensions .odt, .ods, and .odp (from .org) are now recognized as valid attachment types by default. • A new blocklist capability has been added to the core distribution. It allows blocking of posts based on IP address, phrase, or regular expression, and can also make use of publicly available standard blocklists. See PmWiki.Blocklist for details. • There is a new SiteAdmin.AuthList page that can display a summary of all password and permissions settings for pages on a site. This page is restricted to administrators by default. • There are new {$PasswdRead}, {$PasswdEdit}, etc. variables that display the current password settings for a page (assuming the browser has attr permissions or whatever permissions are set in$PasswdVarAuth).
• Forms creation via the (:input:) markup has been internally refactored somewhat (and may still undergo some changes prior to 2.2.0 release). The new (:input select ...:) markup can be used to create select boxes, and (:input default ...:) can be used to set default control values, including for radio buttons and checkboxes.
• The (:input textarea:) markup now can take values from other sources, including page text variables from other pages.
• Specifying focus=1 on an (:input:) control causes that control to receive the input focus when a page is loaded. If a page has multiple controls requesting the focus, then the first control with the lowest value of focus= "wins".
• PmWiki now provides a scripts/creole.php module to enable Creole standard markup. To enable this, add include_once('scripts/creole.php') to a local customization file.
• PmWiki adds a new {(...)} markup expression capability, which allows various simple string and data processing (e.g., formatting of dates and times). This is extensible so that recipe authors and system administrators can easily add custom expression operators.
• It's now possible to configure PmWiki to automatically create Category pages whenever a page is saved with category links and the corresponding category doesn't already exist. Pages are created only if the author has appropriate write permissions into the group. To enable this behavior, add the following to local/config.php:
$AutoCreate['/^Category\\./'] = array('ctime' =>$Now);
• Sites with wikiwords enabled can now set $WikiWordCount['WikiWord'] to -1 to indicate that 'WikiWord' should not be spaced according to $SpaceWikiWords.
• WikiWords that follow # or & are no longer treated as WikiWords.
• Links to non-existent group home pages (e.g., [[Group.]] and [[Group/]]) will now go to the first valid entry of $PagePathFmt, instead of being hardcoded to "Group.Group". For example, to set PmWiki to default group home pages to $DefaultName, use
$PagePathFmt = array('{$Group}.$1', '$1.{$DefaultName}', '$1.$1');` • PmWiki now provides a$CurrentTimeISO and $TimeISOFmt variables, for specifying dates in ISO format. • Cookbook authors can use the internal PmWiki function (temporarily documented at DebuggingForCookbookAuthors) to change page text while preserving history/diff information, updating page revision numbers, updating RecentChanges pages, sending email notifications, etc. • Skin templates are now required to have <!----> and <!----> directives. Setting$EnableSkinDiag causes PmWiki to return an error if this isn't the case for a loaded skin. Skins that explicitly do not want or sections can use <!----> and <!----> to suppress the warning.
• Added a new "pre" wikistyle for preformatted text blocks.
• The xlpage-utf-8.php script now understands how to space UTF-8 wikiwords.
• Searches on utf-8 site are now case-insensitive for utf-8 characters.
• Many Abort() calls now provide a link to pages on pmwiki.org that can explain the problem in more detail and provide troubleshooting assistance.
• PmWiki no longer reports "?cannot acquire lockfile" if the visitor is simply browsing pages or performing other read-only actions.
• The $EnableReadOnly configuration variable can be set to signal PmWiki that it is to run in "read-only" mode (e.g., for distribution on read-only media). Attempts to perform actions that write to the disk are either ignored or raise an error via Abort(). • Including authuser.php no longer automatically calls (). • Authentication using Active Directory is now simplified. In Site.AuthUser or the$AuthUser variable, set "ldap://name.of.ad.server/" with no additional path information (see PmWiki.AuthUser for more details).
• Pages are now saved with a "charset=" attribute to identify the character set in effect when the page was saved.
• The phpdiff.php algorithm has been optimized to be smarter about finding smaller diffs.
• Removed the (deprecated) "#wikileft h1" and "#wikileft h5" styles from the pmwiki default skin.
• The mailposts.php and compat1x.php scripts have been removed from the distribution.

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..

Release Notes archive - notes for versions older than 2.2.0.