Description: I want to print individual form letter - file format ODF (.odt). But in the resulted documents the database connection is not expired and mail merge fields are not deleted. Steps to Reproduce: 1.I want to print individual form letter - file format ODF (.odt). Actual Results: But in the resulted documents the database connection is not expired and mail merge fields are not deleted. Expected Results: In the resulted documents the database connection is not necessary and name and address are a normal text. Reproducible: Always User Profile Reset: No Additional Info: this bug is also in StarOffice 5.2
Mail merge: Print into single odt files with unwanted results. . 1. Fields instead of regular text . When you "print" your source file (mail merge) into several single odt documents, the single documents contain the specific fields not as (plain) text but as a field. Double click on them leads to data base. Versions: LibreOffice 7.6.4.2 and many other versions; beginning on StarOffice 5.2, OpenOffice 3.4.1 and still present in OpenOffice 4.1.15 and latest LibreOffice versions. When printing in PDF files, there are no fields. . 2. Comments remain in single odt files (mail merge) . Same problem with comments. If you print a source file into several single odt documents, these contain the comments, even if not selected in print properties. If you print into only one collecting odt file the comments are regarded as well in contradiction to to print properties. Versions: LibreOffice 7.6.4.2 and many other versions; OpenOffice 4.1.15 and some latest LibreOffice versions. When printing in PDF files, there are no comments, according to print properties.
Created attachment 192455 [details] Single mail merged document
Dear Pit Zaclade, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug