Bug 69284

Summary: MAILMERGE: First page of mail merge has differ page style
Product: LibreOffice Reporter: Arttapong CH. <arttapong.ch>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: medium CC: bfo.bugmail
Version: 4.1.1.2 release   
Hardware: Other   
OS: Windows (All)   
Whiteboard: BSA
i915 platform: i915 features:
Attachments: Zip file of 3 screenshots show - mail merge field, first page, other pages

Description Arttapong CH. 2013-09-12 18:24:13 UTC
Created attachment 85734 [details]
Zip file of 3 screenshots show - mail merge field, first page, other pages

Problem description: First page of mail merge page style differ from expected as others 

Steps to reproduce:
1. Create new text document and setting top margin to 5 cm (defualt is 2 cm). Add text and data field then save as new document template (.ott)
2. Create new document from .ott file in step 1.
3. Create mail merge using mail merge wizard and filter records in step 3 of wizard.
4. Edit individual document in step 7 of wizard. The first page has top margin set as 2 cm while others are 5 cm.

Current behavior: The page style of first page has not setting as expect as in template.

Expected behavior: All page of mail merge has the same page style as expecting in template.

              
Operating System: Windows XP
Version: 4.1.1.2 release
Comment 1 Arttapong CH. 2013-09-12 18:32:10 UTC
If you want to set all page as expected page style using Menu Format > Page and click OK button (without change anything).
Comment 2 bfoman 2013-09-12 23:27:12 UTC
Is this the same as bug 69282?
Comment 3 Arttapong CH. 2013-09-13 08:25:35 UTC
(In reply to comment #2)
> Is this the same as bug 69282?

Yes. When I post bug 69282 the system not response, so I post it again, but I can not remembered all detail that I've post.
Comment 4 bfoman 2013-09-13 09:31:57 UTC
Clone of bug 69282.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.