Your assumption is correct. The idea was to avoid people from saving a page if the plugin parameters are not correct. I think I have to change the plugins in a way that they can work not assuming that the all the saved pages are correctly configured.
Thanks for the help! On Wed, Jan 7, 2009 at 6:39 PM, Foster Schucker <[email protected]> wrote: > I'm assuming you are editing a page and enter something like: > > [{myplugin parm='data that will cause it to fail' }] > > and then you save it. When the page is rendered the PluginException is > caught. Correct? > > Since the edit process has no real understanding of the rendering process > there isn't a simple way to stop it. > > A workaround may be to do a preview first to make sure the page renders the > way you want before saving it. > > Or move the save button to the preview page to force the user to do a > preview first. That won't stop them from doing the preview, not looking at > the page and then hitting save anyway. > > Foster > > > Osvaldo Pina wrote: > > Hi, >> >> >> I'm developing a plugin and even when the plugin launched >> PluginException the page is saved. Can I change this behavior? >> >> >> Tanks, >> Osvaldo Pina. >> >> >> > >
