Problem description: Steps to reproduce: 1. Opret rapport i A5-format 2. Tilføj sidehoved og sidefod Current behavior: Sidehoved vises ikke på første side. Det gør den heller ikke ved A4 format. Der vises kun data på hver anden side. Hvis sidefod fjernes, vises der data på hver side. Expected behavior: Operating System: Windows 7 Version: 4.0.0.3 release
Please read our FDO-policy (https://wiki.documentfoundation.org/FreeDesktop_Rules_Procedures#Policies) and report your bug in English. None of our developers and bug triagers can read/speak Danish, so this bug report can't be reproduced and fixed. Kind regards, Joren
Header in reports do not appear on the first page. When the footer is visible, only data are shown on every second page, when the page size is A5 and column shape are single column.
@Ove, isn't this a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=60888 you reported also? Could you create an attachment, which shows the wrong behavior?
*** Bug 60888 has been marked as a duplicate of this bug. ***
Created attachment 75241 [details] Missing header
Created attachment 75242 [details] Empty page
There must be some different information. When I create a report, set page to A5, set page-header with some text and page-footer with page-number it works. Without example-database or more details about grouping and group-header and group-footer I could not confirm this bug.
I connect to an Access database. Maybe that is the cause. I have now tried to build a new database in the Libre Office format, and that seems to work. I think, you may close the bug.
I close this bug as Resolved → Worksforme. See https://bugs.freedesktop.org/show_bug.cgi?id=60953#c8
Created attachment 76284 [details] Choice of Force new page
I have found out, that the error come, when I choose "After section" in the field "Force new page". I don't think, it's an error.
Yes, of course this is a bug. I have tried this. When you change the section detail to "Before section" or "Before and After section" it works right, not when set to "After section". I will create an attachment as soon as possible. Set this bug as "Reopened".
Created attachment 76286 [details] No Header and Footer on first Page with Pagebreak after Section Detail Open The attached Database and open the report. You see, that there is no page-header and no page-footer on the first page. Section "Detail" is set to "Page-Break after Section". Try to set this to "Page-Break before Section" - works right. Try to set this to "Page-Break before and after Section" - works also.
Just testing all bugs from Report-Builder. This bug first appears in the oldest available version of LO, 3.3.0 beta1. So I set the first available bugzilla-version, 3.3.0 release.
Adding self to CC if not already on
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Bug still exists with LO 5.1.0.2, OpenSUSE 42.1 Leap, 64bit rpm Linux.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Bug still exists in LO 5.3.1.1, OpenSUSE Leap 42.1 64bit rpm Linux.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Ove Hansen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists in LO 6.4.2.1, OpenSUSE 15.1 64bit rpm Linux.
Created attachment 175867 [details] Result of a test Robert: I tried this patch: diff --git a/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java b/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java index d8e50d2d4991..6888da1d204b 100644 --- a/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java +++ b/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java @@ -979,6 +979,12 @@ public class TextRawReportTarget extends OfficeDocumentReportTarget performStyleProcessing(attrs); } + if (isSectionPagebreakAfter(attrs)) + { + // force a pagebreak .. + setPagebreakDefinition(new PageBreakDefinition(isResetPageNumber())); + } + final String namespace = ReportTargetUtil.getNamespaceFromAttribute(attrs); final String elementType = ReportTargetUtil.getElemenTypeFromAttribute(attrs); final AttributeList attrList = buildAttributeList(attrs); I'm not sure what should be the result of After, could you tell me if the pdf is ok or not?
Created attachment 175870 [details] It should look all the same: Pagebreak should have nothing to do with header and footer, Hi Julien, Changing the page break in Detail shouldn't change anything of the header and footer. So the bug is: On first page has to appear Page-Header on the top and Page-Footer on the button. And this won't happen if Detail is set to "page break after section".
Created attachment 175876 [details] Result of a test 2 With this patch: diff --git a/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java b/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java index d8e50d2d4991..398dd83d42a2 100644 --- a/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java +++ b/reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java @@ -731,8 +731,7 @@ public class TextRawReportTarget extends OfficeDocumentReportTarget { expectedTableRowCount = trc; } - - if (isSectionPagebreakBefore(attrs)) + if (isSectionPagebreakBefore(attrs) || isSectionPagebreakAfter(attrs)) { // force a pagebreak .. setPagebreakDefinition(new PageBreakDefinition(isResetPageNumber()));
Thank you Robert for your feedback. I gave another try in my previous comment. It would be very useful you may be able to build sources so I could propose you to test patches. Of course, I haven't forgotten that you'd begin to code soon! :-p