[pmwiki-users] MySQL and Notify?

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 t

Re: [pmwiki-users] Duplicate email notification

Much easier! Thank you. I tested it in on a couple of different forms and it seems to work. Randy On Feb 13, 2008, at 1:21 PM, Hans wrote: > >> In the current case: there is yet no need to change notify.php. You >> can >> instead have in config.php: > >> if($action!='foxpost' >> && $action!='

Re: [pmwiki-users] Duplicate email notification

Wednesday, February 13, 2008, 6:07:48 PM, Patrick R. Michaud wrote: > Thus, fixing notify.php so that NotifyUpdate is only invoked once, > and using an array of updated pages (instead of assuming that $pagename > is the page being updated) should go a long way to resolve this > particular problem.

Re: [pmwiki-users] Duplicate email notification

Wednesday, February 13, 2008, 5:58:51 PM, Petko Yotov wrote: > Hey wait a minute!! Don't search what changes in PmWiki core would serve your > recipes, try to adapt your code instead. PmWiki has countless possibilities > to do this. Sure. I only tried to find a solution to someone's particular pr

Re: [pmwiki-users] java pop-up for duplicate upload name

david roundell said... > > i would like to have a script to warn our users that the filename they > intend to use on an upload is already in use. ideally the pop-up > should state are you sure you wish to overwrite the file yes/no? > whether this should be in java or html is not essential. Well,

Re: [pmwiki-users] Content/Music - extremly long access-path via URL

--- Patrick Ogay <[EMAIL PROTECTED]> wrote: > But "Exsultate justi" definitely made problems (in > Moz) and I changed it to (:music:) again. > http://www.wprj.net/chor/index.php/Tunes/ViadanaExsultateJusti I looked at your page above. I pasted the abcm into my test wiki here: http://www.thefick

Re: [pmwiki-users] Duplicate email notification

On Wed, Feb 13, 2008 at 05:45:10PM +, Hans wrote: > Wednesday, February 13, 2008, 5:30:21 PM, Patrick R. Michaud wrote: > > This is probably the source of the difficulty -- NotifyUpdate > > really doesn't expect to be called more than once in a given > > session. But if multiple pages are bein

Re: [pmwiki-users] Duplicate email notification

On Wednesday 13 February 2008, Hans wrote: > > Randy's problem was that he got duplicates of the same notification. > After a lengthy investigation we found that a change in notify.php > would stop that behaviour: > > changing this in notify.php: > > ## check if we need to do notifications > if (

Re: [pmwiki-users] Duplicate email notification

Wednesday, February 13, 2008, 5:30:21 PM, Patrick R. Michaud wrote: > This is probably the source of the difficulty -- NotifyUpdate > really doesn't expect to be called more than once in a given > session. But if multiple pages are being updated via UpdatePage(), > then it would get reigstered mu

Re: [pmwiki-users] Cookbook path

On Sun, Feb 10, 2008 at 05:52:30PM -0500, DaveG wrote: > I'm writing a Cookbook (or Recipe, I never know which is which), and I > need to get the URL of the location that the script is executing from -- > basically the cookbook directory. This way gets me the script *path* > (not the URL), which

Re: [pmwiki-users] FW: UpdatePage() vs save from ?action=edit

On Fri, Feb 08, 2008 at 09:52:04PM +0100, Peter & Melodye Bowers wrote: >Did anybody have any thoughts on this? I'm guessing it has something to >do with what functions are registered in EditFunctions before calling >UpdatePage()? > > > >To rephrase my question below, I am c

Re: [pmwiki-users] Duplicate email notification

On Fri, Feb 08, 2008 at 10:03:06AM +, Hans wrote: > I suspect something goes wrong there for you, and NotifyUpdate is > twice registered, and twice executed, resulting in double emails. > Why I do not know. But notify.php has no mechanism to prevent the > NotifyUpdate function from being twice

Re: [pmwiki-users] Pre-fill author required field with login name on a one-password-for-all wiki?

Dear Patrick, I am using pmwiki-2.2.0-beta63. Please find below a copy of what could be relevant parts of my config.php $DefaultPasswords['admin'] = crypt('something'); $DefaultPasswords['read'] = crypt('something'); $DefaultPasswords['edit'] = crypt('something'); $DefaultPasswords['rss'] = crypt

Re: [pmwiki-users] Bugs in TextSection and MakePageName

On Wed, Feb 13, 2008 at 02:37:35PM +, Hans wrote: > Wednesday, February 13, 2008, 2:22:42 PM, Petko Yotov wrote: > > > Anyhow, I hope that you will be able to change Fox to use "##section" > > instead > > of "..#section" for it to work without your users required to modify core > > scripts. :

Re: [pmwiki-users] 2.2.0-beta65 and InitialPasswords

On Wed, Feb 13, 2008 at 12:50:33AM -0500, Aaron wrote: >I recently installed 2.2.0-beta65 and have been having great luck with >it. However, I uncovered some funniness tonight with regards to the >information in the InitialPasswords page >(http://www.pmwiki.org/wiki/PmWiki/InitialP

Re: [pmwiki-users] Strip markup to generate plain text

> Sorry for being so unclear. Markdown in this case is text > formatting system that is quite popular > . > > But what I'm looking for is something that will allow me to > strip PmWiki syntax from the stuff I've written and generate > plain text.

Re: [pmwiki-users] Strip markup to generate plain text

On Wednesday 13 February 2008, Hans wrote: > Wednesday, February 13, 2008, 9:43:24 AM, Peter & Melodye Bowers wrote: > > [Hans, might a SnipMarkup() function with a > > corresponding {(SnipMarkup ...)} MX be a good function to have available > > in PowerTools? Just a tho't... I know I could make

Re: [pmwiki-users] Bugs in TextSection and MakePageName

Wednesday, February 13, 2008, 2:22:42 PM, Petko Yotov wrote: > Anyhow, I hope that you will be able to change Fox to use "##section" instead > of "..#section" for it to work without your users required to modify core > scripts. :-) Oh I think Fox does already. I just wanted it to be fully able to

Re: [pmwiki-users] Bugs in TextSection and MakePageName

On Wednesday 13 February 2008, Hans wrote: > Wednesday, February 13, 2008, 1:12:49 PM, Petko Yotov wrote: > > You need to use: > > Page##section > > > > or: > > Page#..#section > Then the documentation is wrong (the commenting of the function in > pmwiki.php): > ####abc, ..#abc - beginni

Re: [pmwiki-users] Strip markup to generate plain text

Wednesday, February 13, 2008, 9:43:24 AM, Peter & Melodye Bowers wrote: > [Hans, might a SnipMarkup() function with a > corresponding {(SnipMarkup ...)} MX be a good function to have available in > PowerTools? Just a tho't... I know I could make use of it with WikiSh.] If the aim is to strip ou

Re: [pmwiki-users] Bugs in TextSection and MakePageName

Wednesday, February 13, 2008, 1:12:49 PM, Petko Yotov wrote: > No, this is not a bug, you are using it incorrectly. > You need to use: > Page##section > or: > Page#..#section > and not > Page..#section Thanks, I am happy to be corrected! Then the documentation is wrong (the commenting

Re: [pmwiki-users] Bugs in TextSection and MakePageName

On Wednesday 13 February 2008, Hans wrote: > I think I found a bug in function TextSection (pmwiki.php): > > The function did not return the correct text when using the suffix > ..#section to a pagename, which should return all text up to anchor > [[#section]]. [...] > > I need that for placing a

[pmwiki-users] Bugs in TextSection and MakePageName

I think I found a bug in function TextSection (pmwiki.php): The function did not return the correct text when using the suffix ..#section to a pagename, which should return all text up to anchor [[#section]]. The preg-match pattern does not match this input. Changing this if (!preg_match("/#

Re: [pmwiki-users] Strip markup to generate plain text

Wednesday, February 13, 2008, 9:43:24 AM, Peter & Melodye Bowers wrote: > If you are looking for plain text with markup stripped out then you may want > to look into Hans's ExtractText with the markup=snip option. You could > "search" for "." (i.e., return every line) and specify markup=snip so t

Re: [pmwiki-users] Strip markup to generate plain text

Peter & Melodye Bowers <[EMAIL PROTECTED]> 08-02-13 10.43 >>Perhaps a stupid question but is there some way to generate >>plain text from pmwiki content source? > >I wasn't sure what you meant by "markdown" -- do you mean "plain text" >*after* markup has been applied? Or are you looking for the s

Re: [pmwiki-users] Strip markup to generate plain text

> Perhaps a stupid question but is there some way to generate > plain text from pmwiki content source? I wasn't sure what you meant by "markdown" -- do you mean "plain text" *after* markup has been applied? Or are you looking for the source text with the markup still visible? Or (as your subject

Re: [pmwiki-users] Content/Music - extremly long access-path via URL

thank you very much. >If you have converters for this it should be easy to >make work. I have some ideas for the future for our chorus singers: - for example, to let the user select a voice (let's say bass) and the instruments. I think I like one "major/static midi", and indivduell temporary