Red Hat Bugzilla – Bug 854775
Table cols breaks sandboxing
Last modified: 2014-10-19 19:01:26 EDT
*ERROR: Fatal Table Error* Table (Broker List URL Options) contains invalid data
Attribute cols (2) does not match number of entry elements (XML::Element=HASH(0xaf61378))
at /usr/share/perl5/Publican/Builder.pm line 467
during publican build.
This occurs if you create a topic with a table with a mismatch between the tgroups col attribute and the number of columns in the row.
Tough one to catch because the <tgroup cols="2"> attribute has to match the number of <entry> elements inside the <row>.
Doing an xmllint validation using the Docbook DTD doesn't even catch this, so the deathstar editor doesn't get it.
Ideally this would be sandboxed so that a topic containing a rogue table doesn't break the whole build.
CSProcessor client version: 0.26.5
JAVA: java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.4) (6b24-1.11.4-1ubuntu0.12.04.1)
OpenJDK Client VM (build 20.0-b12, mixed mode, sharing)
Fixed in version 0.27.0.
Tables in topics are now validated when building to ensure that table or informaltable have the required number of entry for each row (or td/th for tr rows). Note: You are allowed to have less entries than the value in "cols", but you can't have more.
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.