Created attachment 140035 [details] Exampe for Auto text does not properly insert field variables If I use AutoText to insert a text with a "Show variable" statement in it, the content of variable is not shown correctly. Instead of the Text "SQ-XXX" a "0" is shown. If I click on the field it correctly shows "Show variable" with the correct name Steps: - Set a text variable to some string. - Write some text with show variable in it. - Put that text into AutoText - Insert the AutoText again. I've attached a document showing the issue. First the variable is defined, then two times used manually and then one time inserted from AutoText. The Incremental counter after the variable works just fine but the text variable is not.
(In reply to sven.neuz from comment #0) > - Put that text into AutoText How do I do this? I tried to figure AutoText out today for another report, but failed.
- Write any text, with formatting, table, ... - Select the text - Press Cntl+F3 - Select a category - Enter a name (important!) - Click on AutoText => New
Note: To reproduce my issue, the AutoText needs to contain a field with function "Show variable"
Thank you very much for the explanation. I was able to test bug 115489 thanks to it. I could not reproduce bug 115489, though, so maybe you could try it. Actually, I could not repro your problem either. I selected the first SQ-XXX and turned it to an autotext entry. When I insert it either from the autotext dialog or with shortcut + F3, I get SQ-XXX. Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: b8fe96f1da2c42c04a8094ca8c57d49763b7bded CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on March 8th 2018
(In reply to Buovjaga from comment #4) > Thank you very much for the explanation. I was able to test bug 115489 > thanks to it. I could not reproduce bug 115489, though, so maybe you could > try it. Ok, forget it: the reporter was talking about some 3rd party software.
Did you add the complete document to AutoText? Please try again and DO NOT SELECT THE FIRST LINE. Why? The first line defines the variable PROJ which is referenced in the rest of the text. Select everything but the first line, then add it to AutoText. Open a new document. Insert a field with Set Variable. Variable name = PROJ, value = anything Insert AutoText. The variable will not be displayed.
(In reply to Sven Neuz (SERPENTEQ) from comment #6) > Select everything but the first line, then add it to AutoText. > > Open a new document. > > Insert a field with Set Variable. Variable name = PROJ, value = anything > > Insert AutoText. The variable will not be displayed. Ok, I repro. Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: b8fe96f1da2c42c04a8094ca8c57d49763b7bded CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on March 8th 2018
So this affects all platforms, not just Windows. I updated the issue accordingly. Hopefully this will be fixed soon as it has a huge impact on the usage of AutoText.
I found a workaround. -Insert the AutoText -Save and close (!!!) the document -Open it again -Select the entire document -Press F9 -Field variables will be updated and show the correct value Closing the document is essential. It will not work otherwise.
Dear Sven Neuz (SERPENTEQ), 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The bug is still present in the most recent version: Version: 6.2.4.2 (x64) Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64 CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: threaded
Dear Sven Neuz (SERPENTEQ), 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Repro in: Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded The text variable is "0", but the counter is correct. Workaround from comment 9 works.
Code pointer: https://opengrok.libreoffice.org/xref/core/sw/source/core/unocore/unofield.cxx?r=4df22b4d#1763 Somehow the subtype is not correctly retrieved for the field which leads to a formatting of the text as formula which is 0.