Re: [pmwiki-users] AsSpaced PTV (definition list)

[a . sonderhoff]

Dear Mark

As far as I know PTVs do allow spaces, e. g. (:somePTV: a string with spaces:). 
Or are you referring to PTV names?

Regards
Josh


On Jul/30, 2012, at 0846 , Mark Stephen Barralet wrote:

> As PTVs do not allow spaces I would like to format the output 'Name' of 
> definition list ( Name ) with the AsSpaced() function or other 
> method.
> 
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Empty Pages

[a . sonderhoff]

Hi Bernd,

are you using the latest version of PmWiki? This problem often occurs when your 
service provider updates the php server software and you are running an old 
version of PmWiki. Updating PmWiki usually solves the problem in that case. If 
it does not, can you check if the files in your pagestore still have all the 
content, e. g. if this is a rendering or a storage problem.

Best regards,
Josh


On Jul/16, 2012, at 1058 , Bernd Schatz wrote:

> Hello,
> 
> 
> All my pages are suddenly empty, 
> the history is still valid.
> But clicking on "restore" in the history page delivers
> always an empty text field.
> 
> If i edit a page i can make changes and take 
> them back with "restore" on the history page.
> 
> From the de-mailing list i got the following hints:
> 1) edit config.php 
> @ini_set('pcre.backtrack_limit',1000); 
> 
> ==> didnt solved the problem.
> 
> 
> 2) edit config.php:
> $EnableDiag = 1;
> $EnableStopWatch = 1;
> 
> ==> No special messages
> 
> 
> Can somebody give me hint to solve to problem or to 
> increase the logging to find the problem ?
> Is there a simply way to restore the pages from the 
> history with a bash or perl Skript ?
> 
> Greets and thx in advanced
>  Bernd
> 
> 
> 
> 
> 
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] search and replace over multiple / all pages

[a . sonderhoff]

hi clemens

if you want to have a really quick and dirty (and ultrafast) way to change the 
links, you could simply override them client side with jquery. of course this 
comes with the usual drawbacks (clients need to have javascript enabled and the 
additional overhead of loading the jquery framework).

for a pmwiki specific solution have a look at FoxTextReplace by hans bracker 
(http://www.pmwiki.org/wiki/Cookbook/FoxTextReplace).

take care
josh


On Jul/06, 2012, at 1429 , Clemens Gruber wrote:

> Hi, I have to change some URLs in an existing wiki with more than hundred 
> pages.
> 
> The old links is something like that
> http://example.com/aa//more-stuff.html?x=1&y=2&y=3
> 
> the new links
> http://example.com/hh//more-stuff.html?x=1
> 
> Have to do it on the wiki, no chance to do it on the remote server via 
> redirect / htaccess I do not need any documentation of this change (history) 
> so my idea is search and replace on file level all files under wiki.d .
> 
> Are there any side effects you think not do do it this way? Are there more 
> elegant ways (e.g. with documentation as diff) to do this?
> 
> Is there any script where I can specify old (search for) and new (replace 
> with) text parts
> 
> http://example.com/aa//more-stuff.html?x=1&y=2&y=3 | 
> http://example.com/hh//more-stuff.html?x=1
> http://example.com/aa//more-stuff.html?x=4&y=5&y=6 | 
> http://example.com/hh//more-stuff.html?x=4
> http://example.com/aa//more-stuff.html?x=7&y=8&y=9 | 
> http://example.com/hh//more-stuff.html?x=7
> 
> Regards
> Clemens
> 
> 
> 
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] output encoding problem iso latin 1 / utf-8

[a . sonderhoff]

just figured the problem out myself. my local config.php for the en field was 
missing $FarmD/ in the path for the utf-8 script. curiously this did not matter 
on the dev server though, probably because of differences in the mod_rewrite 
configuration.

sorry for bothering you guys.

take care
josh


On Jul/05, 2012, at 1448 , a.sonderh...@gassi-tv.de wrote:

> I just transferred a site from the dev to the live server and encountered a 
> strange behavior: on one field of the farm (the main field) the encoding is 
> perfectly as expected (utf-8, same as outputted by dev server), on the other 
> field it is partially utf-8 (e. g. ) and the rest renders in iso latin 
> 1 (dev server outputs utf-8).
> 
> differences between live and dev server (apart from deviations in apache 
> conf) are mainly different php versions (5.3.3 on live, 5.3.13-nmm1 on dev 
> server). is the encoding problem due to the often mentioned utf encoding 
> function bug in earlier php versions?
> 
> my installation is running on pmwiki-2.2.37
> 
> main field: http://www.comtrans.de/de
> other field: http://www.comtrans.de/en
> 
> thanks in advance for your help.
> 
> take care
> josh


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] output encoding problem iso latin 1 / utf-8

[a . sonderhoff]

I just transferred a site from the dev to the live server and encountered a 
strange behavior: on one field of the farm (the main field) the encoding is 
perfectly as expected (utf-8, same as outputted by dev server), on the other 
field it is partially utf-8 (e. g. ) and the rest renders in iso latin 1 
(dev server outputs utf-8).

differences between live and dev server (apart from deviations in apache conf) 
are mainly different php versions (5.3.3 on live, 5.3.13-nmm1 on dev server). 
is the encoding problem due to the often mentioned utf encoding function bug in 
earlier php versions?

my installation is running on pmwiki-2.2.37

main field: http://www.comtrans.de/de
other field: http://www.comtrans.de/en

thanks in advance for your help.

take care
josh
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] WikiSh t_string error

[a . sonderhoff]

the obvious next question would be: does the error message only occur on pages 
where WikiSh is used?


On Jul/04, 2012, at 0406 , adam overton wrote:

> hi there
> indeed, after digging around a little bit, it seems to be on only a few 
> pages, but not the whole site. that said, WikiSh isn't used on every page. 
> but maybe this suggests it's not a server thing, but a break in my code?
> thx
> 
> 
> 
> On 3 Jul 2012, at 4:33 AM, a.sonderh...@gassi-tv.de wrote:
> 
>> does this error pop up on every site in your wiki? or just a couple of them?
>> 
>> 
>> 
>> On Jul/03, 2012, at 0047 , adam overton wrote:
>> 
>>> 
>>> hi there!
>>> i've been away from one of my sites for awhile, not making any real 
>>> changes, and up popped the following message recently.
>>> 
>>> 
>>> Parse error: syntax error, unexpected T_STRING in 
>>> /home/mysite/public_html/pmwiki/cookbook/WikiSh.2010-06-09/WikiSh.php(2119) 
>>> : eval()'d code on line 1
>>> 
>>> Warning: Cannot modify header information - headers already sent by (output 
>>> started at 
>>> /home/mysite/public_html/pmwiki/cookbook/WikiSh.2010-06-09/WikiSh.php(2119) 
>>> : eval()'d code:1) in/home/mysite/public_html/pmwiki/pmwiki.php on line 1089
>>> 
>>> 
>>> 
>>> i had originally been using a version of WikiSh from 2008, so i tried 
>>> updating it to the latest 2010 version.
>>> 
>>> my question is which of the following scenarios is more likely in terms of 
>>> where an error like this is originating from:
>>> 
>>> a) could this problem could be from a change that my host has made to the 
>>> server (they never tell me when they upgrade, no matter how many times i 
>>> ask).
>>> 
>>> b) or is it more likely to be from data being processed by some WikiSh code 
>>> (i.e. maybe it's using something a user entered into a profile or page, 
>>> i.e. with odd characters or something).
>>> 
>>> 
>>> is one of those more likely?
>>> thanks a bunch for the advice!
>>> adam
>>> ___
>>> pmwiki-users mailing list
>>> pmwiki-users@pmichaud.com
>>> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>> 
> 


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] how to use HTML5

[a . sonderhoff]

Lars: I don’t think that Paul asked how to accomodate the needs of the editors 
of PmWiki’s original target audience, nor that he asked how to completely 
implement every aspect of HTML5 and YAML4 in PmWiki.

> I am reading a book on HTML5 and I am interested in creating a new skin , 
> based on YAML 4 (See http://yaml.de) . As part of that, I would like to use 
> HTML5 in the new skin. New tags likes , ,  and so on is 
> not difficult and can be easily embedded in the skin template, but is there 
> any way to get PMwiki to use the  and  tags in generating 
> page content instead of  ? How would I do that? 

Paul: In fact you can just go with your HTML5/YAML4 skin template and write 
some custom markup for  and  tags. The latter one might be a 
little more complicated, because you have to come up with a way on how to 
determine where  need to be closed again from within a regular 
expressions string. Are you familiar with defining custom markup in PmWiki?



On Jul/03, 2012, at 1504 , Lars Eighner wrote:

> On Tue, 3 Jul 2012, a.sonderh...@gassi-tv.de wrote:
> 
>> As discussed earlier in this mailing list, PmWiki is not just targetting
>> the average wiki use, but is also considered to be a full-fledged CMS.  As
>> such Paul?s question is totally legit and the use of HTML5 especially
>> considering, that its support will be essential soon,
> 
> It is not clear to me in what sense HTML5 will be essential soon.
> 
>> makes sense to me.  I also don?t think, that user experience will be
>> complicated by the introduction of HTML5/YAML4 to PmWiki.  In the end the
>> introduction of additional markup is just another possibility for advanced
>> users to declare structure within the content.  If PmWiki would only
>> target naïve users, there would not be (:table :), (:if :) and other
>> directives.
> 
> As it is, the XHTML TABLE element is not fully supported now (or did I miss
> the markup for THEAD etc.?)  There is plenty of (X)HTML not represented in
> the PmWiki core such as CITE, ADDRESS, and so forth.
> 
>> However, I agree with Lars, that implementing certain structural markup
>> will be more than just a little tweak.  That said, I never experienced any
>> problems generating HTML5 code with PmWiki, that do not use the new
>> structural tags (or YAML4 for that matter), by simply creating an HTML5
>> template.
> 
> It is hard to imagine any potential new flavors of HTML that would not be
> backward compatible with the core PmWiki markup.  However, it is also hard
> to imagine that PmWiki could entirely accommodate everything in any HTML
> flavor.
> 
> For example, HTML5 brings back a redefined I element. HTML5 I is probably
> more like what most users mean when they use wiki '', which is now
> translated EM.  What should be done?  Quietly change the PmWiki translation
> of '' to I, on the grounds that the new, improved I will most be compatible
> with what most users of existing wikis meant most of the time?  Insist ''
> means EM and find a new wikism for I?  Ignore the new, improved I
> altogether? Rip everything out to the walls, recast all the markup,
> abandoning existing installations?
> 
> Of course, most users, most of the time will be happy so long as '' comes
> out in an italic font because wikis are pretty much come down on the
> presentational side.
> 
> Everything except ignoring most of HTML5 would not require a lot of work but
> would also require a lot of soul-searching questions about what a wiki is,
> and so forth.  I don't think I am putting words in the author's mouth to say
> the PmWiki philosophy is very minimalist -- putting just essential stuff in
> the core, enough to get a wiki up, and leaving the rest for user extensions
> via the Cookbook.  That's why there is really no problem with declaring your
> documents HTML5 and making suitable adjustments in the template.
> 
> Then it is up to you how far you want to go in HTML5esque extentions.  You
> probably do want VIDEO.  If I is a better translation of what you want '' to
> mean than EM, that is simple enough.  Maybe you do not really need a markup
> for EM then because you never really mean EM when you use ''.
> 
> But the SECTION and ARTICLE elements within the body of an entry are not
> really very useful by themselves, and I think there is a good case to be
> made that in a wiki there will never be enough call for them to make the
> effort of an extension worthwhile.  Do you really want to write a book on
> one wiki page?  Or would the wiki way be to Group a book or a journal?
> 
> -- 
> Lars Eighner
> http://www.larseighner.com/index.html
> 8800 N IH35 APT 1191 AUSTIN TX 78753-5266


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] very strange behavior

[a . sonderhoff]

Hey Peter

Can you tell us how you set the password for the specific site/sites (whether 
it’s a sitewide password in config.php, etc.)

Groetjes
Josh


-- 
GASSI TV® brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  
web

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!

On Jul/03, 2012, at 1420 , Peter Gragert wrote:

> Hallo,
> An old wiki does nothing if I want to login with my admin password (one of  
> several)
> Installed the latest pmwiki:  it does not obey the password setting: opened 
> for editing without
> asking a password …
>  
> What may be the reason of this differen behavior, suggestions welcome
>  
> Peter
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] how to use HTML5

[a . sonderhoff]

> However, all wikis including PmWiki, are somewhat more presentational than
> the spirit of HTML specs call for.  A wiki is a compromise.  It is a quick
> and easy way for naïve users to write sort-of HTML without having to learn
> HTML.
> […]
> I think you need to ask why you want HTML 5. If you are not thinking of
> naïve users creating and editing pages, perhaps you should be thinking of
> writing documents in HTML 5 directly.

As discussed earlier in this mailing list, PmWiki is not just targetting the 
average wiki use, but is also considered to be a full-fledged CMS. As such 
Paul’s question is totally legit and the use of HTML5 especially considering, 
that its support will be essential soon, makes sense to me. I also don’t think, 
that user experience will be complicated by the introduction of HTML5/YAML4 to 
PmWiki. In the end the introduction of additional markup is just another 
possibility for advanced users to declare structure within the content. If 
PmWiki would only target naïve users, there would not be (:table :), (:if :) 
and other directives.

However, I agree with Lars, that implementing certain structural markup will be 
more than just a little tweak. That said, I never experienced any problems 
generating HTML5 code with PmWiki, that do not use the new structural tags (or 
YAML4 for that matter), by simply creating an HTML5 template.

Take care
Josh

-- 
GASSI TV® brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  
web

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!

On Jul/01, 2012, at 1850 , Lars Eighner wrote:

> On Sun, 1 Jul 2012, Paul Wiegmans wrote:
> 
>> Hello there,
>> 
>> Thank you very much to all you guys making PMwiki the wonderfull wiki system 
>> that it is now!
>> 
>> I am reading a book on HTML5 and I am interested in creating a new skin , 
>> based on YAML 4 (See http://yaml.de) . As part of that, I would like to use 
>> HTML5 in the new skin. New tags likes , ,  and so on is 
>> not difficult and can be easily embedded in the skin template,
> 
> So far so good. Like all wikis I have seen, PmWiki the wiki parts (stuff
> users can edit) translate wiki-ese into some essential HTML elements which
> are generally supported by HTMLs new and old.  There are some very minor
> adjustments in the markup for things such as whether empty elements like BR
> or IMG are explicitily close (whether it is > or  /> ), but otherwise you
> can pretty much determine what the kind of HTML of your documents in the
> template.
> 
> However, all wikis including PmWiki, are somewhat more presentational than
> the spirit of HTML specs call for.  A wiki is a compromise.  It is a quick
> and easy way for naïve users to write sort-of HTML without having to learn
> HTML.  For a wiki to capture the full range and nuance of HTML, wiki markup
> would have to be about as complex and difficult as HTML itself, and that
> would defeat the purpose.  (Besides opening the security holes of allow
> anonymous users to do things accidentally or on purpose that it is not wise
> to trust them to do.)
> 
>> but is there any way to get PMwiki to use the  and  tags
>> in generating page content instead of  ?  How would I do that?
> 
> In HTML 5, ARTICLE and SECTION are not intended to replace P.  While it
> would be a minor matter to add markup that would generate ARTICLE and
> SECTION tags, they are fairly useless without elements such as HGROUP,
> HEADER, FOOTER, and so forth.
> 
> So the answer is no.  It would not be a simple matter to make PmWiki (or any
> wiki at this stage) use these tags in an intelligent way.  Moreover, as
> mentioned above, the point of a wiki is to make markup simple which
> necessarily means the HTML a wiki produces cannot be pristine "best
> practices" HTML.  For example, the present PmWiki/DocumentationIndex
> contains such things as empty paragraphs (   ).  This is
> horrible (x)html, but it is the price of simplicity.
> 
> I think you need to ask why you want HTML 5. If you are not thinking of
> naïve users creating and editing pages, perhaps you should be thinking of
> writing documents in HTML 5 directly.
> 
> -- 
> Lars Eighner
> http://www.larseighner.com/index.html
> 8800 N IH35 APT 1191 AUSTIN TX 
> 78753-5266___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] WikiSh t_string error

[a . sonderhoff]

does this error pop up on every site in your wiki? or just a couple of them?



On Jul/03, 2012, at 0047 , adam overton wrote:

> 
> hi there!
> i've been away from one of my sites for awhile, not making any real changes, 
> and up popped the following message recently.
> 
> 
> Parse error: syntax error, unexpected T_STRING in 
> /home/mysite/public_html/pmwiki/cookbook/WikiSh.2010-06-09/WikiSh.php(2119) : 
> eval()'d code on line 1
> 
> Warning: Cannot modify header information - headers already sent by (output 
> started at 
> /home/mysite/public_html/pmwiki/cookbook/WikiSh.2010-06-09/WikiSh.php(2119) : 
> eval()'d code:1) in/home/mysite/public_html/pmwiki/pmwiki.php on line 1089
> 
> 
> 
> i had originally been using a version of WikiSh from 2008, so i tried 
> updating it to the latest 2010 version.
> 
> my question is which of the following scenarios is more likely in terms of 
> where an error like this is originating from:
> 
> a) could this problem could be from a change that my host has made to the 
> server (they never tell me when they upgrade, no matter how many times i ask).
> 
> b) or is it more likely to be from data being processed by some WikiSh code 
> (i.e. maybe it's using something a user entered into a profile or page, i.e. 
> with odd characters or something).
> 
> 
> is one of those more likely?
> thanks a bunch for the advice!
> adam
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Email Spam

[a . sonderhoff]

hi wade

check out this recipe: 
it’s simple and seems to work. we are using it for years now and our spam 
amount is reasonably low.

take care
josh

-- 
GASSI TV® brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  
web

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!

On Jun/13, 2012, at 0803 , Wade Hudson wrote:

> I'm receiving lots of spam via an email form.
> Any suggestions on what I can do to stop it>
> 
> Thanks,
> Wade
> 
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] is it possible to make (:keywords …:) accessible as a PageVariable?

[a . sonderhoff]

We are currently looking to create keyword related landing pages. As our 
editors have already entered all the necessary content in the (:keywords:) 
directive the most convenient way would be to use a (:pagelist 
$Keywords=*keyword*:). But then I found out that there is no PageVariable 
$Keywords.

Is there an easy way to make sure the (:keywords:) directive creates a 
PageVariable additionally to creating the html meta keyword tag? (Easy way as 
in reconfiguring the directive in config.php)

thx a lot
josh

-- 
GASSI TV® brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  
web

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmWiki cookbook recipe for Anti-virus scanning

[a . sonderhoff]

Long answer: Given the amount of interfacing and server side issues (especially 
file transfer), I don’t think that such a script could be easily written in a 
mere couple of hours. I am not even close to being a real programmer though, so 
maybe someone can figure out an easy way to do this in just a couple of hours. 
It stands to reason though, since this is an issue almost every collaboration 
centered web application has, that someone would have already done it, if it 
were that simple.

Short answer: If you really want to have this functionality, you will probably 
have to hire someone to develop this recipe for you.

-josh


On May/24, 2012, at 2318 , Al Louis Ripskis wrote:

> May 20, 2012 4:46 PM a.sonderh...@gassi-tv.de (Josh) wrote:
>> writing a PmWiki cookbook recipe, that submits uploaded files to an online 
>> virus >scanner.
> 
> Would this be a relatively simple challenge that somebody who knows what they 
> are doing could dash off in a couple of hours?
> Maybe we could make a game of it: who could be the first to come up with a 
> simple, functional recipe. It might be a welcome addition to PmWiki. 
> Al 
> 
> 
> -Original Message-
>> From: a.sonderh...@gassi-tv.de
>> Sent: May 20, 2012 4:46 PM
>> To: Al Louis Ripskis 
>> Cc: PmWiki Users 
>> Subject: Re: [pmwiki-users] Anti-virus scanning & PmWiki
>> 
>> Antivirus scanning is something you really don’t want a php script to 
>> perform. You would face script timeouts, slow performance, memory issues, 
>> etc. So unless you want to prepackage PmWiki with a server OS bundle and 
>> throw in apache, clamav, php-clamav, etc, it is not doable. There are far to 
>> many different web server and operating system configurations.
>> 
>> Unless it would be done without involving the local filesystem, e. g. 
>> writing a PmWiki cookbook recipe, that submits uploaded files to an online 
>> virus scanner. You would still have to deal with various timeout and timing 
>> issues, but this is actually something that could work. Given the amount of 
>> feedback to this thread, it’s probably not very high up on the priority list 
>> though.
>> 
>> Josh
>> 
>> 
>> On May/20, 2012, at 1937 , Al Louis Ripskis wrote:
>> 
>>> May 19, 2012 4:22 PM a.sonderh...@gassi-tv.de wrote:
>>> For all those interested in FOSS-based approaches to virus scanning for web 
>>> app servers, this is an article I found while researching whether there was 
>>> an easy solution to Al’s request:
 
>>> 
>>> The take home message that I got from examining the above site, et al. is 
>>> keep it simple: that it can be a "nightmare" and very expensive if one gets 
>>> into meta scanning and collaborative antivirus programs. Instead use one 
>>> program, such as AVG, and integrate it into PmWiki. The question is, is it 
>>> doable architecturally? 
>>> Al
>>> 
>>> -Original Message-
 From: a.sonderh...@gassi-tv.de
 Sent: May 19, 2012 4:22 PM
 To: tamouse mailing lists 
 Cc: PmWiki Users 
 Subject: Re: [pmwiki-users] Solved: How do you creating one, wiki-wide,
 Upload Directory on Local Site, not remote site?
 
 For all those interested in FOSS-based approaches to virus scanning for 
 web app servers, this is an article I found while researching whether 
 there was an easy solution to Al’s request:
 
 
 
 On May/19, 2012, at 0019 , tamouse mailing lists wrote:
 
> Hi, Al,
> 
> This can be automated, but it's not exactly a one or two-line script.
> I think others and myself discussed this a bit in your last thread
> about virus checking. If you aren't up for writing it yourself,
> perhaps you might engage the services of someone who can do it for
> you.
> 
> On Fri, May 18, 2012 at 3:46 PM, Al Louis Ripskis  
> wrote:
>> Many thanks to Josh, Gilles, Tamouse and JDD for helping me resolve this 
>> conundrum.
>> Since PmWiki architecture apparently doesn't permit to automate this 
>> process, here is how I'm dealing with it:
>> I manually (via FileZilla) transfer all the files From the PmWiki-wide 
>> uploads directory to my local C:\public_html\UnTestedUploads directory, 
>> where I can use my AVG anti-virus program to check out and delete the 
>> infected files, then process the uninfected files as necessary.
>> It would be nice to be able to do this automatically, but c'est la vie!
>> Thanks to all,
>> Al
>> 
>> -Original Message-
>>> From: a.sonderh...@gassi-tv.de
>>> Sent: May 17, 2012 3:21 PM
>>> To: Al Louis Ripskis 
>>> Cc: pmwiki-users 
>>> Subject: Re: [pmwiki-users] How do you creating one, wiki-wide, Upload 
>>> Directory on Local Site, not remote site?
>>> 
>>> Dear Al,
>>> 
>>> obviously this can’t work. your remote confi

Re: [pmwiki-users] Anti-virus scanning & PmWiki

[a . sonderhoff]

Antivirus scanning is something you really don’t want a php script to perform. 
You would face script timeouts, slow performance, memory issues, etc. So unless 
you want to prepackage PmWiki with a server OS bundle and throw in apache, 
clamav, php-clamav, etc, it is not doable. There are far to many different web 
server and operating system configurations.

Unless it would be done without involving the local filesystem, e. g. writing a 
PmWiki cookbook recipe, that submits uploaded files to an online virus scanner. 
You would still have to deal with various timeout and timing issues, but this 
is actually something that could work. Given the amount of feedback to this 
thread, it’s probably not very high up on the priority list though.

Josh


On May/20, 2012, at 1937 , Al Louis Ripskis wrote:

> May 19, 2012 4:22 PM a.sonderh...@gassi-tv.de wrote:
> For all those interested in FOSS-based approaches to virus scanning for web 
> app servers, this is an article I found while researching whether there was 
> an easy solution to Al’s request:
>> 
> 
> The take home message that I got from examining the above site, et al. is 
> keep it simple: that it can be a "nightmare" and very expensive if one gets 
> into meta scanning and collaborative antivirus programs. Instead use one 
> program, such as AVG, and integrate it into PmWiki. The question is, is it 
> doable architecturally? 
> Al
> 
> -Original Message-
>> From: a.sonderh...@gassi-tv.de
>> Sent: May 19, 2012 4:22 PM
>> To: tamouse mailing lists 
>> Cc: PmWiki Users 
>> Subject: Re: [pmwiki-users] Solved: How do you creating one, wiki-wide,  
>> Upload Directory on Local Site, not remote site?
>> 
>> For all those interested in FOSS-based approaches to virus scanning for web 
>> app servers, this is an article I found while researching whether there was 
>> an easy solution to Al’s request:
>> 
>> 
>> 
>> On May/19, 2012, at 0019 , tamouse mailing lists wrote:
>> 
>>> Hi, Al,
>>> 
>>> This can be automated, but it's not exactly a one or two-line script.
>>> I think others and myself discussed this a bit in your last thread
>>> about virus checking. If you aren't up for writing it yourself,
>>> perhaps you might engage the services of someone who can do it for
>>> you.
>>> 
>>> On Fri, May 18, 2012 at 3:46 PM, Al Louis Ripskis  
>>> wrote:
 Many thanks to Josh, Gilles, Tamouse and JDD for helping me resolve this 
 conundrum.
 Since PmWiki architecture apparently doesn't permit to automate this 
 process, here is how I'm dealing with it:
 I manually (via FileZilla) transfer all the files From the PmWiki-wide 
 uploads directory to my local C:\public_html\UnTestedUploads directory, 
 where I can use my AVG anti-virus program to check out and delete the 
 infected files, then process the uninfected files as necessary.
 It would be nice to be able to do this automatically, but c'est la vie!
 Thanks to all,
 Al
 
 -Original Message-
> From: a.sonderh...@gassi-tv.de
> Sent: May 17, 2012 3:21 PM
> To: Al Louis Ripskis 
> Cc: pmwiki-users 
> Subject: Re: [pmwiki-users] How do you creating one, wiki-wide, Upload 
> Directory on Local Site, not remote site?
> 
> Dear Al,
> 
> obviously this can’t work. your remote config.php will only affect the 
> remote settings and therefore only manipulate the remote file system.  to 
> achieve what you want to do, you will…
> 
> 1) …either have to mirror the site using something like rsync’ing with 
> the help of a cron job (and have all the problems discussed in an earlier 
> desktop virus scan software thread in this list, which you will probably 
> find in the mailing list archives)
> 
> 2) …or write some script that does what you need it to do (basically find 
> a way to interface the local and the remote sites).
> 
> 
> assuming your primary goal is not to move pages from one pmwiki instance 
> to another and have them cross-reference/load their pages, but rather 
> have a way to scan your uploaded files for malware/viruses/etc, you 
> should probably do one of those things:
> 
> a) if you need to run the scan from your workstation, rather than running 
> it on the server itself, the easiest way would be to mount the server 
> directory as a smb share on your local machine (if your remote and local 
> sites are not on the same network, you will probably have to use a vpn 
> tunnel for that). to explain how to do that is kind of out of the scope 
> of this mailing list, as it is not a PmWiki specific question, but more 
> of a general server administration/setup task.
> 
> b) you could consider installing a virus scanner (e. g. clamav-server) on 
> your remote site’s 

Re: [pmwiki-users] Solved: How do you creating one, wiki-wide, Upload Directory on Local Site, not remote site?

[a . sonderhoff]

For all those interested in FOSS-based approaches to virus scanning for web app 
servers, this is an article I found while researching whether there was an easy 
solution to Al’s request:



On May/19, 2012, at 0019 , tamouse mailing lists wrote:

> Hi, Al,
> 
> This can be automated, but it's not exactly a one or two-line script.
> I think others and myself discussed this a bit in your last thread
> about virus checking. If you aren't up for writing it yourself,
> perhaps you might engage the services of someone who can do it for
> you.
> 
> On Fri, May 18, 2012 at 3:46 PM, Al Louis Ripskis  wrote:
>> Many thanks to Josh, Gilles, Tamouse and JDD for helping me resolve this 
>> conundrum.
>> Since PmWiki architecture apparently doesn't permit to automate this 
>> process, here is how I'm dealing with it:
>> I manually (via FileZilla) transfer all the files From the PmWiki-wide 
>> uploads directory to my local C:\public_html\UnTestedUploads directory, 
>> where I can use my AVG anti-virus program to check out and delete the 
>> infected files, then process the uninfected files as necessary.
>> It would be nice to be able to do this automatically, but c'est la vie!
>> Thanks to all,
>> Al
>> 
>> -Original Message-
>>> From: a.sonderh...@gassi-tv.de
>>> Sent: May 17, 2012 3:21 PM
>>> To: Al Louis Ripskis 
>>> Cc: pmwiki-users 
>>> Subject: Re: [pmwiki-users] How do you creating one, wiki-wide, Upload 
>>> Directory on Local Site, not remote site?
>>> 
>>> Dear Al,
>>> 
>>> obviously this can’t work. your remote config.php will only affect the 
>>> remote settings and therefore only manipulate the remote file system.  to 
>>> achieve what you want to do, you will…
>>> 
>>> 1) …either have to mirror the site using something like rsync’ing with the 
>>> help of a cron job (and have all the problems discussed in an earlier 
>>> desktop virus scan software thread in this list, which you will probably 
>>> find in the mailing list archives)
>>> 
>>> 2) …or write some script that does what you need it to do (basically find a 
>>> way to interface the local and the remote sites).
>>> 
>>> 
>>> assuming your primary goal is not to move pages from one pmwiki instance to 
>>> another and have them cross-reference/load their pages, but rather have a 
>>> way to scan your uploaded files for malware/viruses/etc, you should 
>>> probably do one of those things:
>>> 
>>> a) if you need to run the scan from your workstation, rather than running 
>>> it on the server itself, the easiest way would be to mount the server 
>>> directory as a smb share on your local machine (if your remote and local 
>>> sites are not on the same network, you will probably have to use a vpn 
>>> tunnel for that). to explain how to do that is kind of out of the scope of 
>>> this mailing list, as it is not a PmWiki specific question, but more of a 
>>> general server administration/setup task.
>>> 
>>> b) you could consider installing a virus scanner (e. g. clamav-server) on 
>>> your remote site’s server and have it watch your uploads folder and 
>>> subdirs. this would definitely be a better solution, but users still won’t 
>>> get feedback why their file has suddenly disappeared. disappearing files is 
>>> still better than serving malware. and if you have to much spare time on 
>>> your hand you could even come up with a solution how to have clamav-server 
>>> tell pmwiki which files had to be removed.
>>> 
>>> c) you could come up with a new way for pmwiki to upload files (e. g. write 
>>> a new uploader) which automatically triggers your server’s antivirus 
>>> software and only successfully moves the file into place after it has been 
>>> cleared by the av software.
>>> 
>>> 
>>> again, this topic is not really related to PmWiki in the first place, since 
>>> it’s a problem basically every content management system has. you might 
>>> have better luck searching the web for a more general solution to this 
>>> problem, or maybe ask this question in a more generalized way on 
>>> stackoverflow.
>>> 
>>> Josh
>>> 
>>> On May/17, 2012, at 1957 , Al Louis Ripskis wrote:
>>> 
 May 17, 2012 8:57 AM a.sonderh...@gassi-tv.de; Josh wrote:
 $UploadDir = "C:/public_html/pmwiki/uploads";
 $UploadUrlFmt = 
 "http://www.politicaltransformation.org/htdocs/pmwiki/uploads";;
> Did you put these lines in your local or remote site’s local/config.php?
> Can you clarify what your local and remote sites actually are?
 The remote site is my politicaltransformation.org PmWiki and that's the 
 config.php file that I inserted the above two lines of script.
 Now my local site is the computer I'm operating from that has Windows XP 
 Home OS.
 Thanks again,
 Al
 
> On May/17, 2012, at 1414 , Al Louis Ripskis wrote:
> 
>> May 16, 2012 10:11 PM Tamouse wrote: Do I understand this correctly.Let 
>> me know if that's the situatio

Re: [pmwiki-users] edit passwd?

[a . sonderhoff]

hi jdd

can you tell me the page’s attributes? (just add ?action=attr to the url and 
you will get the attributes)

josh


On May/18, 2012, at 0832 , jdd wrote:

> Hello :-)
> 
> I have this in my config.php:
> 
> $DefaultPasswords['admin'] = crypt('x');
> $DefaultPasswords['edit'] = crypt('');
> 
> I can edit a given page with the admlin passwd, but not with the edit pass
> 
> what is wrong?
> 
> (I could solve the problem changing the passwd online for this page, but need 
> to understand
> 
> thanks
> jdd
> 
> 
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] How do you creating one, wiki-wide, Upload Directory on Local Site, not remote site?

[a . sonderhoff]

Dear Al,

obviously this can’t work. your remote config.php will only affect the remote 
settings and therefore only manipulate the remote file system.  to achieve what 
you want to do, you will…

1) …either have to mirror the site using something like rsync’ing with the help 
of a cron job (and have all the problems discussed in an earlier desktop virus 
scan software thread in this list, which you will probably find in the mailing 
list archives)

2) …or write some script that does what you need it to do (basically find a way 
to interface the local and the remote sites).


assuming your primary goal is not to move pages from one pmwiki instance to 
another and have them cross-reference/load their pages, but rather have a way 
to scan your uploaded files for malware/viruses/etc, you should probably do one 
of those things:

a) if you need to run the scan from your workstation, rather than running it on 
the server itself, the easiest way would be to mount the server directory as a 
smb share on your local machine (if your remote and local sites are not on the 
same network, you will probably have to use a vpn tunnel for that). to explain 
how to do that is kind of out of the scope of this mailing list, as it is not a 
PmWiki specific question, but more of a general server administration/setup 
task.

b) you could consider installing a virus scanner (e. g. clamav-server) on your 
remote site’s server and have it watch your uploads folder and subdirs. this 
would definitely be a better solution, but users still won’t get feedback why 
their file has suddenly disappeared. disappearing files is still better than 
serving malware. and if you have to much spare time on your hand you could even 
come up with a solution how to have clamav-server tell pmwiki which files had 
to be removed.

c) you could come up with a new way for pmwiki to upload files (e. g. write a 
new uploader) which automatically triggers your server’s antivirus software and 
only successfully moves the file into place after it has been cleared by the av 
software.


again, this topic is not really related to PmWiki in the first place, since 
it’s a problem basically every content management system has. you might have 
better luck searching the web for a more general solution to this problem, or 
maybe ask this question in a more generalized way on stackoverflow.

Josh

On May/17, 2012, at 1957 , Al Louis Ripskis wrote:

> May 17, 2012 8:57 AM a.sonderh...@gassi-tv.de; Josh wrote:
> $UploadDir = "C:/public_html/pmwiki/uploads";
> $UploadUrlFmt = 
> "http://www.politicaltransformation.org/htdocs/pmwiki/uploads";;
>> Did you put these lines in your local or remote site’s local/config.php?
>> Can you clarify what your local and remote sites actually are?
> The remote site is my politicaltransformation.org PmWiki and that's the 
> config.php file that I inserted the above two lines of script.
> Now my local site is the computer I'm operating from that has Windows XP Home 
> OS.
> Thanks again,
> Al
> 
>> On May/17, 2012, at 1414 , Al Louis Ripskis wrote:
>> 
>>> May 16, 2012 10:11 PM Tamouse wrote: Do I understand this correctly.Let me 
>>> know if that's the situation so I can respond:
 a) politicaltransformation.org is hosted on a remote site? YES
 b) you are expecting the remote site to understand a path on your local 
 machine? YES
 c) you are further expecting the wiki software to deliver a file to a user 
 by cross-loading it from your local machine? NO. Deliver the user uploaded 
 files to Local Upload directory so they can be checked out by my AVG virus 
 program for viruses, etc..If this is not possible, is there another way to 
 check out automatically whether the uploaded files are infected?
>>> Thanks very much,
>>> Al
>>> 
>>> -Original Message-
 From: tamouse mailing lists 
 Sent: May 16, 2012 10:11 PM
 To: Al Louis Ripskis 
 Cc: pmwiki-users 
 Subject: Re: [pmwiki-users] How do you creating one, wiki-wide, Upload 
 Directory on Local Site, not remote site?
 
 On Wed, May 16, 2012 at 1:43 PM, Al Louis Ripskis wrote:
> According to PmWiki Upload Administration instructions all you suppose to 
> do
> is put this or equivalent in you Config file::
> 
> $UploadDir = "/home/foobar/public_html/uploads";
> $UploadUrlFmt = "http://example.com/~foobar/uploads";;
> 
> When I translate the above to my Windows XP OS needs, I come with this:
> 
> $UploadDir = "C:/public_html/pmwiki/uploads";
> $UploadUrlFmt =
> "http://www.politicaltransformation.org/htdocs/pmwiki/uploads";;
> 
> But all this does is create another upload directory on the remote site.
> I would like to create one, site-wide directory on the local site.
> How do I do that?
 
 Do I understand this correctly:
 
 a) politicaltransformation.org is hosted on a remote site?
 b) you are expecting the remote site to understand a path

Re: [pmwiki-users] How do you creating one, wiki-wide, Upload Directory on Local Site, not remote site?

[a . sonderhoff]

> >> $UploadDir = "C:/public_html/pmwiki/uploads";
> >> $UploadUrlFmt =
> >> "http://www.politicaltransformation.org/htdocs/pmwiki/uploads";;

did you put these lines in your local or remote site’s local/config.php?

josh


On May/17, 2012, at 1414 , Al Louis Ripskis wrote:

> May 16, 2012 10:11 PM Tamouse wrote: Do I understand this correctly.Let me 
> know if that's the situation so I can respond:
> >a) politicaltransformation.org is hosted on a remote site? YES
> >b) you are expecting the remote site to understand a path on your local 
> >machine? YES
> >c) you are further expecting the wiki software to deliver a file to a user 
> >by cross-loading it from your local machine? NO. Deliver the user uploaded 
> >files to Local Upload directory so they can be checked out by my AVG virus 
> >program for viruses, etc..If this is not possible, is there another way to 
> >check out automatically whether the uploaded files are infected?
> Thanks very much,
> Al
> 
> -Original Message-
> >From: tamouse mailing lists 
> >Sent: May 16, 2012 10:11 PM
> >To: Al Louis Ripskis 
> >Cc: pmwiki-users 
> >Subject: Re: [pmwiki-users] How do you creating one, wiki-wide, Upload 
> >Directory on Local Site, not remote site?
> >
> >On Wed, May 16, 2012 at 1:43 PM, Al Louis Ripskis wrote:
> >> According to PmWiki Upload Administration instructions all you suppose to 
> >> do
> >> is put this or equivalent in you Config file::
> >>
> >> $UploadDir = "/home/foobar/public_html/uploads";
> >> $UploadUrlFmt = "http://example.com/~foobar/uploads";;
> >>
> >> When I translate the above to my Windows XP OS needs, I come with this:
> >>
> >> $UploadDir = "C:/public_html/pmwiki/uploads";
> >> $UploadUrlFmt =
> >> "http://www.politicaltransformation.org/htdocs/pmwiki/uploads";;
> >>
> >> But all this does is create another upload directory on the remote site.
> >> I would like to create one, site-wide directory on the local site.
> >> How do I do that?
> >
> >Do I understand this correctly:
> >
> >a) politicaltransformation.org is hosted on a remote site?
> >b) you are expecting the remote site to understand a path on your local 
> >machine?
> >c) you are further expecting the wiki software to deliver a file to a
> >user by cross-loading it from your local machine?
> >
> >Let me know if that's the situation so I can respond.
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Keeping links while moving files between different PmWiki sites

[a . sonderhoff]

Dear Patrick

I am not aware of any out-of-the-box solution to your problem. Are all the 
pages you are moving in the same group? Or are all the pages referred to from 
the moved pages in the same group?

Groetjes
Josh


On May/16, 2012, at 0848 , Patrick Van Cauteren wrote:

> 
> 
> I am moving a subset of a Wiki (pmwiki) from one site to another. Both sites 
> are on the same server (assume they're called Wiki1 and Wiki2).
> The problem is that some of the pages that I am moving from Wiki1 to Wiki2 
> refer to pages which should remain on Wiki1.
> Is there a method to tell PmWiki (the Wiki2 installation) that it should also 
> look in Wiki1 if the file is not found in Wiki2?
>  
> Patrick
> 
> 
> Patrick Van Cauteren
> Senior Software Architect
> 
> pvancaute...@ompartners.com
> 
> OM Partners
> Koralenhoeve 23
> 2160 Wommelgem
> Belgium
> 
> Phone: +32 3 650 22 11, Fax: +32 3 650 22 90
> 
> 
> http://www.ompartners.com
> 
> 
> 
>  
> IMPORTANT NOTICE
> The information in this e-mail and any attachments is intended for the 
> addressee only. The contents do not represent the opinion of OM Partners n.v. 
> or any of its affiliates except to the extent that it relates to their 
> official business. If you receive this in error, please contact the sender 
> and delete the material from any computer.
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Question about RACT

[a . sonderhoff]

Hi Mingyuan

Apparantly the RACT Toolbox page 
() uses PmWiki as their CMS, 
which led you to post your question to the pmwiki-users mailing list. This 
mailing list is only about the PmWiki CMS and _NOT_ the content of every site 
which uses PmWiki as their underlying CMS. There is probably no one here who 
can help you with your questions. I suggest you contact the author(s) of the 
RACT Toolbox software.

Best regards
Josh




On May/16, 2012, at 2355 , cenmmy wrote:

> Dear all,
> Thank you for reading my email.I am writing to ask a question about the 
> ract_ToolBox. According to the ract-manual, the “feaslmi” function can be 
> used to find the probabilistically feasible solution of LMIs.My question is 
> how to use the “feaslmi” function to deal with that when the LMIs have a few 
> unknown variable?
> Thank you very much for your help.
> 
> Best Wishes.
> Mingyuan Chen
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Enabling autosave

[a . sonderhoff]

Hi Pranav

just edit yout Site.EditForm page and insert (:autosave:) on its own line to 
the content. Press save and you are already on your way.

Take care
Josh


On May/12, 2012, at 1557 , Pranav Lal wrote:

> Hi all,
> 
> I am trying to enable autosave from
> http://www.pmwiki.org/wiki/Cookbook/AutoSave
> 
> I have completed most of the steps except the following.
> .add the directive (:autosave:) to your edit form, by default located at
> Site.EditForm
> 
> What am I supposed to do in the above step?
> Pranav
> 
> 
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] using PTVs from pagelists in skin scripts (or how to register a new PV)

[a . sonderhoff]

Hi Peter,

thanks a lot for your advice. I had a look at Hans’ powertools recipe, but then 
opted for the quick and dirty solution to use (:setSomeVar {=$FullName}:) in 
the pagelist template (together with the markup to translate the directive into 
a global variable) to work around the PTV limitations.

> if (preg_match_all($pat, 
> IsEnabled($PCache[$pagename]['=preview'],@$page['text']), 
>   $match, PREG_SET_ORDER))
>   foreach($match as $m) {
> $t = preg_replace("/\\{\\$:{$m[2]}\\}/", '', $m[3]);
> $pc["=p_{$m[2]}"] = Qualify($pagename, $t);
>   }

Thanks for pointing out this section. Now I do understand, why it’s not 
possible to use PTVs in a pagelist.

Take care
josh



On May/12, 2012, at 1004 , Peter Bowers wrote:

> On Sat, May 12, 2012 at 9:20 AM,  wrote:
> I rewrote the template script into a cookbook script and included it in 
> config.php as Peter suggested. no luck there. apparently the problem is about 
> setting PTVs from within a pagelist.
> 
> Sorry, I wasn't clear in my earlier email.  I wasn't suggesting that you take 
> your existing script (step #2) and put it in config.php and leave the rest of 
> the steps with the pagelist etc.  I was suggesting that you take steps #1 
> through 6 (the whole thing) and place it in a single markup:
> 
> (:mess_with_latestpage groupname varname:)
> 
> Then your script (triggered by the (:mess_with_latestpage ...:) markup) will 
> find the latest page in that group and output all the various markup you are 
> wanting to do.  Since it is a single markup rule you can easily put it early 
> enough to occur prior to the (:title ...:) markup and etc.
> 
> Be aware that you cannot dynamically create PTV-setting markup, so you'll 
> have to have some other way of doing that.if that's something you need...
> 
> For running a pagelist from PHP, check out how Hans did it in powertools.
> 
> -Peter


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] using PTVs from pagelists in skin scripts (or how to register a new PV)

[a . sonderhoff]

Dear Hans,

> I don't understand why you want to include a php script that way or
> any other way inside the tmpl file. The tmpl file is processed late,
> and you bound to have problems with the script.

The script is my own html5 video with flash fallback script. It serves the same 
mp4 as html5 video to safari and mobilesafari browsers and with a flash player 
to all others. I like to bundle it with the skin, because it’s an essential 
part of the skin. It’s not just _a_ player, it’s _the_ primary content object. 
To me it’s more elegant to have the script referenced in the skin’s template, 
because it’s not intended to be available as a markup to editors. Also I was 
counting on the tmpl file to be processed as late as possible.


> How do you load your custom skin?

config.php: $Skin = "someSkin";
and in /someSkin/someSkin.php: LoadPageTemplate($pagename, 
"$SkinDir/someSkin-someTemplate.tmpl");


> Please include the script in the same way as you would set your skin,

I rewrote the template script into a cookbook script and included it in 
config.php as Peter suggested. no luck there. apparently the problem is about 
setting PTVs from within a pagelist.

why does (:var: {=$:var}:) produce an epic fail, while (:title {=$:var}:) just 
works fine?


Thanks for helping me clarify the problem.

Take care,
Josh


> Hi Josh,
> 
>> Saturday, May 12, 2012, 7:11:23 AM, you wrote:
>> I will also look into triggering the script as a php markup script
>> ( instead of
>> ). hopefully this workaround will solve
>> the order issues by having PmWiki figure them out.
>> 
> 
> Please include the script in the same way as you would set your skin,
> i.e. in config.php or a Group.php or Group.Name.php file in the
> local/ directory to load the skin and script for a page group "Group"
> or for a single page "Group.Name".
> How do you load your custom skin?
> 
> Best regards,
> Hans   
> www.softflow.co.uk

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] using PTVs from pagelists in skin scripts (or how to register a new PV)

[a . sonderhoff]

Peter, thx so much for your reply. I was suspecting that much. That’s why I 
tried to write some markup to actually register a real PV (with <{$var} 
priority), but I couldn’t get that to work beyond the scope of a single page.

As far as I can tell, the problem breaks down this single question: 
Why can a php script referenced in the skin’s .tmpl file access PTVs and PVs 
set by (:var: :) and (:var :) but not when those are within a pagelist? Is 
there a way to tell the script to run ‘>pagelist’ (after all pagelists have 
been processed)?

I will also look into triggering the script as a php markup script 
( instead of ). hopefully 
this workaround will solve the order issues by having PmWiki figure them out.

Josh


On May/11, 2012, at 2356 , Peter Bowers wrote:

>> On Fri, May 11, 2012 at 10:29 AM,  wrote:
>> Here is my problem. #1 and #2 are for further background only. I am 
>> basically trying to use PVs and PTVs of the newest page in a certain group 
>> when visiting another page in another group within a script referenced by 
>> the active skin’s .tmpl file by using a pagelist.
>> 
>> 1) I have a simple custom skin which loads a script into a div with 
>> 
>> 
>> 2) the somescript.php basically does this:
>> 
>> > global $pagename;
>> $imageLink = PageVar($pagename,'$:image');
>> echo MarkupToHTML($pagename, "Attach:$imageLink");
>> 
>> 3) (:image: …:) is set on SomeGroup.SomePage
>> 
>> 4) I have a pagelist in SomeOtherGroup.SomeOtherPage which basically does 
>> this:
>> 
>> (:pagelist fmt=somePagelistFmt group=SomeGroup count=1 order=-ctime 
>> name=-*Recent*,-GroupAttributes:)
>> 
>> 5) #somePageListFmt is defined in LocalTemplates as
>> 
>> [[#somePageListFmt]]
>> (:template each:)
>> (:title {=$Title}:)
>> (:image: {=$:image}:)
>> ! {=$Title}
>> Attach:{=$:image}
>> [[#somePageListFmtend]]
>> 
>> 6) what happens on SomeOtherGroup.SomeOtherPage is, that {$Title} is set by 
>> the pagelist while {$:image} is not. both are displayed correctly in the 
>> further output of the pagelist template. this is driving me mad (already 
>> tried to circumvent this with a real PV, which failed due to my lack of 
>> understanding of PmWiki’s $FmtPV[] / setProperty()). any ideas on what I am 
>> doing wrong?
> 
> Ooh, that made my head hurt just trying to figure out where everything was 
> going.  You've got so many things going on there which will require *very* 
> complex  rule ordering and may be impossible.  I would strongly recommend 
> simply writing a custom markup that does what you need in PHP rather than 
> trying to get a pagelist to run based on certain variables which in turn sets 
> other variables and creates attachment and image markup...  It may well be 
> possible, but you're going to have to look at the order of the rules very 
> closely -- I'm taking a guess that this is what is causing your solution to 
> not work.  Assuming you can get it working I think it will be carefully 
> "balanced" and every time you make a little change to your configuration (esp 
> anything which affects the rules) you will "knock it off balance" again..
> 
> -Peter
> 


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] using PTVs from pagelists in skin scripts (or how to register a new PV)

[a . sonderhoff]

Here is my problem. #1 and #2 are for further background only. I am basically 
trying to use PVs and PTVs of the newest page in a certain group when visiting 
another page in another group within a script referenced by the active skin’s 
.tmpl file by using a pagelist.

1) I have a simple custom skin which loads a script into a div with 


2) the somescript.php basically does this:


web

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] how to access configuration variables from skin scripts

[a . sonderhoff]

> Sorry for my late reply. You are using PmWiki in unusual ways so I had to find
> some time to test the thing.

guilty as charged ^^


> You can set this line in pub/skins/yourskin/yourskin.php if you declare the 4
> variables global.

this does the trick. is there a way to additionally suppress the ?

Petko, thanks a lot for all your help so far.

Best regards / Mit freundlichem Gruß,

i. A. Josh Sonderhoff
Purchasing Manager

-- 
cell: +49 1511 5794189
mail: j...@movingpixies.com
web:  http://movingpixies.com

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!



On Mar/18, 2012, at 1800 , pmwiki-users-requ...@pmichaud.com wrote:

> Sorry for my late reply. You are using PmWiki in unusual ways so I had to find
> some time to test the thing.
> 
> a.sonderh...@gassi-tv.de writes:
>>> $HandleBrowseFmt = array(&$PageStartFmt, &$PageRedirectFmt, &$PageEndFmt);
>> This works as well, though not exactly like I was hoping to use it. I was  
>> hoping to use a directive like this in the skin template?s php file (where I 
>>  
>> have all the skin related conditional stuff).
> 
> You can set this line in pub/skins/yourskin/yourskin.php if you declare the 4
> variables global.
> 
>> In which order are config.php and skin.php(1) evaluated? 
> config.php is used very early, long before a skin-template.php file.
> 
>> E. g. can I define a global variable in skin.php to conditionally  
>> use the var in config.php? 
> 
> No.
> 
>> Or are there other ways to achieve this?
> 
> I hope that I have correctly understood your need and I hope that the above  
> line in a template-skin.php file with a global declaration will work for you.
> 
> Petko


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] text and image as link content in same [[ ]]

[a . sonderhoff]

Dear Dominique,

Thanks for your reply. I had a look at the recipe’s page 
(http://www.pmwiki.org/wiki/Cookbook/DomTT) and could not quite find the 
functionality I am looking for. The DomTT recipe does not allow me to put an 
image and text content in the same [[ ]] pmwiki link markup.


Best regards / Mit freundlichem Gruß,

i. A. Josh Sonderhoff
Purchasing Manager

-- 
cell: +49 1511 5794189
mail: j...@movingpixies.com
web:  http://movingpixies.com

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!

On Mar/19, 2012, at 0655 , Dominique Faure wrote:

> On Sun, Mar 11, 2012 at 13:44,   wrote:
>> Hi
>> 
>> I am trying to put some text and an image in the same link markup:
>> [[ linktarget | some text goes here http://host/image.ext ]]
>> 
>> This is necessary in order to trigger the hover state of the text when the 
>> mouse cursor moves over the image. This also why I cannot use separate link 
>> markups, e. g. text in another link wikimarkup than the image.
>> 
>> Can this be achieved using readily available pmwiki markup or do I have do 
>> define a custom markup for that in config.php?
> 
> Hi,
> Feel free to have a try on the DomTT recipe, which implement the kind
> of features you're looking for.
> 
> -- 
> Dominique


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] text and image as link content in same [[ ]]

[a . sonderhoff]

Hi

I am trying to put some text and an image in the same link markup:
[[ linktarget | some text goes here http://host/image.ext ]]

This is necessary in order to trigger the hover state of the text when the 
mouse cursor moves over the image. This also why I cannot use separate link 
markups, e. g. text in another link wikimarkup than the image.

Can this be achieved using readily available pmwiki markup or do I have do 
define a custom markup for that in config.php?

Thanks
Josh


-- 
GASSI TV® brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  
web

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] how to access configuration variables from skin scripts

[a . sonderhoff]

Dear Petko

Apologies for my delayed reply and many thanks for your answers. Your hint with 
the globals declaration works great (I did try to access the globals with the 
globals array only and not by declaring them global in my script, which was my 
error).

> $HandleBrowseFmt = array(&$PageStartFmt, &$PageRedirectFmt, &$PageEndFmt);
This works as well, though not exactly like I was hoping to use it. I was 
hoping to use a directive like this in the skin template’s php file (where I 
have all the skin related conditional stuff). 

My template basically has a primary content div which shows an image and some 
text extracted from PTVs and a sidebar content div into which the sidebar 
(basically a pagelist with pagination) is AJAXed:
› The sidebar has its own tmpl file which will either use  or 
 directive to render the contents
› The primary content’s tmpl does not use the  directive at all
› all actions other than browse obviously use a tmpl which needs 

So I can either 
A) conditionally implement ‘$HandleBrowseFmt = array(&$PageStartFmt, 
&$PageRedirectFmt, &$PageEndFmt);’ in the config.php to show up only on action 
== browse and use  directive to 
circumvent the  directive being neutralized in the config.php or
B) find some way to do place the conditional logic in the template’s .php

B sounds like the cleaner solution to me, but I am lacking knowledge of 
PmWiki’s processing chain. In which order are config.php and skin.php(1) 
evaluated? E. g. can I define a global variable in skin.php to conditionally 
use the var in config.php? Or are there other ways to achieve this?

Thanks a lot
Josh



(1) skin.php in this context is a placeholder for the skin templates primary 
php file



-- 
GASSI TV® brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  
web

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!


On Feb/26, 2012, at 1900 , pmwiki-users-requ...@pmichaud.com wrote:

> Date: Sun, 26 Feb 2012 12:18:28 +0100
> From: 5...@5ko.fr
> To: pmwiki-users@pmichaud.com
> Subject: Re: [pmwiki-users] how to access configuration variables from
>   skin scripts
> Message-ID: 
> Content-Type: text/plain; format=flowed; delsp=yes; charset="UTF-8"
> 
> a.sonderh...@gassi-tv.de writes:
>> 1) Basically I have a lot of  in my tmpl to fire the  
>> scripts that merge the page variables and PTVs with the html/css. The  
>> functions described in the link given above work just fine, configuration  
>> variables (such as $FarmD, $SkinDirUrl, etc.) however are not accessible.
> 
> Add at the beginning of your scripts
> 
>  global $FarmD, $SkinDirUrl;
> 
>> a limitation as I do not need the output produced by  in all  
>> of the tmpl files ...   Omitting the  
>> PageText special directive results in PmWiki outsmarting me and inserting  
>> the PageText content just before the  tag. Is there any way to force  
>> PmWiki to not output the PageText in certain tmpl?s?
> 
> You can add this in config.php - possibly conditionnally :
> 
>  $HandleBrowseFmt = array(&$PageStartFmt, &$PageRedirectFmt, &$PageEndFmt);
> 
> Petko


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] how to access configuration variables from skin scripts

[a . sonderhoff]

hi

I am currently working on a skin with multiple templates, where most of the 
content is loaded from page variables (using the functions described in 
http://www.pmwiki.org/wiki/Cookbook/Functions).

1) Basically I have a lot of  in my tmpl to fire the 
scripts that merge the page variables and PTVs with the html/css. The functions 
described in the link given above work just fine, configuration variables (such 
as $FarmD, $SkinDirUrl, etc.) however are not accessible. Is there a function 
readily available to access these variables? My search in the documentation 
index did not spawn any helpful results so far.

2) The skin template file format states that three directives are REQUIRED in a 
template (HTMLHeader, PageText, HTMLFooter). In my case that is kind of a 
limitation as I do not need the output produced by  in all of 
the tmpl files. As a dirty workaround I could restructure the site to construct 
a lot of the layout in PmWiki markup, but this will eventually introduce a lot 
of redundant code to my site (yes I know, that I could come up with a custom 
markup to remove the redundancy to a minimum, but this single line of 
redundancy would remain no matter what). Omitting the PageText special 
directive results in PmWiki outsmarting me and inserting the PageText content 
just before the  tag. Is there any way to force PmWiki to not output the 
PageText in certain tmpl’s?

thanks
josh


-- 
GASSI TV® brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  
web

moving pixies GmbH
Aurikelweg 22
DE-50259 Pulheim
Geschäftsführer: Daniel Sonderhoff
Amtsgericht Köln, HRB 74273


Save the world — Don't print this e-mail!


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Password protection not working

[a . sonderhoff]

yue, can you tell me what 5.3 version you are using? 5.3.7?
according to  there is a confirmed md5 
crypt specific to php 5.3.7. if you are using 5.3.7, you should upgrade to 
5.3.7-p11 or 5.3.8.

josh

-- 
ALJOSCHA SONDERHOFF
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  

GASSI-TV
Aurikelweg 22
50259 Pulheim, NRW
GERMANY

http://gassi-tv.de

On Nov/10, 2011, at 2117 , a.sonderh...@gassi-tv.de wrote:

> checked the supplied link. most interestingly Main.HomePage?action=attr shows 
> the edit password set by site. still (:if auth edit:) evaluates to true for 
> non-logged in users while (:if auth admin:) evaluates to false.
> 
> can you post the contents of your entire local/config.php? (minus clear 
> passwords, of course)
> sadly my servers are running php versions 5.2.6 and 5.2.12, so I cannot 
> verify if this is a 5.3 related problem. to verify or falsify that faulty 
> crypt implementation in php 5.3 theory, you could use md5 or sha-1 encrypted 
> passwords stored in a .htpasswd (see the Passwd section in 
> http://www.pmwiki.org/wiki/Cookbook/AuthUser).
> 
> josh
> 
> -- 
> ALJOSCHA SONDERHOFF
> brand & marketing
> 
> office +49 2238 4629519
> mobile +49 1511 5794189
> fax+49 2238 963023
> email  
> 
> GASSI-TV
> Aurikelweg 22
> 50259 Pulheim, NRW
> GERMANY
> 
> http://gassi-tv.de
> 
> On Nov/10, 2011, at 1900 , pmwiki-users-requ...@pmichaud.com wrote:
> 
>> Date: Thu, 10 Nov 2011 11:13:14 -0500
>> From: "Sun, Yue" 
>> To: "'pmwiki-users@pmichaud.com'" 
>> Subject: [pmwiki-users] Password protection not working
>> Message-ID:
>>  <814d48ca046ee04dba96c426b6ceacb112bbcf6...@xcluster.vgn.cty>
>> Content-Type: text/plain; charset="us-ascii"
>> 
>> Hi,
>> 
>> We have a pmwiki site (version 2.2.0) that has been up for a few years. 
>> Recently we upgraded to RedHat 5 and PHP 5.3.7, after that the password 
>> protection is not working any more. To help figure out the problem, I've set 
>> up a new pmwiki 2.2.34, and use the simple config file with
>> 
>> $DefaultPasswords['edit'] = crypt('operations');
>> 
>> and
>> 
>> $EnableDiag = 1;
>> 
>> but still the Edit is open to everyone and never got a password prompt. When 
>> I changed $DefaultPasswords['edit'] ='@lock' and the 
>> password was prompted. I notice there are some discussions about the new 
>> crypt() in php 5.3 and doubt if it's related to the issue I am having. Here 
>> is the test pmwiki I set up 
>> http://newsletter.vaughanpl.info/pmwiki/pmwiki.php. Can someone provide a 
>> help? Do I have to downgrade to php 5.2?
>> 
>> Any comments or suggestions would be appreciated!!
>> 
>> Yue
>> 
>> 
>> This e-mail, including any attachment(s), may be confidential and is 
>> intended solely for the attention and information of the named addressee(s). 
>> If you are not the intended recipient or have received this message in 
>> error, please notify me immediately by return e-mail and permanently delete 
>> the original transmission from your computer, including any attachment(s). 
>> Any unauthorized distribution, disclosure or copying of this message and 
>> attachment(s) by anyone other than the recipient is strictly prohibited.
>> -- next part --
>> An HTML attachment was scrubbed...
>> URL: 
>> 
> 


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Password protection not working

[a . sonderhoff]

checked the supplied link. most interestingly Main.HomePage?action=attr shows 
the edit password set by site. still (:if auth edit:) evaluates to true for 
non-logged in users while (:if auth admin:) evaluates to false.

can you post the contents of your entire local/config.php? (minus clear 
passwords, of course)
sadly my servers are running php versions 5.2.6 and 5.2.12, so I cannot verify 
if this is a 5.3 related problem. to verify or falsify that faulty crypt 
implementation in php 5.3 theory, you could use md5 or sha-1 encrypted 
passwords stored in a .htpasswd (see the Passwd section in 
http://www.pmwiki.org/wiki/Cookbook/AuthUser).

josh

-- 
ALJOSCHA SONDERHOFF
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  

GASSI-TV
Aurikelweg 22
50259 Pulheim, NRW
GERMANY

http://gassi-tv.de

On Nov/10, 2011, at 1900 , pmwiki-users-requ...@pmichaud.com wrote:

> Date: Thu, 10 Nov 2011 11:13:14 -0500
> From: "Sun, Yue" 
> To: "'pmwiki-users@pmichaud.com'" 
> Subject: [pmwiki-users] Password protection not working
> Message-ID:
>   <814d48ca046ee04dba96c426b6ceacb112bbcf6...@xcluster.vgn.cty>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi,
> 
> We have a pmwiki site (version 2.2.0) that has been up for a few years. 
> Recently we upgraded to RedHat 5 and PHP 5.3.7, after that the password 
> protection is not working any more. To help figure out the problem, I've set 
> up a new pmwiki 2.2.34, and use the simple config file with
> 
> $DefaultPasswords['edit'] = crypt('operations');
> 
> and
> 
> $EnableDiag = 1;
> 
> but still the Edit is open to everyone and never got a password prompt. When 
> I changed $DefaultPasswords['edit'] ='@lock' and the 
> password was prompted. I notice there are some discussions about the new 
> crypt() in php 5.3 and doubt if it's related to the issue I am having. Here 
> is the test pmwiki I set up 
> http://newsletter.vaughanpl.info/pmwiki/pmwiki.php. Can someone provide a 
> help? Do I have to downgrade to php 5.2?
> 
> Any comments or suggestions would be appreciated!!
> 
> Yue
> 
> 
> This e-mail, including any attachment(s), may be confidential and is intended 
> solely for the attention and information of the named addressee(s). If you 
> are not the intended recipient or have received this message in error, please 
> notify me immediately by return e-mail and permanently delete the original 
> transmission from your computer, including any attachment(s). Any 
> unauthorized distribution, disclosure or copying of this message and 
> attachment(s) by anyone other than the recipient is strictly prohibited.
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

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

[a . sonderhoff]

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,
Josh


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.
-- 
ALJOSCHA SONDERHOFF
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  

GASSI-TV
Aurikelweg 22
50259 Pulheim, NRW
GERMANY

http://gassi-tv.de

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

> Date: Sat, 5 Nov 2011 16:50:34 +0100
> From: Petko Yotov <5...@5ko.fr>
> To: pmwiki-users@pmichaud.com
> Subject: Re: [pmwiki-users] Page Variable for Original Author
> Message-ID: <20051650.34908@5ko.fr>
> Content-Type: Text/Plain;  charset="iso-8859-1"
> 
> On Saturday 05 November 2011 14:51:10 a.sonderh...@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.


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Page Variable for Original Author

[a . sonderhoff]

Is there an easy way to have something like {$LastModifiedBy} for the original 
author of a page, e. g. {$FirstModifiedBy} or something similar? I am currently 
setting up a blog system where I need the original author named automatically.

Also, I am looking for a recipe which can automatically create multiple pages 
with two clicks to set up the individual blogs. I would need to build a custom 
form to put in the required information (name of the blog, the user who runs 
the blog) and the recipe should create certain pages from templates, fill in 
the parts which need filling in (Title, description and stuff like that) and 
set the attributes (user rights) according to what I need. I looked into 
newpageboxplus (which I am using a lot) but that's only good for single pages 
and cannot modify/set group and page attributes (user rights). of course I 
could do that with a standalone php script, but that way AllRecentChanges and 
the search index won't include the new groups and pages.

thanks in advance!
-josh


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

-- 
ALJOSCHA SONDERHOFF
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  

GASSI-TV
Aurikelweg 22
50259 Pulheim, NRW
GERMANY

http://gassi-tv.de


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] mod EditForm to parse certain directives and preprend them to the content after submitting

[a . sonderhoff]

Dear Petko

thanks for pointing me to these recipes. I managed to configure EditAttributes 
with some quick and dirty javascript hacks to do the job. I noticed though, 
that there is a major bug in the recipe when handling checkboxes. it will only 
set the PTV to 1 once. if you want to set it to 0 again, it will ignore the 
unchecked checkbox leaving the PTV on a value of 0. also the recipe does not 
work with radiobuttons, select lists, etc without using a hidden helper form 
field and implementing all additional functionality with javascript hacks.

does the job more or less though.

thanks again,
josh

-- 
ALJOSCHA SONDERHOFF
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  

GASSI-TV
Aurikelweg 22
50259 Pulheim, NRW
GERMANY

http://gassi-tv.de

On Nov/02, 2011, at 1800 , pmwiki-users-requ...@pmichaud.com wrote:

> Date: Tue, 1 Nov 2011 18:04:42 +0100
> From: Petko Yotov <5...@5ko.fr>
> To: pmwiki-users@pmichaud.com
> Subject: Re: [pmwiki-users] mod EditForm to parse certain directives
>   and preprend them to the content after submitting
> Message-ID: <20011804.43089@5ko.fr>
> Content-Type: Text/Plain;  charset="windows-1252"
> 
> Hello. The EditAttributes recipe can be configured to do such additional form 
> fields, and it works even with existing pages.
> 
>  http://www.pmwiki.org/wiki/Cookbook/EditAttributes
> 
> While editing, it removes the (:title ... :), (:myPTV: ... :) and other 
> configured strings from the page text and places them in additional text 
> boxes 
> (not sure if it can do drop-down select lists). After submitting the changes, 
> it compiles the page again, with all variables at the end of the page text.
> 
> The other recipe that can edit PageTextVariables is PmForm. It can edit 
> PageTextVariables (it adds them if they are not in the page) and it can add 
> text in a page, like from a template. Standard pmwiki forms are used as edit 
> forms, so there is some configuration to do.
> 
>  http://www.pmwiki.org/wiki/Cookbook/PmForm
> 
> There is also the Fox recipe. I have never had the chance to use it or review 
> it, but it seems to do these kinds of things and more.
> 
>  http://www.pmwiki.org/wiki/Cookbook/Fox
> 
> Petko
> 
> On Tuesday 01 November 2011 12:23:41, a.sonderh...@gassi-tv.de wrote :
>> Dear PmWiki community,
>> 
>> I am looking for a way to modify the edit form (preferably by writing a new
>> Cookbook recipe) to be a little more n00b-friendly. ^_~ on gassi-tv.de we
>> are using a lot of directives (variables and page text variable
>> declarations) to control certain modules, e. g. whether the FB Like Button
>> or FB Comments show up on a site or not, where the video and poster files
>> for a certain vodcast are, title, description, keywords and stuff like
>> that.
>> 
>> that means there are quite some lines of directives on an average page,
>> which also means, that it needs certain training level to actually edit
>> the content without screwing something up by accident.
>> 
>> what I am looking to do (inspired by the EditForm Custom Fields recipe) is,
>> to have form inputs (text fields, text areas, dropdowns, etc) for all of
>> the commonly used directives without changing the way PmWiki essentially
>> works. EditForm Custom Fields for example disables the (:title ? :)
>> directive and sets a new title field. this might be the more sophisticated
>> approach, but is basically unusable for sites with a lot of already
>> existing pages.
>> 
>> so what I want to do is some regex which extracts the particular directives
>> from the content and shows them as dedicated form inputs. after submitting
>> these form input values should be prepended in form of directives to the
>> content.
>> 
>> example:
>> 
>> (:DirectiveA: VALUE:)
>> !! content
>> 
>> should show up in edit form as
>> 
>> DirectiveA: [input_field name=DirectiveA]
>> Text: [textarea name=text id=text]
>> [submit_button]
>> 
>> after submitting, "DirectiveA" and "Text" are re-merged with the directive
>> prepending the content of "Text".
>> 
>> I can think of two ways to do this:
>> 
>> 1) The Quick and Dirty JS way
>> have client-based JS run the regex and inject additional form input fields,
>> hijack the submit button and have the JS merge all before submitting into
>> the "text"-textarea. as this is nothing PmWiki specific, I already know
>> how to do this, and what the downsides are (limited processing power on
>> mobile devices, fallback compatibility with NoScript/JS-disabled browsers,
>> IE-specific workarounds).
>> 
>> 2) write a real cookbook recipe
>> that's basically what I prefer to do and need some ideas and pointing in
>> the right direction. I do know how to declare form fields in PmWiki with
>> "SDVA($InputTages['?'], array?", but I basically haven't the slightest
>> idea how the forms are processed into the file based database system after
>> submitting.
>> 
>> 
>> Thanks for any replies in advance and happy brainstorming.

[pmwiki-users] mod EditForm to parse certain directives and preprend them to the content after submitting

[a . sonderhoff]

Dear PmWiki community,

I am looking for a way to modify the edit form (preferably by writing a new 
Cookbook recipe) to be a little more n00b-friendly. ^_~
on gassi-tv.de we are using a lot of directives (variables and page text 
variable declarations) to control certain modules, e. g. whether the FB Like 
Button or FB Comments show up on a site or not, where the video and poster 
files for a certain vodcast are, title, description, keywords and stuff like 
that.

that means there are quite some lines of directives on an average page, which 
also means, that it needs certain training level to actually edit the content 
without screwing something up by accident.

what I am looking to do (inspired by the EditForm Custom Fields recipe) is, to 
have form inputs (text fields, text areas, dropdowns, etc) for all of the 
commonly used directives without changing the way PmWiki essentially works. 
EditForm Custom Fields for example disables the (:title … :) directive and sets 
a new title field. this might be the more sophisticated approach, but is 
basically unusable for sites with a lot of already existing pages.

so what I want to do is some regex which extracts the particular directives 
from the content and shows them as dedicated form inputs. after submitting 
these form input values should be prepended in form of directives to the 
content.

example: 

(:DirectiveA: VALUE:)
!! content

should show up in edit form as

DirectiveA: [input_field name=DirectiveA]
Text: [textarea name=text id=text]
[submit_button]

after submitting, "DirectiveA" and "Text" are re-merged with the directive 
prepending the content of "Text".

I can think of two ways to do this:

1) The Quick and Dirty JS way
have client-based JS run the regex and inject additional form input fields, 
hijack the submit button and have the JS merge all before submitting into the 
"text"-textarea. as this is nothing PmWiki specific, I already know how to do 
this, and what the downsides are (limited processing power on mobile devices, 
fallback compatibility with NoScript/JS-disabled browsers, IE-specific 
workarounds).

2) write a real cookbook recipe
that's basically what I prefer to do and need some ideas and pointing in the 
right direction. I do know how to declare form fields in PmWiki with 
"SDVA($InputTages['…'], array…", but I basically haven't the slightest idea how 
the forms are processed into the file based database system after submitting.


Thanks for any replies in advance and happy brainstorming.
—Josh

-- 
ALJOSCHA SONDERHOFF
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  

GASSI-TV
Aurikelweg 22
50259 Pulheim, NRW
GERMANY

http://gassi-tv.de


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Looking for articles/reviews about PmWiki

[a . sonderhoff]

>> I see many webdesigners using wordpress as a basis for their work
> ...
>> Maybe PmWiki, if it would have been visually
>> more attractive at first sight, could have suit their need too.
> 
> Maybe. But those people are curiuos and educated so I think they know what 
> they're doing.
> 
> They may also be just young and/or not part of the wiki culture: 
> collaboration, evolving articles, blank text area, a wiki markup as an 
> additional layer of punctuation, fist add a link then click on it to create a 
> page etc...

Dear PmWiki developer community,

I studied media design and I am currently employed as a creative director in a 
small advertising agency. Obviously I am the brand manager of GASSI TV® as 
well. As such I would like to comment on PmWiki and maybe even give some 
inspiration. I am also aware, that some of the stuff I am going to write is not 
really in line with Pm's original philosophy on PmWiki.

I have been using PmWiki quite a lot for small business websites and as of this 
year even for a professional more complex, content centered site. I started 
playing around with PmWiki in 2003 or 2004 when I was looking for an 
alternative to Mediawiki, which would not run on my shared webhosting account. 
I found PmWiki and was both intrigued and disappointed. The simplicity meant it 
would run on the shared webhosting account. But the lack of an mysql db was 
somewhat of an administration and file rights nightmare (for backup on a shared 
webhosting account without ssh login). So basically I used for several years as 
a Wiki for small collaboration communities.

In 2006 I had to design a website as a college project in Webdesign class. Not 
wanting to put much effort in setting up a complex cms, I realized the heavily 
design centered site (mootools animations, large pictures, multiple templates 
etc.) within a short time with PmWiki. In fact my initial technical 
presentation on PmWiki made another project group of media designers to go with 
PmWiki as well. That's when I realized, that PmWiki is much more than a Wiki. 
It's in fact a simple cms framework which is easy to extend and where you can 
design the backend to the needs of your clients.

It's a great wiki (I currently use it for two private collaboration projects), 
but it's only one of the few available cms which offer maximum flexibility with 
minimum configuration and setup time (another being pixie). For us designers 
PmWiki is nearly invisible, because the pmwiki.org site looks visually outdated 
and the content centers around the wiki functionality. Just have look on the 
Pixie or Wordpress sites. They are much more visually appealing.

These lines are just my two cents. But just think about this: When GASSI TV® 
was relaunched this year, we were planning to use Drupal as the new CMS. But 
when I played around with PmWiki, it soon became clear, that I could actually 
realize the same functionality and design faster with PmWiki. If I didn't play 
around with PmWiki for a long time and figured out, that it can be easily 
configured as a cms, I would never even have considered using it. From a brand 
management point of view, the brand name PmWiki is not really a benefit, as it 
reduces the cms to a wiki. The visual appearance of both site and brand are 
plainly speaking not adding to the brand value at all. It's a great product, 
but it ships in an unappealing packaging.

Take care, Josh

-- 
ALJOSCHA SONDERHOFF
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  

GASSI-TV
Aurikelweg 22
50259 Pulheim, NRW
GERMANY

http://gassi-tv.de

On Oct/02, 2011, at 1900 , pmwiki-users-requ...@pmichaud.com wrote:

> Date: Sun, 2 Oct 2011 14:28:46 +0200
> From: Petko Yotov <5...@5ko.fr>
> To: pmwiki-users@pmichaud.com
> Subject: Re: [pmwiki-users] Looking for articles/reviews about PmWiki
> Message-ID: <201110021428.46790@5ko.fr>
> Content-Type: Text/Plain;  charset="iso-8859-1"
> 
> On Sunday 02 October 2011 10:26:12, Eric Forgeot wrote :
>>> PmWiki was very popular in the past because it was one of the first
>>> wikis/CMSs written in PHP at a moment when cheaper hosting providers
>>> started providing PHP in addition to static HTML,
>> 
>> I didn't know PmWiki was that old. It would worth mentionning it on the
>> wiki (date of creation or first release)
> 
> The very first version 0.1 was released January 8, 2002, that is almost 10 
> years ago. We should think about the birthday party, and what we should have 
> done before that date: improving the homepage and the documentation, updating 
> the translations...?
> 
>> About the {{notability}} and {{primary sources}} tags added on the
>> PmWiki page on WP, I see they were added by an unregistered user from
>> Poland. Don't you think it could be a kind of vandalism? Wouldn't it be
>> possible to revert this random and non justified action?
> 
> It is not vandalism. BTW, on Wikipedia like on all open wikis, it is 
> recommended to assume good

Re: [pmwiki-users] pagelist / searchresults with weighted search

[a . sonderhoff]

Thanks for the suggestion, but I am more of a designer and less of a real 
developer. I tend to get lost in complex existing code like the PmWiki internal 
functions. I managed to fork Gilles' suggested cookbook recipe (SortByScore) 
and change it to suit my purpose for now. It's still some kind of a quick and 
dirty solution as SortByScore uses fmt=score with a fixed SDV instead of 
order=score with the option to use your own fmt templates from 
Site/LocalTemplates.

SortByScore Pros:
• does the job somehow
• configureable weight multiplier for title
• leightweight cookbook recipe solution
• extends already existing (:pagelist:) functionality

SortByScore Cons:
• lacking visual customization (uses fixed fmt=score instead of order=score)
• no normalization of score (for consistent gui visualization of search result 
quality, e. g. always 5 stars for top result/s)

-Josh

On Jul/29, 2011, at 1312 , V.Krishn wrote:

> On Friday 29 Jul 2011 5:48:44 am a.sonderh...@gassi-tv.de wrote:
>> With several PmWiki powered pages I am experiencing limitations in the
>> Search functionality to a point where searching is nearly useless. This
>> happens when there are a lot of pages (100+) with a large amount of content
>> (50+ words). What happens is, that when using certain search terms, the
>> page which is most relevant is nearly never listed as the first hit. This
>> is because the search results can only be ordered by ctime, title, group
>> etc., but not relevance/search quality.
>> 
>> I was looking into writing a cookbook recipe myself to implement a simple
>> weighted search (e. g. Title 0-20 pts, Description 0-10 pts, other content
>> 0-5 pts) which the results can be sorted by (I used to do weighted searches
>> a lot with mysql). But that would have meant to write an indexing routine
>> of sorts. Of course PmWiki already comes with a simple search index, which
>> basically lists keywords for the pages in the wiki. But the .pageindex
>> seems to have no information about the quantity of these keywords within a
>> specific page.
> 
> Have a look at some of search engines here:
> http://www.pmwiki.org/wiki/PITS/00333
> 
> From a brief look at php impementation of Lucene in Zend framework I guess 
> that would be an easy approach.
> 
>> 
>> Any ideas how to implement a weighted search without having to do that from
>> scratch, e. g. adding this to the pagelist? I have to admit, that my
>> understanding of PmWiki's internal functions and programming style is
>> rather limited at this point. I am not so much a developer, more of a
>> designer actually.
>> 
>> Thanks for any input. I think weighted search is the only major feature
>> PmWiki is missing to be a fully grown up wiki/cms.
>> 
>> —Josh
> 
> -- 
> Regards.
> V.Krishn


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] pagelist / searchresults with weighted search

[a . sonderhoff]

With several PmWiki powered pages I am experiencing limitations in the Search 
functionality to a point where searching is nearly useless. This happens when 
there are a lot of pages (100+) with a large amount of content (50+ words). 
What happens is, that when using certain search terms, the page which is most 
relevant is nearly never listed as the first hit. This is because the search 
results can only be ordered by ctime, title, group etc., but not 
relevance/search quality.

I was looking into writing a cookbook recipe myself to implement a simple 
weighted search (e. g. Title 0-20 pts, Description 0-10 pts, other content 0-5 
pts) which the results can be sorted by (I used to do weighted searches a lot 
with mysql). But that would have meant to write an indexing routine of sorts. 
Of course PmWiki already comes with a simple search index, which basically 
lists keywords for the pages in the wiki. But the .pageindex seems to have no 
information about the quantity of these keywords within a specific page.

Any ideas how to implement a weighted search without having to do that from 
scratch, e. g. adding this to the pagelist? I have to admit, that my 
understanding of PmWiki's internal functions and programming style is rather 
limited at this point. I am not so much a developer, more of a designer 
actually.

Thanks for any input. I think weighted search is the only major feature PmWiki 
is missing to be a fully grown up wiki/cms.

—Josh

-- 
ALJOSCHA SONDERHOFF
brand & marketing

office +49 2238 4629519
mobile +49 1511 5794189
fax+49 2238 963023
email  

GASSI-TV
Aurikelweg 22
50259 Pulheim, NRW
GERMANY

http://gassi-tv.de


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users