Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

2-column layout with correct page breaks

Avatar

Level 4

Hi there,

I am trying to produce a 2-column layout in my form.

The problem is: These columns stretch over more than one page and I just cannot get the page breaks right.

I have a flowed layout with two adjacent subforms which form my columns. In these column subforms I fill lots of data from XML.

Problem 1 is: At the end of the page I miss about 5 lines. They vanish in the page break.

Problem 2 is: My second column starts getting filled only on the second page (which happens to be the page where the first column ends).

I also tried this with one table with exactly one row. But there all lines after the first page disappear and I get empty pages instead.

Has anyone ever come across this problem?

What is a good safe way to build dynamic 2-column forms?

Ulrich

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

You won't be able to flow beyond the one page and then go back to a previous page .....the data woudl have to be split up so that the complete layout of a page woudl have to occurr before moving to the next page.

You cannot go back in the layout after a page has been completed....sorry it just cannot do that.

Paul

View solution in original post

4 Replies

Avatar

Former Community Member

So is the goal to continue column 1 on Page 2 or at the top of column 2 on Page 1 (like a newspaper)?

Paul

Avatar

Level 4

Hi Paul,

the former. It is NOT like in a newspaper where the content runs from left to right from one column into the next and finally into the leftmost column of the next page.

Im my case the content of the 2 columns is completly separat from each other: The data in the left column is distincly left-column-only data. As is the data in the right column distinctly right-column-only data.

Actually it is not even sure, that the left column is longer than the right.

It is absolutly o.k. to have  3 pages where the left column is empty and only the right column is filled.

An example would be: Technical data of two articles to be compared: Left is the Mercedes-data and right is the BMW-data.

Ulrich

Avatar

Correct answer by
Former Community Member

You won't be able to flow beyond the one page and then go back to a previous page .....the data woudl have to be split up so that the complete layout of a page woudl have to occurr before moving to the next page.

You cannot go back in the layout after a page has been completed....sorry it just cannot do that.

Paul

Avatar

Level 4

Sorry to hear that - but it sounds reasonable.

I chose the second best choice and force the data into a more tabular format. Doesn't look as good. But that just are the technical limitations.

Thanks a lot for the answer!

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] ----