All right. I'll look into this. I suppose we could pass an array back from the custom function--one with content and two with a flag to return or continue processing. This would allow you to either return immediately, or continue on through the rest of the function. Or perhaps we could have an array of functions called in some order, by default including the core page save routine, but not necessarily. This could really open things up--which I like! Can you remember how PmWiki did this? I never got to that point in understanding its inner workings. No promises though. I suspect this could introduce problems if not done carefully.
Cheers, Dan On Mon, Oct 5, 2009 at 10:06 AM, blues <[email protected]> wrote: > > On Oct 5, 4:48 pm, The Editor <[email protected]> wrote: >> Well the idea is to copy the entire BOLTsavepage to your new >> myBOLTsavepage function and then just tweak what you want. That way >> you can change just part or all of the function as needed. > > i also thought of that, but it would become unbearable to update it > (or at least double-check it) every time boltwire gets updated. > not nice for a plugin. > > >> Other than >> the replace table, there's no real way to edit the content. > > do you remember the PmWiki times? there was an array $EditFunctions > which was the pipe through which the page goes when saving. i thought > maybe there is something like that here. > well, a full pipe is not needed but maybe is it possible to implement > a way to fall back to the default BOLTsavepage after the custom code > is performed? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
