Typically, the functions of pmwiki.php should ''not be called directly'' in a cookbook recipe which is executed as include file in config.php.

While this is true for UpdatePage() I'm not convinced it is a general rule...
This general rule was my initial question to this mailing list. As long as one cannot be sure about the appropriate context, using handlers are the safe way, aren't they? I, for instance, would have destroyed all my page histories otherwise ...


BTW I documented the custom action business on a different page at http://www.pmwiki.org/wiki/PmWiki/CustomMarkupAlt#customaction after Hans wrote and before you posted here.  I suppose having it in 2 places is better than none...
Is it possible to move http://www.pmwiki.org/wiki/PmWiki/CustomMarkupAlt#customaction to
http://www.pmwiki.org/wiki/PmWiki/CustomActions ? (by leaving a link, of course)
Because I was looking into actions when I felt that Markup was just NOT what I wanted.

I suggest promoting Custom Markup and Custom Actions as the two main customization features for add-on scripts. My own earlier naive approach of scripting effectively during execution config.php (albeit in cookbook includes) is not the way that "layman" add-on authors should be guided too.

Frank

-- 
_______________________________________________________________________
Dr. Frank F. Schweickert
AMSTEL Institute, Faculty of Science, University of Amsterdam
Kruislaan 404, Amsterdam, 1098 SM, Netherlands
Room 1.09
Phone: +31 20 525-5969, Fax: +31 20 525-5866
http://www.science.uva.nl/amstel
http://www.natsim.net



_______________________________________________
pmwiki-devel mailing list
pmwiki-devel@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-devel

Reply via email to