Problem description: I've created a table of content in a Writer document. I added some extra entries manually (select text and the select in the menu Insert > Indexes & Tables > Entry...). The manually added entries are missing the hyperlink function. Nothing happens when I ctrl + click on an entry. The other entries created from the Heading 1,2,3.. are active. Cross-link to a forum question: http://ask.libreoffice.org/en/question/27880/hyperlink-is-missing-for-toc-entries-based-on-inserted-index-entries/ Steps to reproduce: 1. Highlight text somewhere in document. 2. Insert > Indexes and Tables > Entry... > Index of "Table of Contents" > click Insert. 3. Right-click on ToC > Update Index/Table. Current behavior: The newly added TOC entry is inactive for CTRL-click, no hyperlink is present Expected behavior: The entry should present a hyperlink as well ad other predefined Heading entries. Operating System: Windows 7 Version: 4.1.4.2 release
Created attachment 91529 [details] ODT/PDF demonstrating the problem as reported. Example was created under Ubuntu 10.04 x86_64 running v4.1.4.2 Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72. Opening the example under the same OS using: - v3.3.0.4 OOO330m19 Build: 6 - v3.4.6.2 OOO340m1 Build: 602 - v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b - v3.6.7.2 Build ID: e183d5b - v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 ... and updating the table of contents does not include a hyperlink for the "here" entry in any of the listed versions.
As per comment #1, confirmed. Status set to NEW. Version set to Inherited From OOo. Platform set to All (from Windows). Minor edit to Summary for clarity.
Reproducible with LO 4.4.1.2, Win 8.1
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Bug still present in Version: 5.0.5.2 Build ID: 1:5.0.5~rc2-0ubuntu2 - tested with Ubuntu Linux x86_64. Same behaviour as already described.
*** Bug 90495 has been marked as a duplicate of this bug. ***
Still present in Libo 5.2.3.3 on Windows 10 64 bit. Same behaviour as described.
Bug still present in LO 5.2.5.1. Tested with opensuse 42.1. Would be really nice to get it solved.
*** This bug has been marked as a duplicate of bug 65463 ***