Bug 51303 - MAILMERGE: Add option to prevent printing of graphic in otherwise empty label
Summary: MAILMERGE: Add option to prevent printing of graphic in otherwise empty label
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-21 08:26 UTC by Le Gluon du Net
Modified: 2014-06-01 20:30 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
labels odt file with a picture (16.17 KB, application/vnd.oasis.opendocument.text)
2012-06-21 08:26 UTC, Le Gluon du Net
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Le Gluon du Net 2012-06-21 08:26:16 UTC
Created attachment 63312 [details]
labels odt file with a picture

Problem description: 

Steps to reproduce:
1. make labels in writer and merge the document with a database
2. put a picture and your fields in the first label and synchronize all the labels
3. print your labels: Writer print the picture even if the field is empty (no more records in the database). So if you have only two labels to print on the 16 labels of your paperlabel, all the labels on the paper have the picture...

Current behavior: printed label with empty field (empty label) have picture

Expected behavior: writer should not print picture on empty label

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:13.0) Gecko/20100101 Firefox/13.0.1

Thanks for your help.
Comment 1 Cor Nouws 2013-10-27 15:27:10 UTC
Hi,

thanks for the issue.
Have you tried to do something with conditional formatting of a paragraph with the picture in it, in the label, based on other fiels in the label?
(Be ware of the line ends, rather then paragraph breaks) ?
I bet it would be possible.
(You may ask help from other users of course too
  http://www.libreoffice.org/get-help/ )

If that is not possible, it could be an enhancement request..

Cheers,
Cor
Comment 2 QA Administrators 2014-05-17 00:34:17 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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
Comment 3 QA Administrators 2014-06-01 20:30:13 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO