Loading Profile...
Error message: "You must have a data row." ?
Hi all,
I'm a scaffolding newbie, so please be gentle. I've searched the forum, but have not found answer to my problem. I'm adding the {table-data} macro to an existing table, to allow dynamic adding of rows. Everything looks great except I get the error message: "You must have a data row."
My markup looks as follows:
{scaffold:ServiceTable}
{table-data:addRow|initialRows=1}
||Customer ||Node / Zone / User ||IP ||DB ||Cluster ||Service ||Service Access ||SLA ||Status ||
| {text-data:Customer}{text-data} | {text-data:Node/Zone/User}{text-data} | {text-data:IP}{text-data} | {text-data:DB}{text-data} | {text-data:Cluster}{text-data} | {text-data:Service}{text-data} | {text-data:ServiceAccess}{text-data} | {text-data:SLA}{text-data} | |
{table-data:addRow}
{scaffold}
Any help would greatly appreciated!
Thanks,
Lotta
I'm a scaffolding newbie, so please be gentle. I've searched the forum, but have not found answer to my problem. I'm adding the {table-data} macro to an existing table, to allow dynamic adding of rows. Everything looks great except I get the error message: "You must have a data row."
My markup looks as follows:
{scaffold:ServiceTable}
{table-data:addRow|initialRows=1}
||Customer ||Node / Zone / User ||IP ||DB ||Cluster ||Service ||Service Access ||SLA ||Status ||
| {text-data:Customer}{text-data} | {text-data:Node/Zone/User}{text-data} | {text-data:IP}{text-data} | {text-data:DB}{text-data} | {text-data:Cluster}{text-data} | {text-data:Service}{text-data} | {text-data:ServiceAccess}{text-data} | {text-data:SLA}{text-data} | |
{table-data:addRow}
{scaffold}
Any help would greatly appreciated!
Thanks,
Lotta
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
The best answer from the company
-
The parser for {table-data} isn't quite as flexible as the standard wiki table parser. In particular, make sure you have at least one space on either side of cell boundaries (ie " || " and " | "). However, I think the main problem you have here is that you have an extra "addRow" in your closing macro for {table-data}.
Also, I don't recommend you use the {scaffolding} macro any more. It has been optional since Scaffolding 2.0, and only serves to confuse things generally.
So, try this for your example:
{table-data:ServiceTable|initialRows=1}
|| Customer || Node / Zone / User || IP || DB || Cluster || Service || Service Access || SLA || Status ||
| {text-data:Customer}{text-data} | {text-data:Node/Zone/User}{text-data} | {text-data:IP}{text-data} | {text-data:DB}{text-data} | {text-data:Cluster}{text-data} | {text-data:Service}{text-data} | {text-data:ServiceAccess}{text-data} | {text-data:SLA}{text-data} | |
{table-data}
The company and 1 other person say
this answers the question
-
Inappropriate?The parser for {table-data} isn't quite as flexible as the standard wiki table parser. In particular, make sure you have at least one space on either side of cell boundaries (ie " || " and " | "). However, I think the main problem you have here is that you have an extra "addRow" in your closing macro for {table-data}.
Also, I don't recommend you use the {scaffolding} macro any more. It has been optional since Scaffolding 2.0, and only serves to confuse things generally.
So, try this for your example:
{table-data:ServiceTable|initialRows=1}
|| Customer || Node / Zone / User || IP || DB || Cluster || Service || Service Access || SLA || Status ||
| {text-data:Customer}{text-data} | {text-data:Node/Zone/User}{text-data} | {text-data:IP}{text-data} | {text-data:DB}{text-data} | {text-data:Cluster}{text-data} | {text-data:Service}{text-data} | {text-data:ServiceAccess}{text-data} | {text-data:SLA}{text-data} | |
{table-data}
The company and 1 other person say
this answers the question
3 Comments Add a comment
This answers the question
-
This parsing issue is pretty subtle for newcomers! Perhaps there should be warnings on the base documentation.... -
Well, there is a fairly explanatory comment about the parsing issue above on the wiki documentation for table-data. The core issue turned out to be that there was no proper closing {table-data} macro, which is a more general macro usage issue.
-
ok...sorry...still learning where to look. When I put the spaces in I get a "\" put in front of the "|" when I get back from preview into the wiki markup. Posted separately on this
-
Inappropriate?Wonderful, that solved that problem, thank you.
Now, I've got another problem, following the first: the rows added "inside" {table-data} doesn't connect to the existing (old, created before the macro) table rows. I get a table (created by the macro), and then space, then the old table. When I move the ending {table-data}, I get the same error as before (for obvious reasons).
Thanks for the prompt reply!
I’m confused
-
Inappropriate?What's your complete wiki markup?
-
Inappropriate?Ok, I'll post a subset, confidentiality and such:
{table-data:addRow|initialRows=1}
|| Customer || Node / Zone / User || IP || Cluster || Service || Service Access || Status ||
| {text-data:Customer}{text-data} | {text-data:Node/Zone/User}{text-data} | {text-data:IP}{text-data} | {text-data:Cluster}{text-data} | {text-data:Service}{text-data} | {text-data:ServiceAccess}{text-data} | {text-data:Status}(/){text-data} |{table-data}
| [ActualCustomer|HOST:Customer] | stz2 | 123.4.5.6 | B | Bunch of services | [http://customer.hosting.company.com/s...|http://customer.hosting.company.com/smscaa] (not accessible by webbrowser) | (/) |
And then 20 rows or so of this type of info.
/Thanks.
I’m confident
-
Inappropriate?Ah, I see. There isn't any way to automatically transfer that data into the {table-data}. You'll have to manually add rows, copy values, and then remove the old table from the page.
EMPLOYEE
