This is not that serious. But if you happen to add a new custom property via the API doc.getDocumentProperties().getUserDefinedProperties().addProperty('MyProp', 0, 'LibreOffice is the best') The newly created property will not show up in the File properties dialog until the file is saved and reloaded. Newly created properties created with the dialog will be displayed in the File properties dialog on subsequent views. The only workaround I have found is to save and reload file.
Can you share the full code, so we can quickly test? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the code.
Full code (in Python) is as follows: ============================================== import uno import unohelper g_ImplementationHelper = unohelper.ImplementationHelper() g_ImplementationHelper.addImplementation( None,"org.openoffice.script.MyImplementationForPythonScripts", ("org.openoffice.script.MyServiceForPythonScripts",),) def properties_test(aaa=1): doc= XSCRIPTCONTEXT.getDocument() doc.getDocumentProperties().getUserDefinedProperties().addProperty('MyProp', 0, 'LibreOffice is the best') =============================================== To reproduce. 1. Run code 2. Look at file Properties (custom tab) --> no property there 3. Save and reload file. 4. Look at file Properties (custome tab) --> property is shown tested on 7.2.7.2 Writer, Calc, Impress, Draw
Thanks, added it as a .py file in share/Scripts/python and ran. I reproduce. Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4172fcb7514ff8a9e9740ff0939e9a2f611edbce CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 25 January 2023
Dear wpeaton4, 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