Loading Profile...
Table-data content not showing when including a page
We've recently upgraded from Confluence 2.9 to 3.0.2 and have discovered what appears to be a bug with Scaffolding which causes all {table-data} content on a page to be omitted when including the page onto another page. We were using Scaffolding 3.2.0 on both versions.
We have many documents that consists of a set of sub-pages for each chapter, with all of these being included together on another page to show the full document.
To do this we've been using the Reporting plugin as shown here:
With Confluence 2.9 this worked perfectly, except that in a few distinct cases the PDF export function gave an error as I've reported elsewhere. Now with Confluence 3.0 all {table-data} content from the sub-pages are simply omitted in the complete document, which of course is very unfortunate for us.
I would be very happy if you could help me out with a bugfix that could sort this problem out without having to modify all of our documents manually, but a workaround would be appreciated too!
We have many documents that consists of a set of sub-pages for each chapter, with all of these being included together on another page to show the full document.
To do this we've been using the Reporting plugin as shown here:
{report-block:injected=true}
{local-reporter:content:descendents}{local-reporter}
{report-body}
h1. {report-info:content:title|link=true}
{include:%content:title%}
{report-body}
{report-block}
With Confluence 2.9 this worked perfectly, except that in a few distinct cases the PDF export function gave an error as I've reported elsewhere. Now with Confluence 3.0 all {table-data} content from the sub-pages are simply omitted in the complete document, which of course is very unfortunate for us.
I would be very happy if you could help me out with a bugfix that could sort this problem out without having to modify all of our documents manually, but a workaround would be appreciated too!
I’m distressed
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Hi there,
Could you please create a bug report and I'll schedule it for investigation. Thanks!
David -
Inappropriate?Bug report has been created here:
http://greenhouse.customware.net/jira...
I’m confident
-
Inappropriate?Do you have a schedule or any expectations about when Scaffolding 3.2.1 will be out? It would be very good to have even a ballpark figure so I have something to tell my users.
-
Inappropriate?Hi,
Not sure if my problem is similar, but when i report on scaffold pages, the text-data field inside a table-data are not showing on the report using the
{report-column:title=Contexte Novell}{report-info:text:Contexte}{report-column}
In this case, the Contexte value refers to the text-data field.
Could someone tell me if the problem is similar? -
Inappropriate?Hi Michael, try 'data:Contexte' instead of 'text:Contexte'.2 Comments
Add a comment
This solves the problem
-
Hi David,
Sorry, i tried but no success. By the way, you are right, data should be used.
To get a better picture of the page, here is the complete code:
{table-plus:heading=true|enableSorting=true|autoNumber=true|autoTotal=false|columnTypes=S,S,S,S,S,S,S,I,X,S}
{report-table}
{local-reporter:content:descendents|source=INFO-SITE}
{report-column:title=Demandeur}{report-info:content:creator|link=false}{report-column}
{report-column:title=Page}{report-info:content:title|link=true}{report-column}
{report-column:title=Département}{report-info:data:Dept}{report-column}
{report-column:title=Service}{report-info:data:NomduSite}{report-column}
{report-column:title=Contexte Novell}{report-info:data:Contexte}{report-column}
{report-column:title=Type réseau}{report-info:data:RéseauType}{report-column}
{report-column:title=Type classe}{report-info:data:ClasseType}{report-column}
{report-column:title=IP Base}{report-info:data:réseau1}{report-column}
{report-column:title=IP Fin}{report-info:data:ipfin1}{report-column}
{report-column:title=Service Réseau}{report-info:data:ipserv}{report-column}
{report-empty}
This report is empty
{report-empty}
{report-table}
{table-plus}
The last 6 colums are having the same problem.
This is the code for one table in the scaffold formular:
{table-data:Novell}
|| Contexte NDS || Serveur Novell || IP Serveur ||
| {text-data:Contexte|width=150px}{text-data}| {text-data::Serveur|width=150px}{text-data} | {text-data:ip1|width=130px}{text-data} |
{table-data}
It seems correct to me... -
Hi David,
I found a solution to my problem.
I'm adding a local-reporter inside a report-column to focus on a field from a table-data. That works. I'm not sure it is elegant, but it works.
This is an example:
{report-column:title=Contexte}
{report-block}
{local-reporter:data:Novell}
{report-body}
{report-info:data:Contexte}
{report-body}
{report-block}{report-column}
hope this helps someone... -
Inappropriate?Hi Michael,
Yes this did help me - thank you.
However, I was wanting to try and do even more with this.
I would like the result of the report to provide individual rows in a table, allowing the table to be sorted.
eg. I have a parent page called school children ages. Under this I have two child pages each with a table of childrens names and ages for eg.
Child Page 1
Name Age
Bill 6
Bob 8
Child Page 2
Name Age
Jill 7
Jane 9
On the parent page to these child pages, I want a reporting table which combines the information from the two child page tables and allows a sort on the data - the resulting table on the parent page sorted by Age in Ascending order would be ...
Name Age
Bill 6
Jill 7
Bob 8
Jane 9
At the moment, the report that you have created (and I am not trialling) dispalys the results from both tables in one row, not allowing them to be sorted seperately.
I know this is a stretch, but would anyone out there have any advise on how this can be done? If there is a way, it will make me very very happy :)
I’m optimistic
1 Comment Add a comment
This solves the problem
-
Hi Michael (Roff, and possibly Regelin),
The {expanding-reporter} is what you need here. Assuming you have a {table-data} something like this on the Child pages:
{table-data:Children}
|| Name || Age ||
| {text-data:Name} | {number-data:Age|minValue=0} |
{table-data}
Then you can output a combined table on the parent with something like this:
{report-table}
{expanding-reporter:data:Children|as=Child}
{local-reporter:page:children}
{number-sort:data:Age}
{text-sort:data:Name}
{expanding-reporter}
{report-column:title=Name}{report-info:data:Name}{report-column}
{report-column:title=Age}{report-info:data:Age}{report-column}
{report-empty}_No children currently recorded._{report-empty}
{report-table}
Hope that helps! -
Inappropriate?Thanks David.
I have been working ok with the solution that Mr Regelin came up with but I will certainly give your suggestion a go as if it sorts the individual details into an ordered table, I think that will be very ideal for me.
Thanks again for your input.
Michael
I’m happy David is so clever
-
Inappropriate?OK David, I am close, but I don't have text being displayed.
This is the script I have used .....
{report-table}
{expanding-reporter:data:Milestones|as=Date}
{content-reporter:data:Milestones|space=CB|scope=CB:Corporate Initiatives > children}
{date-sort:data:Date}
{expanding-reporter}
{report-column:title=Project}{report-info:page:title}{report-column}
{report-column:title=Milestone}{report-info:data:Milestone}{report-column}
{report-column:title=Date}{report-info:data:Date}{report-column}
{report-column:title=Status}{report-info:data:Status}{report-column}
{report-empty}{_}No children currently recorded._{report-empty}
{report-table}
Milestones is the name of the Table on the childpage.
Date is the name of the column I want to sort by.
CB is the Space this info is in.
Corporate Initiatives is the parent page to the child pages that contain the information.
So what happens when I run this is a blank table with all the right columns comes up.
When I remove one of the rows from the Milestones Table in a child page, the blank table reduces by one row so it seems it is getting everything right, but it simply isn't displaying the information as I would require.
Can you see any obvious mistakes in the script I have used or make any suggestions which might help me track down the problem? -
Inappropriate?Hi Michael,
Your reporter is a bit off. Firstly, I'd avoid the {content-reporter} in this case. {local-reporter} is faster and simpler. And I forgot to account for the 'expanded' values in the output. So, you want something like this:
{report-table}
{expanding-reporter:data:Milestones|as=Milestone}
{local-reporter:page:children|source=CB:Corporate Initiatives}
{date-sort:data:Date}
{expanding-reporter}
{report-column:title=Project}{report-info:expanded:item > page:title|link=true}{report-column}
{report-column:title=Milestone}{report-info:expanded:Milestone > data:Milestone}{report-column}
{report-column:title=Date}{report-info:expanded:Milestone > data:Date|format=d MMM, yyyy}{report-column}
{report-column:title=Status}{report-info:expanded:Milestone > data:Status}{report-column}
{report-empty}_No children currently recorded._{report-empty}
{report-table}
I'm guessing a bit, since I don't know what your 'Milestones' table-data actually looks like...
-
Inappropriate?Spot on David. That works a treat.
I also wanted to keep any links that were in the table by using render=wiki but when I do it comes up with a link to a new page. Is there any way you can think of which will retain the link information from within a table?
Thanks again - this is really coming together.
I appreciate all your help. -
Inappropriate?I'm not quite sure what you mean about the links Michael. Can you give me an example of the table data that's not working as expected?
-
Inappropriate?OK, let me try and explain.
On the child page I am using a {table-data} and within this table data I populate a {text-data} field with the following [Link A] which produces a child page with the title Link A and also produces a link to that child page in the Table.
I want to be able to have this link follow through to the report.
In the previous way I was doing it with Mr Regelin's method I was able to achieve this with the use of the render=wiki on the
This is the segment of code which I used previously ...
{report-info:data:Milestone|render=wiki}
Now when I use something simlar for this part of the report, I only get a link to a new page which is blank. This new blank page is under the page which I am generating the report on. Does this have something to do with the use of the local-reporter rather than content-reporter?
One thing worth mentioning is I am generating the report in another space to where the information is available.
Let me know if you need more details.
DETAILS
Here is the Table-Data code from Space CR
{table-data:Milestones}
|| Key Milestone || Date || PMT Review? || Status ||
| {text-data:Milestone}{text-data} | {date-data:Date|format=dd MMM yy}{date-data} | {list-data:PMT}{list-option} No {list-option}{list-option} Yes {list-option}{list-data} | {list-data:Milestone Status}{list-option} On Schedule {list-option}{list-option} Delayed {list-option}{list-option} Complete {list-option}{list-data} |
{table-data}
Here is the Report-Table code located in Space Sandpit
{report-table}
{expanding-reporter:data:Milestones|as=Milestone}
{local-reporter:page:children|source=CB:Corporate Initiatives}
{date-sort:data:Date}
{expanding-reporter}
{report-column:title=Project}{report-info:expanded:item > page:title|link=true}{report-column}
{report-column:title=Milestone}{report-info:expanded:Milestone > data:Milestone|render=wiki}{report-column}
{report-column:title=Date}{report-info:expanded:Milestone > data:Date|format=d MMM, yyyy}{report-column}
{report-column:title=Status}{report-info:expanded:Milestone > data:Status}{report-column}
{report-empty}{_}No children currently recorded._{report-empty}
{report-table} -
Inappropriate?Hmm. Possibly because it's accessed via 'expanded' values, it's not rendering the markup in the context of the page being expanded on. And because pulling the pages from another space, the current page doesn't know where to execute either.
Haven't tried this, but you could try wrapping the whole report with this:
{report-on:source=CB:Corporate Initiatives}
...rest of report goes here
{report-on}
This should execute the whole report in the context of the 'CB:Corporate Initiatives' page, thus giving you correct local page links. -
Inappropriate?BINGO!
Thanks Dave, that works perfectly.
Kudos to you and your team for all the great support you provide everyone on these forums!
I’m very happy
EMPLOYEE
