Description: Similar to #123729 the "Author" information can't be inserted through the menu item "Insert > Field command > Author" (Einfügen > Weitere Feldbefehle > Autor" in the iOS app. Steps to Reproduce: 1. Create/open a document in the iOS app 2. Click the menu entry "Insert > Field command > Author" Actual Results: The author name is not inserted. Expected Results: The author name (maybe taken from the device settings, see #123729) could be used. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 150062 [details] Printscreen showing the menu entry
Author is the author of the document. When a new document is created, the author should be the owner of the device. I don't know how to push this info to LibreOffice.
Maybe this is of some help? https://stackoverflow.com/questions/37397814/ios-get-users-personal-information-from-the-device#37398043 However I'm not sure, if in my use case the users will have an iCloud account (the public cloud usage is very limited by purpose). Is it possible to run an iPad w/o such an account? Maybe a "first start" dialog who askes for some details and then save them in the app directory could be a solution? Thanks for looking into this!
Created attachment 150972 [details] Adding author information to iOS Collabora App settings
Created attachment 150973 [details] User data options in libreoffice desktop version
(In reply to Andras Timar from comment #2) > Author is the author of the document. When a new document is created, the > author should be the owner of the device. I don't know how to push this info > to LibreOffice. Alternatively, additional fields in the iOS-Settings of the Collabora App could be used, see attachment "author_information_in_ios_collabora_settings.png". The fields could allow the user to enter information similar to the fields in the libreoffice desktop version under "Tools > Options > LibreOffice > User Data", see "libreoffice_desktop_tools_options_user_data.png" attached. Further, common settings for a group of devices (e.g., the template URL for all devices of a school or business) could be moved and configured following an accepted standard such as "AppConfig", see #124930.
Dear Nicolas Christener, 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
The iOS related issues are tracked on GitHub now, let's close this issue here. You can follow the status of this issue here: https://github.com/CollaboraOnline/online/issues/1812