Hello,
I'm trying to create a site-wide (placed in the root category) table
subelement, which has roughly the following structure:
- Element Type : table Min. 0 Max. 0
Field (select): table_style Min. 1 Max. 1 (I'm using Bricolage 1.11.2)
Subelement: table_row Min. 1 Max. 0
Field (checkbox): is_header Min. 1 Max. 1
Subelement: table_cell Min. 1 Max. 0
Field (WYSIWYG): contents Min. 1 Max. 1
That is, by default my table has 1 row and 1 cell which you have to fill
out with contents.
When I try to use this element "table" in my new stories, after adding
the table_row, I get the default table_cell, but not the default
contents field. If I add another "table_cell" subelement to the same
row, a second correctly shown "table-cell"-subelement along its
corresponding contents"-field appears. I have then to delete the
"faulty" first "table_cell" subelement.
I can provide screenshots for this.
Do you suspect what I'm doing wrong here?
Thanks for your help.
Best,
Michael
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I'm getting back to this issue, because after trying different scenarios it still doesn't work for me under Bricolage 1.11.2, and I don't know whether I should post a bug.
My first assumption was that this is an IU related issue, because after inserting the element instance in the story I can still see the correct structure through the bulk edit. Besides this, I've seen noticed some JS errors fired up by Xinha (something about a parent node without an existing id). So I've recreated my table element with a row subelement consisting of plain text fields instead of WYSIWYG-fields for the cells. The problem is still there when inserting the table element in my story. Then I've recreated the table element for a fixed number of columns (in my case: 3), in order to avoid adding code to correct input errors like column number inconsistencies among rows. Now I have a table element with a row subelement consisting of 3 plain text fields. If I make the row subelement "required", then the UI is unable to insert the element instance showing the row with the three cells, whereas if I define it as not required, I simple add the first row and the subsequent rows manually in my story and everything is
fine...
Best,
Michael
I'm trying to create a site-wide (placed in the root category) table
subelement, which has roughly the following structure:
- Element Type : table Min. 0 Max. 0
Field (select): table_style Min. 1 Max. 1 (I'm using Bricolage 1.11.2)
Subelement: table_row Min. 1 Max. 0
Field (checkbox): is_header Min. 1 Max. 1
Subelement: table_cell Min. 1 Max. 0
Field (WYSIWYG): contents Min. 1 Max. 1
That is, by default my table has 1 row and 1 cell which you have to fill
out with contents.
When I try to use this element "table" in my new stories, after adding
the table_row, I get the default table_cell, but not the default
contents field. If I add another "table_cell" subelement to the same
row, a second correctly shown "table-cell"-subelement along its
corresponding contents"-field appears. I have then to delete the
"faulty" first "table_cell" subelement.
I can provide screenshots for this.
Do you suspect what I'm doing wrong here?
Thanks for your help.
Best,
Michael
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I'm getting back to this issue, because after trying different scenarios it still doesn't work for me under Bricolage 1.11.2, and I don't know whether I should post a bug.
My first assumption was that this is an IU related issue, because after inserting the element instance in the story I can still see the correct structure through the bulk edit. Besides this, I've seen noticed some JS errors fired up by Xinha (something about a parent node without an existing id). So I've recreated my table element with a row subelement consisting of plain text fields instead of WYSIWYG-fields for the cells. The problem is still there when inserting the table element in my story. Then I've recreated the table element for a fixed number of columns (in my case: 3), in order to avoid adding code to correct input errors like column number inconsistencies among rows. Now I have a table element with a row subelement consisting of 3 plain text fields. If I make the row subelement "required", then the UI is unable to insert the element instance showing the row with the three cells, whereas if I define it as not required, I simple add the first row and the subsequent rows manually in my story and everything is
fine...
Best,
Michael