Created attachment 143382 [details] To demonstrate empty date field When a form showing a date field containing a valid date is exported as a PDF file with "Create PDF form" checked, the resultant PDF file shows an empty field. To demonstrate :- 1. Open the attached "Test5 - Date.odb" database file. 2. Open form "Form1" - this will display a form containing a single field of type date containing "31/12/81". 3. From the menu bar, select "File", then "Export as PDF..." 4. On the right hand side of the resultant "PDF Options" panel, check only "Create PDF Form" and "View PDF after export", then select "Export" 5. Save the resultant PDF file to a convenient place - it will then be automatically displayed. 6. Observe that the PDF file contains a single empty editable field - it has not been preset to contain "31/12/81"
Bug 107402 (now shown as WORKSFORME) described similar symptoms as part of a more general complaint about exporting as PDF. The current bug report is more specific, so should be easier to reproduce (and hopefully fix). Should bug 107402 be marked as a duplicate of this one (118614)?
(In reply to Alan Wheeler from comment #0) > Created attachment 143382 [details] > To demonstrate empty date field > > When a form showing a date field containing a valid date is exported as a > PDF file with "Create PDF form" checked, the resultant PDF file shows an > empty field. > Yes, I can confirm that there is no way to get that default string into the form control in the PDF file. Doing a search just nor though I find that even with Adobe tools the solution to default dates as strings (and other strings defaults) is by using a snippet of javascript embedded in the PDF file. The adobe tools offer a scripting environment similar to that in LibreOffice for basic (etc.). So, I'm not sure this is an error in LibreOffice. It would be great if there were an OS tool that would let you apply the solution from recommended in the Adobe forums.
I have discovered a workaround. If, after the form is displayed, but before exporting as PDF, the date field is modified (I added a space after "31/12/81", then removed the space), the field in the resultant PDF file HAS been preset to "31/12/81". If the form contains several date fields, it is necessary to modify each one in order for all the relevant fields on the resultant PDF file to have been preset.
Tested with LibreOffice 3.3.0. Exactly the same symptoms as described in the original bug report are exhibited using 3.3.0, so set version to "Inherited from OOo"
Can you help to me to fix my britness issue in ubuntu os 18.04<a href="https://lyricspay.com">.</a>
Can you help to me to fix my britness issue in ubuntu os 18.04 <a href="https://sbhilyrics.com/">.</a>
Thanks for sharing this
The issue is only reproducible if you don't change the value in the form, If you change it to another date and then you save to PDF, the date is there in the PDF
Still present in LibreOffice 7.4.4
Dear Alan Wheeler, 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
Still present in LibreOffice 24.8.4.2 Version info :- Version: 24.8.4.2 (X86_64) / LibreOffice Community Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 CPU threads: 4; OS: Windows 11 X86_64 (10.0 build 22631); UI render: default; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded