Issue 76273 - Insertion of TOC leads to deletion of page break
Summary: Insertion of TOC leads to deletion of page break
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 2.2 RC4
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@sw
URL:
Keywords: oooqa
: 76323 77150 77850 79344 80346 80487 (view as issue list)
Depends on:
Blocks:
 
Reported: 2007-04-11 17:01 UTC by wolle2000
Modified: 2013-08-07 14:42 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description wolle2000 2007-04-11 17:01:47 UTC 
This is imho a bug in version 2.2 and can be reproduced, doing the following:
Write some words on a first page. Then insert a manual break. Insert a TOC 
(uncheck "protected against manual changes"). Now, when you go to "Format - 
Paragraph" you can see on the tab "Text Flow" that "Page Break" is checked.
Now safe and close the document. Reopen it and you will see that the page break 
has disappeared, the TOC is on the first page and its formatting is destroyed 
(where the latter is not really the problem).

Wolfgang
Comment 1 Regina Henschel 2007-04-11 17:19:51 UTC 
As described. The error seams to happen on saving, because such a document from
2.2 has the same error when opened in 2.1

Formatting in 2.1 and save and open in 2.1. is OK.
Comment 2 michael.ruess 2007-04-11 20:09:45 UTC 
Reassigned to ES.
Comment 3 frank.meies 2007-04-12 05:16:26 UTC 
FME: One for me. Regression from cws swautomatic01.
Comment 4 frank.meies 2007-04-12 06:11:26 UTC 
.
Comment 5 frank.meies 2007-04-12 09:13:27 UTC 
FME: Fixed in cws swautomaticfixes, node.cxx rev. 1.34.92.1.
Comment 6 andreas.martens 2007-04-16 12:26:47 UTC 
*** Issue 76323 has been marked as a duplicate of this issue. ***
Comment 7 wolle2000 2007-04-16 15:15:44 UTC 
Why ist Target Milestone still 2.3, when it is already fixed? Can't it be 2.2.1
 ?
Wolfgang
Comment 8 frank.meies 2007-04-24 11:48:12 UTC 
FME->WOLLE2000: The issues considered for OOo 2.2.1 have to meet some very
strict criteria, among them the potential risk and the required QA effort. I'm
sorry but from this point of view this has to wait till OOo 2.3.

FME: Ready for QA.
Comment 9 eric.savary 2007-05-10 11:28:37 UTC 
*** Issue 77150 has been marked as a duplicate of this issue. ***
Comment 10 eric.savary 2007-05-10 11:50:03 UTC 
Reassigning to me
Comment 11 eric.savary 2007-05-10 11:57:57 UTC 
Verified in CWS swautomaticfixes
Comment 12 eric.savary 2007-05-30 15:31:09 UTC 
*** Issue 77850 has been marked as a duplicate of this issue. ***
Comment 13 alexandervanloon 2007-06-12 20:36:28 UTC 
So according to the comments on this bug a fix was committed on 10 May. The
latest development release is m213 which is released on 24 May. Why can I still
reproduce this bug with that release? Is the fix not included in m213 for some
reason?
Comment 14 frank.meies 2007-06-12 21:20:21 UTC 
Because this bug has been fixed in a cws which has been integrated into m214:

http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fswautomaticfixes
Comment 15 eric.savary 2007-07-06 15:43:13 UTC 
Ok in m219
Comment 16 michael.ruess 2007-07-09 15:40:13 UTC 
*** Issue 79344 has been marked as a duplicate of this issue. ***
Comment 17 eric.savary 2007-08-08 10:49:20 UTC 
*** Issue 80346 has been marked as a duplicate of this issue. ***
Comment 18 michael.ruess 2007-08-09 09:11:44 UTC 
*** Issue 80487 has been marked as a duplicate of this issue. ***