Expand my Community achievements bar.

SOLVED

Blank pages being inserted between table header and body

Avatar

Level 1

Hi,

When I populate a growable textbox in a table body row with large amounts of text (about 2 pages worth) I get a blank page being inserted after the first table header row before the first table body row.

I have attached an example form that shows this problem and also attached the example text in a seperate textfile.

Any suggestions on how to fix this problem would be greatly appreciated.

Thanks

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

This is a case where using a table is making this more difficult. I created another sample that shows how to do this.

Note that I set the target version to 9 (I seem to remember that fields where not allowed to break across

pages in version 8 but I am not 100% sure).

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

This is a case where using a table is making this more difficult. I created another sample that shows how to do this.

Note that I set the target version to 9 (I seem to remember that fields where not allowed to break across

pages in version 8 but I am not 100% sure).

Paul

Avatar

Level 1

Managed to figure it out, it was caused by the form not being able to find a common split point between the two side by side text boxes.

There is an excellent blog post about this problem at http://blogs.adobe.com/formfeed/2009/06/displaying_parallel_columns_of.html

I had tried his suggestions earlier but it turned out that even though both text boxes used the same font/size etc, having them vertically center align was causing the problem and making them vertically top align solved it.

Thanks also to Pgurrett about the version 8.0 compatability tip as version 8.0 does not support content splitting accross pages.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----