Hi Folks, This is probably operator error, but i cannot find what I have done to cause the problem. I have had an Alphabetical Index in my document for a while. Recently, when I add text then add index entries, when I 'Update' the Alphabetical Index, my Table of contents is copied to the location (Index is gone). I do not know if this is related, but I have noticed the Index Entry box is larger and I cannot adjust the size. Kind Regards
Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you
Created attachment 125591 [details] This is a Word document Hi Folks, Here is the word document. It is an ongoing log of our travels. I used to have windows and thats where the doc was created. Some time ago, while on windows platform, the index was destroyed. Those are the places where "reference not found" appear. It was not long after that I went to the new platform. I have been slowly creating the new index, based on error reference and on our current daily goings on. Recently, maybe a week ago, I did an "Index Update" and what appeared was a copy of the Table of Contents Under the Alphabetical Index heading. Hope this helps, Kind regards
I reproduce with the document (update the index at the end of the document). Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ Build ID: e1ca24369142af3e721e789bf757be671e1905b7 CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on June 10th 2016 Ubuntu 16.04 Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
"Show Repairs" when .DOC is opened in MSO. And update does the same in MSO as in LO. I'll mark as Invalid because .doc is invalid. It's easy to create new A. Index that can be updated. Moral: use ODT to work as save as DOC as needed.