Bug 43784 - Show infobar when document has broken linked files
Summary: Show infobar when document has broken linked files
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: Infobar Files-Linked
  Show dependency treegraph
 
Reported: 2011-12-13 03:13 UTC by Harald Koester
Modified: 2017-09-23 06:07 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2011-12-13 03:13:22 UTC
Steps in order to reproduce the bug:
[1] Create a new text document (Document A) and insert some text.
[2] Save and close Document A.
[3] Create a second new document (B).
[4] Set option "LibreOffice Writer, General, Update link when loading" to "On request".
[5] Insert a section as a link to Document A. The content of Document A is displayed inside this section of Document B.
[6] Save and close Document B.
[7] Rename Document A with file manager.
[8] Open Document B. 
[9] You are informed, that the document contains links to external data and you are asked if you like to update the links. Click Yes.
[10] The borders of the section inside Document B are displayed, but its content is empty.

If you choose at step [4] "Always" the behavior is equal except step [9] is not performed.

Expected behavior:
Before step [10] I expected an error message, in order to inform the user that the linked file does not exist.

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.24) Gecko/20111103 Firefox/3.6.24
Comment 1 Florian Reisinger 2012-01-21 09:31:43 UTC
Hi!

You are right, there is no error message...
Comment 2 Thomas Hackert 2012-01-21 09:41:24 UTC
Hello Harald, *,
I can confirm it with Debian Testing AMD64 and LO 3.5.0 RC1 ... :(
HTH
Thomas.
Comment 3 Harald Koester 2012-11-27 10:56:56 UTC
Bug still exists in Version 3.6.3.

To my opinion it's not only an enhancement. Particularly if you are asked explicitly to update the link, I expect, that LO informs you, that an update is not possible. 

Otherwise there is the _danger_of_data_loss_. Suppose a case where Document A has been deleted errorneously. Without an error message, also the former inserted text of Document A will be deleted in Document B. Furthermore, especially with a larger document, you may recognize the missing of Document A much more later. So hopefully you have a good backup, so that you are able to reconstruct your documents or you are able to fetch back Document A from the recycle bin.
Comment 4 Harald Koester 2017-09-22 09:01:29 UTC
Bug still exists in version 5.4.1. (Win7)
Bug already exists in version 3.3.0. Hence inherited from OOo.
Comment 5 Yousuf Philips (jay) (retired) 2017-09-22 20:01:37 UTC
In my view, the error should appear as an infobar message, which the user can click the button to open the Edit > Links dialog, as showing a msgbox dialog for such an error would cause alot of problems when there were multiple broken linked files.

UX-Team: what do you guys think?
Comment 6 Heiko Tietze 2017-09-23 04:18:27 UTC
(In reply to Yousuf Philips (jay) from comment #5)
> In my view, the error should appear as an infobar message, which the user
> can click the button to open the Edit > Links dialog, as showing a msgbox
> dialog for such an error would cause alot of problems when there were
> multiple broken linked files.
> 
> UX-Team: what do you guys think?

Fully agree with the infobar. Question is only whether it's a warning (yellow) or error (red). Would say the latter.
Comment 7 V Stuart Foote 2017-09-23 04:24:38 UTC
+1, Infobar--Red--warning of broken links with button action to open the Edit -> Links dialog. Just generic in the warning, the dialog will show them all.

A separate message box for each of multiple links would be annoying--single Infobar warning on launch is enough.