Patrick R. Michaud said... > > [EMAIL PROTECTED] wrote: > > > Would it make sense to let the PmWiki distribution contain a "backup" > > > list of the recipe versions? Then when you update PmWiki, you can also > > > check to see if there are any recipes that you might want to update. > > Interesting idea... but I think it could lead to confusion. > And it really improves things only for admins that cannot > use RecipeCheck or SiteAnalyzer to check their recipes using > the pmwiki.org copy of recipelist. (Admins that can access > the pmwiki.org-based checks can do a check immediately following > an PmWiki update without any extra work.)
<snip> > Perhaps we should put a note about doing recipe checks into > the PmWiki.Upgrades page? In the spirit of having the data stored locally, have you considered storing the recipelist locally? So, say, displaying an appropriate page would automatically update from pmwiki.org, or if this fails (fopen() and curl), it falls back to allowing the admin to c&p the data from a displayed page into, say, Site.RecipeList. In this way, at least the recipe version check will only require one version, rather than RecipeCheck or SiteAnalyzer, and you'll know that the process will always work (providing the recipelist page has been populated at least once). -- Cheers, Marc _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
