[pmwiki-users] ZAPmarkups

Hans design5 at softflow.co.uk
Mon Apr 2 13:04:27 CDT 2007


Hi Dan, I got some questions and comments about zapmarkups.php

* If zapmarkups.php is installed without zap.php I get a Fatal Error:
Call to undefined function ZAPpageshortcuts. It would be nice if this
recipe can run without ZAP installed.

* The count markup gives different results than Pm's pagelist
fmt=count (PagelistCount). It may be because ZAPmarkups uses a
hardcoded exclusion list, and so will not reflect custom exclusion
lists as PmWiki allows. In any case Pagelistcount is more flexible and
more accurate, so i am not sure why {(count)} is needed.

* I am not sure what "Thread" means. A ZAP term? Last page in a ZAP
group of data pages with numeric page names?

* {(pagelist group=Group)} does not work. And why is this markup
needed, if all it does is to translate the normal syntax?

* I am not clear how the time markup should work: I tried
{(time +|+0s|%d.%m.%Y - %H:%i)} for current time formatted
according to strftime syntax, and also {(time +|+0s|d.m.Y - H:i)}
with no result. Some examples would help. The latter syntax
(d.m.Y)(without the %) is used in Fox's {date: } var and seems a good
shortcut within dedicated time markup.

* Are the   strings necessary? They feel awkward to use.

* For some of these markups I wonder why the normal pmwiki
pagevariable syntax {$VarName} is not used, as they are providing page
variables. Like

$FmtPV['$IP'] = '$_SERVER[REMOTE_ADDR]';
$FmtPV['$Host'] = '$_SERVER[REMOTE_HOST]';
$FmtPV['$HTTPS'] = '$_SERVER[HTTPS]';
$FmtPV['$Browser'] = '$_SERVER[HTTP_USER_AGENT]';

The last one is actually not that useful as it returns the whole agent
string. Normally something shorter is filtered out to give just a
browser name and perhaps version number.


  ~Hans   




More information about the pmwiki-users mailing list