PmWeekly, July 03, 2017

Update for PmWiki activity June 26 - July 03, 2017: documentation about conditionals, internationalization, one new recipe added and two recipes updated, discussion about improving the development platform.


PmWiki entries at Wikipedia and WikiMatrix were updated.

Subversion changes to the core

Change log. You can get the latest, yet unpublished PmWiki code from Subversion or download as a ZIP archive.

  • The documentation of the wiki variable $Author conflicts with the Subversion keyword $Author:...$ and was automatically transformed by Subversion. The next version works around this conflict, but in the documentation we need to write $Author : with an additional space before the colon.
  • The documentation was updated, see below.

Documentation, Internationalization

The documentation was improved for Conditional Markup, explaining that protecting a page or a group with passwords is different and probably more secure than hiding parts of the page with conditionals.

The German documentation was updated. You can download it here.

The international documentation listing is now ordered alphabetically instead of reverse-chronologically.


In the PITS: PmWiki Issue Tracking System (please comment, vote):

  • 01412 integrated developer platform How to unclutter your watchlist trail, can we add personal pages or groups for users/developers, simple self-registration?
  • 01414 Saving blocked because of "invalid edit summary" Caused by a spam filter. Add a ` backtick ` before CamelCase words or words with too many consonants.
  • 01415 PITS new issue form replaces old bugs Bug in the PITS recipe, now fixed.

Cookbook (addons, modules, skins)

New recipe:

Recipes updated:

  • B3 blog (Easy to install and use wiki blogging system) by Petko : Add $B3['EnableStatus']: default status settings when pre-filling the edit template. Can be Public or Draft.

  • PITS (The PmWiki Issue Tracking System) by Petko : Fix wrong issue number when a non-issue page starts with a number.

Leave a reply
Your name (required):

Your comment (required):

Enter value: Captcha