Description: It looks like the "Author" field recalled from Insert -> Field menu is different from the real "Author" field inserted from Insert -> Field -> More fields (CTRL + F12) Steps to Reproduce: 1. Open Writer 2. Click on Menu Insert -> Fields -> Author 3. hit CTRL + F9 to switch from field content (value) to its name 4. hit CTRL + F2 to open More Fields 5. Now select Tab "Document" 6. Select "Author" from Type and "Name" from Select, then click Insert Actual Results: You'll notice that the first field reports "DocInformation:Created" while the second is "Author" Expected Results: Both fields should be "Author" Reproducible: Always User Profile Reset: Yes Additional Info: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
Confirmed on Versione: 5.3.1.2 Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 Thread CPU: 4; Versione SO: Windows 6.1; Resa interfaccia: predefinito; Motore layout: nuovo; Versione locale: it-IT (it_IT); Calc: group
Already present in 3.3.0. I kind of think it's just somewhat bad/overlapping naming of actually different data (at least data that is stored in different places, I haven't looked at where they're coming from exactly), but it is confusing.
So this isnt something that can be easily fixed within the menu xml file and needs to be fixed at the code level in the uno command (.uno:InsertFieldCtrl). @Maxim, @Gulsah, @Regina: Anyone have some time to fix this bug that should likely be a 1-liner?
Notice that it could be that simple but also not, because sometimes the result is correct, even if the field is wrong. So it happens that "DocInformation:Created" gives back the author name as result... so there could be an error in this too. What I'd expect from such a field should be the creation (date?) of that document. But I may be wrong in this case. Anyway I suggest to investigate on what should be the output of this field and why it gives the author name.
There exists two places, where information about the authors and dates are stored, one is the meta.xml file and the other the content.xml file, inside the ODF package. With the fields in the tab DocInformation in the "More Fields" dialog, you get fields, which mirror the content of the meta.xml file. They are: For the initial author: Created Author = text:initial-creator = meta:initial-creator Created Time/Date = text:creation-time/date = meta:creation-date This information is stored once with the first saving. Using Field > Author you get an element text:initial-creator. For the current author: Modified Author = text:creator = dc:creator Modified Time/Date = text:modification-time/date = dc:date This information is updated with each saving. Both are shown in File > Properties in the tab "General". With the fields in the tab Document, you use the elements text:author-name (which combines first and last name) and text:author-initials for the initial author and the elements text:sender-firstname, text:sender-lastname and text:sender-initials for the subsequent authors. Content can be fixed by the checkbox. These information is only stored in the content.xml file. Because of the possibility to fix content, you can track intermediate authors. Unless fixed, the information about the current author is updated in the sender...-fields, when you change and save the document. You need to save the document, otherwise you might see an old value in the field. LibreOffice fills these fields automatically from the information in Tools > Options > LibreOffice > User data. For me the Field dialog is a little bit confusing in regard to authors, but it corresponds to the elements in the ODF file format and therefore I see no bug here. If you see inconsistent values, perhaps you have not saved your document or you have unchecked the option Automatically Update Fields?
(In reply to Gabriele Ponzo from comment #4) > Notice that it could be that simple but also not, because sometimes the > result is correct, even if the field is wrong. > > So it happens that "DocInformation:Created" gives back the author name as > result... so there could be an error in this too. (In reply to Regina Henschel from comment #5) > For me the Field dialog is a little bit confusing in regard to authors, but > it corresponds to the elements in the ODF file format and therefore I see no > bug here. If you see inconsistent values, perhaps you have not saved your > document or you have unchecked the option Automatically Update Fields? Well as Title is using 'DocInformation:Title' and Subject is using 'DocInformation:Subject', author should be fine using 'DocInformation:Created', though if you change the values in Tools > Options > LibreOffice > User data in an unsaved document, 'Author' will correctly update and 'DocInformation:Created' wont even if you updated fields.
(In reply to Yousuf Philips (jay) from comment #6) > Well as Title is using 'DocInformation:Title' and Subject is using > 'DocInformation:Subject', author should be fine using > 'DocInformation:Created', IMHO it should be Creator or CreatedBy but surely not Created which leads me thinking of a date or a Boolean... though if you change the values in Tools > Options > > LibreOffice > User data in an unsaved document, 'Author' will correctly > update and 'DocInformation:Created' wont even if you updated fields. Correct, so it looks like it is just a naming issue in those fields AND in menu / dialog items, because since they are two different data, they should be referred with different words in items. Even Author could be improved in LastAuthor or so, if I understood correctly its meaning, but that's not so important at the moment, and probably not so easy to change, if ODF tags are implied.
Gabriele Ponzo committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=badbdb41acf69e3eba4ca7253ec0218dc1e63d0a tdf#108224: rename insert author menu entry It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Gabriele Ponzo from comment #7) > IMHO it should be Creator or CreatedBy but surely not Created which leads me > thinking of a date or a Boolean... That is how ODF has decided to name the field in the XML, so if you think it should be changed, then you should take it up with them. > Correct, so it looks like it is just a naming issue in those fields AND in > menu / dialog items, because since they are two different data, they should > be referred with different words in items. They are the same data but one gets updated automatically and one gets updated only after opening a document. (In reply to Commit Notification from comment #8) > Gabriele Ponzo committed a patch related to this issue. > It has been pushed to "master": > > http://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=badbdb41acf69e3eba4ca7253ec0218dc1e63d0a > > tdf#108224: rename insert author menu entry This should be reverted as it isnt the right fix. The correct fix would be to change the underlying code to insert the 'Author' field rather than 'DocInformation:Created', if others agree this is the preferred field to insert.
(In reply to Yousuf Philips (jay) from comment #9) > This should be reverted as it isnt the right fix. The correct fix would be > to change the underlying code to insert the 'Author' field rather than > 'DocInformation:Created', if others agree this is the preferred field to > insert. I agree with Gabriele that just "Author" is misleading. And the solution with "First Author" makes it more clear. On the other hand most users likely want to insert the actual/current author. Tried the obvious thing and modified DI_CREATE|DI_SUB_AUTHOR to DI_CHANGE|DI_SUB_AUTHOR in https://opengrok.libreoffice.org/xref/core/sw/source/uibase/shells/textfld.cxx#715 but with not success on the fly.
Dear Gabriele Ponzo, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.
Dear Gabriele Ponzo, 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
Thanks for the reminder. I've just checked and it looks like it's been solved.