[pmwiki-users] Referencing Page Variables through multiple pages / use markup expressions as pagename base for page variable path / AuthUser htpasswd behavior

a.sonderhoff at gassi-tv.de a.sonderhoff at gassi-tv.de
Sun Nov 6 20:03:33 CST 2011

Dear Petko,

thanks for the help. Still more questions… 
1) Page1's title is set to something like “MyTitle” Page2's title is set to “{Page1$Title}” and Page3's title is set to “{Page2$Title}”. Is the expected behavior that Page3's title reads “{Page1$Title}” and not “MyTitle̦”? 
2) Is there a way to substring say {$Group} with markup expressions and use the returned string in a new pagename to retrieve a page variable (e. g. {NewGroup.{(substr("{$Group}" 10))}$Title}?
3) We are using AuthUser with some users in SiteAdmin/AuthUser and other users in a .htpasswd (defined in local/config.php). Whenever rights attributes from pages are changed, the users defined in SiteAdmin/AuthUser are immediately logged out by force. the users defined in the .htpasswd are not logged out and ignore the new rights attributes until they log out manually. Can someone explain why .htpasswd users are handled differently? To me this looks like a potential security threat.

Sorry for all the questions and thanks again for the great help so far.

Best regards,

ps: I've heard you, but I don't have the time to maintain a fork of PmWiki, even though if it would be more of a customized bundle. My guess would be that in order to generalize the PmWiki installation on GASSI TV to a non vodcast centered functionality, I would have to invest ~200 hours. As much as I would like to give something back to the PmWiki community, this is just more than I can handle on my own. And besides, most of the scripts and micro recipes are really written quick and dirty.
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax    +49 2238 963023
email  <a.sonderhoff at gassi-tv.de>

Aurikelweg 22
50259 Pulheim, NRW


On Nov/05, 2011, at 1800 , pmwiki-users-request at pmichaud.com wrote:

> Date: Sat, 5 Nov 2011 16:50:34 +0100
> From: Petko Yotov <5ko at 5ko.fr>
> To: pmwiki-users at pmichaud.com
> Subject: Re: [pmwiki-users] Page Variable for Original Author
> Message-ID: <201111051650.34908.5ko at 5ko.fr>
> Content-Type: Text/Plain;  charset="iso-8859-1"
> On Saturday 05 November 2011 14:51:10 a.sonderhoff at gassi-tv.de wrote:
>> Is there an easy way to have something like {$LastModifiedBy} for the
>> original author of a page, e. g. {$FirstModifiedBy} or something similar?
> See http://www.pmwiki.org/wiki/Cookbook/PageCreator.
>> Also, I am looking for a recipe which can automatically create multiple
>> pages with two clicks to set up the individual blogs...
> Again, I have not had the chance to review the recipe, but see NewGroupBox:
>  http://www.pmwiki.org/wiki/Cookbook/NewGroupBox
>> ps: on a side note and from my point of view, it would make sense to have
>> cms version of pmwiki bundled with the most important recipes (newpagebox
>> plus, htpasswdform, editattributes, movepage, cmsmode, extendconditional,
>> sitemap, etc.) and a customized EditForm (which already features dedicated
>> Title, Description and Keywords form fields) for those who use PmWiki as a
>> CMS rather than a WikiWikiWeb. throw in a CMS friendly skin and
>> default-config.php (with AuthUser enabled, etc.) and name the bundle
>> PmWiki CMS (or similar).
> At the moment Pm and I don't have the possibility to review and support all 
> recipes that might be used in a CMS installation. 
> But you can create a recipe page detailing how you use PmWiki as a CMS, which 
> recipes you recommend, and even support and offer for download your bundle. 
> Just don't call it "PmWiki CMS" or "PmCMS" as visitors may assume that Pm 
> wrote it or endorses it; a better name would be "Form based CMS" or something 
> less generic like "JoshCMS", etc.
> Other people have done it for blogs, see 
>  http://www.pmwiki.org/wiki/Category/Bundles
>  http://www.pmwiki.org/wiki/Cookbook/CMS
>  http://www.pmwiki.org/wiki/Category/WikipediaSuite
> Petko
> P.S. We all use PmWiki for content management, PmWiki *is* a content 
> management system. For example I use none of the recipes listed above for my 
> content management. :-) So, it depends on the needs of each team, or more 
> likely on the admin's (or management's) assumptions about these needs.

More information about the pmwiki-users mailing list