Blarg. Likely a problem that would have to be fixed with http://plugins.jquery.com/project/issues/treeTable

Files: 
CommentFileSizeAuthor
#8 1062492-treetable-keep-events-in-same-table.patch670 bytesDave Reid
PASSED: [[SimpleTest]]: [MySQL] 245 pass(es).
[ View ]
#7 1062492-treetable-keep-events-in-same-table.patch730 bytesDave Reid
PASSED: [[SimpleTest]]: [MySQL] 245 pass(es).
[ View ]
#6 1062492-treetable-keep-events-in-same-table.patch705 bytesDave Reid
PASSED: [[SimpleTest]]: [MySQL] 245 pass(es).
[ View ]
#1 allow_multiple_tables.patch2.3 KBBerdir
PASSED: [[SimpleTest]]: [MySQL] 186 pass(es).
[ View ]

Comments

Status:Active» Needs review
StatusFileSize
new2.3 KB
PASSED: [[SimpleTest]]: [MySQL] 186 pass(es).
[ View ]

Here is a patch that fixes it in token.module by adding a prefix to the used id's.

The prefix is only added if there is more than a single table, this could easily be changed add one by default.

Patch is quite simple I think :)

hm, why not use classes instead of ids if its not unique? Or, drupal_html_id() ?

Could also use drupal_html_id(), the problem is that it is a mix of an id and classes. First, we add an id, which needs to be unique and then we have a number of classes (all rows that have the previous with the id as the parent) which need to reference to that id.

But yeah, it might be possible to use drupal_html_id() once then then re-used what has been returned.

Subscribe.

StatusFileSize
new705 bytes
PASSED: [[SimpleTest]]: [MySQL] 245 pass(es).
[ View ]

Using drupal_html_id will not allow us to cache the token tree's output. And modifying the library to use classes rather than IDs is a bigger step then it looks. Please try the following patch which changes the behavior of the childrenOf and parentOf functions to search only the 'current' treeTable.

StatusFileSize
new730 bytes
PASSED: [[SimpleTest]]: [MySQL] 245 pass(es).
[ View ]

StatusFileSize
new670 bytes
PASSED: [[SimpleTest]]: [MySQL] 245 pass(es).
[ View ]

Even better which uses .siblings().

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.