Description: encountering the following exception error when using Mendeley citation plugin: LibreOffice version 6.0.2.1 Error: An exception occurred Type: com.sun.star.container.NoSuchElementException Message: . At line: 797 Steps to Reproduce: 1. Install Mendeley citation plugin 2. Type up text in document. 3. Insert citation from Mendeley. 4. press enter. Actual Results: Error message displayed. The following message displayed instead of citation: {Formatting Citation} Expected Results: Inserted citation in chosen format. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: This error occurs repeatably on 2 different machines in two different locations. The machines have 2 different versions of Windows installed Win 7 Starter and Win 7 Home. The Mendeley citation plugin used to work on both machines. User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
Did you report it to Mendeley?
Please bear in mind that those who test don't use this. So "Install Mendeley citation plugin" not clear, looks like testing this bug requires Mendeley desktop and registration. Please see https://ask.libreoffice.org/en/question/64799/mendeley-error/.
Gentlemen, Thanks for the good response. I have now gone the path of uninstalling LibreOffice 6.0.2.1 and installing version 5.4.5.1. The problem still persists. From bug report 100654,the problem appears to have emerged after/around LO v 5.0.x The problem manifests exactly the same as Bug 100654. This problem occurs repeatably on two different machines running two different versions of Windows. As far as I know, the Mendeley plugin has not changed. The plugin used to work satisfactory before upgrading to LibreOffice 6.xxx. Unfortunately I can't remember the version of LO I had before upgrading to LO 6.0.2.1. I had no formatting problem of the nature explained in the comments on bug 100654. Used to be able to enter references into Mendeley manually or by plugins, then cite them in my document using the Mendeley plugin in LO. Both my document and the Mendeley database resides in the cloud, so I was able to work from anywhere. In this case two different machines. No problems.
Can you try this https://ask.libreoffice.org/en/question/64799/mendeley-error/?answer=71099#post-id-71099 "I was having the same problem, but It seems to me that it is nether a Mendeley or LO problem, it has something to do with the file. Here is my work around: I started from scratch a new document and copied the text as "unformatted text" then I tried to add my citations with Mendeley again and they started working, the "{Formatting citation}" thing disappeared and incited the correct citation, then just save and remane your previous document and that is it. Hope this helps."
Dear Support, Herewith your copy of my message to the Mendeley support team. After some deliberation the following came to mind: The problem may be associated with a corrupted style sheet in the document. The problem may occur when the macro does not read the document style sheet, but references some style alien to the document. The problem may also occur when the text in the document has a style that is neither defined in the document style sheet nor in the default application (LibreOffice) style sheet. So the macro just hangs and the default coding type error message is displayed. A corrupted style sheet is a fairly common occurrence. The sensible way to get past this is to have a piece of code acting as a watchdog. Then, when the error occurs, the watchdog code should display an error message that is understandable to the non-coding user. Like me. The message could be thus: Possible undefined style encountered or corrupted document style sheet. Kindly refer to FAQ list. The error message should contain a hyperlink to the FAQ list. The FAQ list would then contain an instruction on how to get past the problem. In the present case, I am not sure of where the error occurred, so this message is also going verbatim to the support folks at the Document Foundation for their consideration. I hope this helps. Regards,
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20181009
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20181105