Re: [pmwiki-users] Strip markup to generate plain text
Jan Erik Moström wrote: Eemeli Aro [EMAIL PROTECTED] 08-02-14 18.45 I suggest you take a look at www.pmwiki.org/wiki/Cookbook/MarkdownOutput. That looks pretty good. Looking at the sample output, I notice that its output character format is UTF-8. Is this hard-coded, or does it depend on the format of the source wiki text? ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] markup question
noskule wrote: hi list could someone please take a look at this markup. I cant get it to work. It should rpoduce a fieldset: If what you want is markup for fieldset and legend, it already exists: http://www.pmwiki.org/wiki/Cookbook/FormExtensions ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] MySQL and Notify?
Thursday, February 14, 2008, 7:43:04 AM, Stirling Westrup wrote: Use a database recipe and some variation of Notify perhaps? Will they even play nice together? DataQuery looks interesting. The documentation says that you do not need ZAP for it, you could use another form processing system. If I understand it correctly, it should work quite transparent. You just designate a wiki group as a query in the configuration, and actions on pages in it are done on database records. The database acts as a wiki page store. Notify should work, if you set the mail receiver to get notification for a page change in your data page, and set squelch=0 for this. ~Hans ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] MySQL and Notify?
In article [EMAIL PROTECTED], [EMAIL PROTECTED] says... I've been asked to put up a simple volunteering form on a PmWiki website. They would like the results from the form to be stored in a MySQL database, and a copy of the data emailed to the person in charge of volunteers. I know of recipes to store form data in a database, and ones to mail results to someone, but what's the best way to do both? Use a database recipe and some variation of Notify perhaps? Will they even play nice together? Any suggestions would be helpful, although I should mention that I'm not interested in using Zap. The learning curve for getting MySQL working is already steep enough (I've never used it before), so I don't want to add to the difficulty. I found the easiest way to do this was to write my own recipe. I kept it simple by using AdoDB and its active record feature - thus each table is an object. If you are not doing anything fancy with your tables, then building a recipe to simply do CRUD is not at all onerous. (I would have developed this into a general recipe, but the sentiment when I was building it was not to use objects with db access. The design hinges on creating a db object on connection.) It might be fun to create a PmWiki on Rails example of how to do this for a couple of tables. I used phpmailer for email, although you could use notify for this, or wrap phpmailer in a recipe. -- Cheers Marc ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] Content/Music - preprocessor step
I'm trying to extend the (:abcm:) to use a preprcessorstep - abcpp
I looked at the script and I found a place where the scripts are assigned.
ContentRegFSConverter(abcm, midi, 'abc2midi ${i} -o ${o}');
Does it make sense to pipe,
Soemting like here
ContentRegFSConverter(ppm, gif, 'pnmcrop ${i} | ppmtogif ${o}');
But it seems to be better to me to have a separate step.
Actually I don't understand how the processing sequenz is controlled
regards
Patrick
P.S.
For postprocessing (mp3 generation) I wrote a script. And I do manually
at the moment.
The contentstructure is clear, so the midi can be found below the
directoryname, which is the same name like the pmwiki page.
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Re: [pmwiki-users] Strip markup to generate plain text
On Fri, Feb 15, 2008 at 11:11 AM, [EMAIL PROTECTED] wrote: Eemeli Aro [EMAIL PROTECTED] 08-02-14 18.45 I suggest you take a look at www.pmwiki.org/wiki/Cookbook/MarkdownOutput. That looks pretty good. Looking at the sample output, I notice that its output character format is UTF-8. Is this hard-coded, or does it depend on the format of the source wiki text? I'm pretty sure that the charset depends on the source text; the output I get from my own sites is in ISO-8859-1. The sample just happens to be in UTF-8. I modified the code a bit today, and the latest version of MarkdownOutput now also converts tables, definition lists and some other markups that aren't a part of the default Markdown syntax. eemeli ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
[pmwiki-users] Security Update for Fox recipe
Since the last major upgrade 2008-01-09 Fox was by default open to receive input not just from form controls but also via url parameter input. I now changed this default, so Fox is by default only accepting input from form submissions (via PHP $_POST). Input from url parameters (via PHP $_GET) can be achieved by setting a new config variable $EnableFoxUrlInput = true; This security measure is in additional to having to set explicitly page posting permissions and authorisation level for page access. Please consider upgrading, any feedback and suggestions are very welcome! ~Hans ___ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users
