[Pmwiki-users] Re: Publishing a part of your wiki -- Experience using PmWiki

Knut Alboldt mailing
Wed Sep 22 14:28:46 CDT 2004

At 15:50 22.09.2004, chr wrote:
>On Wed, 22 Sep 2004, Patrick R. Michaud wrote:
> > > A custom EditFunction could instead of exporting the page upon a 
> save, add
> > > the name of the page to e.g. 'PagesToBeExported'. The publisher can then
> > > use this page to simplify the proofreading task.
> >
> > One can do this already -- just create custom RecentChanges pages that
> > are only updated when the text contains [:public:].  In PmWiki 1.0:
> >
> >     if (strstr(@$_REQUEST['text'],'[:public:]')!==false) {
> >       $RecentChanges['Main.PagesToBeExported'] =
> >         '* $Group.$Tlink . . . $CurrentTime by $AuthorLink';
> >     }
>That's nice. I don't think I'll need this functionality soon, but it's
>nice to know that I can easily monitor changes to certain pages. Then it's
>a matter of making a script (or php-function) that exports the relevant
>However, since my need isn't urgent, I really just wanted to discuss the
>functionality as such. Below is the idea I had, but with some more meat,
>to help clarify what I was thinking about.
>Reminder: The objective is to create a set of separate wiki pages in a
>"public" wiki, based on a subset of pages in a "private" wiki. A page
>which may be exported is called "publishable" page, and this might for
>instance be indicated by the prescene of a '[:public:]'-directive. The
>public wiki is an entirely separate wiki(-field), and will optionally
>allow users to edit the published pages.
>User case (the user is referred to as the "publisher" here):
>* A "publisher" creates a special wiki page, 'Main.PagesToExport', where
>   he lists pages that should be exported. And also to where they should
>   be exported (through some special directive).
>** The publisher can then export pages listed on this page through a URI:
>         http://www.pmwiki.org/Main/PagesToExport?action=export
>    Suitable access rights should be necessary for this action of course.
>* When a publishable page is modified, this is noted here:
>         'Main.ModifiedExportedPages'
>* That page, 'Main.ModifiedExportedPages', allows the "publisher" to:
>** Check what changes have happened to the various publishable pages
>** Re-export the pages, perhaps by invoking some special action.
>         http://www.pmwiki.org/Main/ModifiedExportedPages?action=export
>   where the export destination could be specified in the page source.
>So what do people think of this? Does it sound useful, or is it bloat?

First I think it's an good idea to leave the function in pmwiki, cause then 
you don't need any additional programs, rights etc.

Second, I think it would be a good idea to implement a bit of a workflow 
for publishing pages:
- An author creates / edits a page, he will use a special markup to mark 
this page to be published
- after saving pmwiki will put this change to the changelist (maybe another 
than recentchanges), where a reviewer (could be the author as well) can 
click a link (e.g. an action=review-link) to the page to review the changes 
and publish the page by using a button (will only be displayed with 
action=review) for executing the action=publish, the destination could be 
within the markup like Christian said. action=publish could be password 
protected as well and publishing a page could be logged in a page info field.

(Maybe this should all be put in a cookbook-recipe ?)

Please remember, that there already is an action=publish implemented in the 
cookbook, I mean the (very useful) function to create a document by 
scanning all "*"-items of a page


More information about the pmwiki-users mailing list