Created attachment 94019 [details] the document LO 4.2.0.4 on Xubuntu 12.04 64bit Two years ago I created a presentation with LO impress (I don't know which version). Now I opened this presentation with impress 4.2.0.4 and all hyperlinks are broken. They don't work in edit mode and presentation mode and they are not editable. This is a very serious problem for me, because I need this presentation next thursday. And even more tragical on the same day I have a training with new teachers and I want them to show LO impress and how to create good presentaions with hyperlinks within. So what should I do? I tested the same document on LO 4.1.1.2. In presentation mode the hyperlinks work, but they are not editable.
So I found a reason for this bug. It's the same like in bug 30583. I created the file in a LO with german language and now opened it in LO with US-english language. So I changed the language to german and the hyperlinks work again. But still the problem with editing an existing hyperlink, i.e. to change the target slide. How can I do this? If I mark the hyperlink, which is enough complicated, and go rightclicking on open hyperlink the slide jumps to the target slide, but no way to edit.
In the same document are graphic objects with an interaction "go to page or object". Here editing works fine. I can with a rightclick edit the interaction options and change the target slide. So why doesn't this work with hyperlinks on text?
I think it's a duplicate of bug 75968 because when editing the hyperlink with the dialog, it shows the same !!br0ken!! instead of the target, but I'm not sure, so I've added Maxim in copy. Sophie
It's a duplicate of Bug 30583, as indicated by the reporter. (In reply to comment #1) > If I mark the hyperlink, > which is enough complicated, and go rightclicking on open hyperlink the > slide jumps to the target slide, but no way to edit. There is a menu item for it: Edit->Hyperlink..., but it's currently broken - see Bug 75968. You can use 4.1 instead, or wait for 4.2.3 which will include a fix. *** This bug has been marked as a duplicate of bug 30583 ***