Item5019: if you get a lease conflict when using EditTablePlugin, the oops conflict output link is unusable

When you edit a table with EditTablePlugin and get a lease conflict with someone the edit again and break anyway buttons send you to normal view mode.

-- TWiki:Main/KennethLavrsen - 23 Nov 2007



<verbatim><form action="/cgi-bin/TWikiRelease04x02/bin/view/Sandbox/EditTablePlugin" method="post">
To edit the topic anyway, click </verbatim>

EditTablePlugin is using the view script, because editing / adding a row is a view operation, but because the plugin is written to use #edittable1 it breaks the oopsconflict message - losing the =#edittable1=

-- SvenDowideit - 24 Nov 2007

It would need to pass aditional parameters:

• viewauth instead of view
• ettablenr=1 (or any other table number)
• etedit=on

-- TWiki:Main.ArthurClemens - 02 Dec 2007

other options:

• EditTablePlugin could have its own oops tmpl or message
• EditTablePlugin could could use a more 'standard' trigger, using urlparams that are not lost

but i guess these are fo the future?

-- TWiki:Main.SvenDowideit - 09 Dec 2007

As Sven mentioned on IRC, the plugin throws the oops error itself. Instead of redirecting to the default oops page, it can redirect to a special edittableplugin oops, passing the url parameters.

-- TWiki:Main.ArthurClemens - 09 Dec 2007

I think that an easy work around is to change to a normal oops that warns that the topic is being edited by someone else and that you can edit and save the topic in a normal edit mode to break the lock.

Not elegant but would be an OK work around for 4.2

-- TWiki:Main.KennethLavrsen - 10 Dec 2007

The simple solution was to pass the edit table parameters to the oops url. The rest is TWikiMagic.

-- TWiki:Main.ArthurClemens - 12 Dec 2007