Item2241: Edit Table should interpret sections when including table from another topic

(reproduced at foswiki.org)

If Multiple Editable tables are included from a page with named SECTIONs, the tables all assume #edittable1 which is incorrect.

Assume two pages:

SourcePage

%STARTSECTION{name="A"}%

%EDITTABLE{}%
| *Animal* | *Size* |
| Bear | Large |
| Elephant | Huge |

%ENDSECTION{name="A"}%

%STARTSECTION{name="B"}%

%EDITTABLE{}%
| *Fruit* | *Color* |
| Banana | Yellow |
| Eggplant | Purple |

%ENDSECTION{name="B"}%

%STARTSECTION{name="C"}%

%EDITTABLE{}%
| *Make* | *Model* |
| Toyota | Camry |
| Honda | Civic |

%ENDSECTION{name="C"}%

DestinationPage

%INCLUDE{"SourcePage" section="C"}%

%INCLUDE{"SourcePage" section="B"}%

%INCLUDE{"SourcePage" section="A"}%

Result

Although the tables will be presented in proper order on DestinationPage, any button that is clicked will open the first table ("Animals") for editing.

-- VickiBrown - 12 Oct 2009

Edit table reads the text of included topic and finds the first table. No parsing is involved, so sections are not interpreted. This is documented: "The first in the topic is used." So only to a certain degree it does not work as expected.

Changed to enhancement and changed the summary from "Included Editable Tables do not work as expected if Sections are used" to "Edit Table should interpret sections when including table from another topic".

-- ArthurClemens - 12 Oct 2009

Arthur - That's close enough for me.

One thing I'd love to see is a better way to reference tables. The problem, as I see it, is that ET calculates #edittable1 without any thought. If the user could override that, say with named tables?...

-- VickiBrown - 12 Oct 2009