re-worded from Kenneth's report in Item5014
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.
- 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
it breaks the oopsconflict message - losing the =#edittable1=
- 24 Nov 2007
It would need to pass aditional parameters:
viewauth instead of
ettablenr=1 (or any other table number)
Somehow these would need to get passed to
- 02 Dec 2007
but i guess these are fo the future?
- 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.
- 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
- 10 Dec 2007
The simple solution was to pass the edit table parameters to the oops url. The rest is TWikiMagic.
- 12 Dec 2007