Description: Hi, I'm writing a document in which page numbers are placed in the Footer. With Edit Fields I set "offset" to 36 (my need). Without further configuration, from page 43 onwards the page number just got empty, although showing the grey zone of the field. A previous document with pages 1..36 everything worked just fine. I'm using Windows 10 Pro, and got: Version: 6.3.6.2 (x64) Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-GB Calc: threaded from Writer. Thanks Pedro Steps to Reproduce: 1.Insert > Header and Footer > Footer > Default Style 2.(cursor on footer) Inert > Page Number 3.Right-click on page number (has a 1) 4.Set offset to 36 and close form Actual Results: Page number field in footer got grey without any number Expected Results: Should appear 37 Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.6.2 (x64) Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-GB Calc: threaded
Pedro, as LO help says (but not very clear to me): "If you want to change the actual page number and not the displayed number, do not use the Offset value. To change page numbers, read the Page Numbers guide." [1] So I guess your document 42 pages and that's the reason why page numbering stops at 43. You can define page number with Insert => More Breaks => Manual Break, but not on the first page of you document. So I think it would be an enhancement request to start document with a customized page number. Do you agree and would this solve your problem? [1] https://help.libreoffice.org/7.0/en-GB/text/swriter/01/04090001.html?System=WIN&DbPAR=WRITER&HID=modules/swriter/ui/flddocumentpage/FieldDocumentPage#bm_@@nowidget@@
Thank you for reporting the bug. I can not reproduce the bug in version 6.4.4.2 or 7.1.0.0.alpha0
(In reply to Dieter from comment #1) > You can define page number with Insert => More Breaks => Manual Break, but > not on the first page of you document. So I think it would be an enhancement > request to start document with a customized page number. Do you agree and > would this solve your problem? Pedro: please respond.
Hi, thanks for your support. I'm upgrading to the new release and will test against this issue. If I get the same issue in the new release too, I'll post a new case and refer to this. For the moment, please close this case. Thanks and kind regards Pedro
(In reply to Pedro from comment #4) > For the moment, please close this case. Better to leave status to NEEDINFO, until you're able to test with a new release.
Dear Pedro, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Pedro, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp
*** This bug has been marked as a duplicate of bug 35694 ***