Both Writer and Calc have the possibility to configure their behaviour when loading the document that contains links to external sources. It is in Tools > Options > Calc | Writer > General > Update links when loading, the choice is between "Always", "On request" and "Never"
Impress, however, has no such option and it seems to always uses "on request" mode. There is no way to disable that. As we have seen on HH Hackfest, some users create presentations containing external links too (images, tables etc.) and it is then PITA for them, being always forced to confirm that they really want to update the content from external source(s) ...
So the suggestion is either to i) implement this choice in Tools > Options for Impress too, or better yet ii) make it global for all app
all apps, even :)
@Sebastian: I thought you might be interested in this ticket
Thanks - I would prefer an option per module.
I expect people to have diverging preferences per doc-type..
1+ for Cor Nouws: per module
1+ for this kind of implementation
-1 for the Radio buttons to setup each file if its updated manually or automatically.
Reason: (1) It's redundant with the question box at the startup.
(2) What it if one file is automatically and the other is manually?
-> My conclusion: The radio buttons and in the list-box-element that there stands Manual is PSEUDO what they are doing at the moment. Therefore there is reported another bug: https://bugs.documentfoundation.org/show_bug.cgi?id=95302
Solutions for this redundant conflict:
Variant 1: Only the solution to implement the conclusion of 95380 is the solution
Variant 2: 95380 concludes the general settings, and 95302 individual for the document. So settings of 95380 are ignored if for example a Radio button is switched from Global settings to either Manual or Automatically. But is this good for security? Or should then there be an additional option in 95380, that says allow file to make a own decision?
We're replacing our use of the 'ux-advise' component with a keyword:
Component -> LibreOffice
Add Keyword: needsUXEval
Removing needsUX, the request makes sense and received some +1.
We should allow to set this feature per module - option i). And in respect to comment 3 / bug 95302 allow to override this setting per document, which is a nice-to-have to me. Some code pointers are in 95032.
Please add keyword 'needsUXEval' and CC 'firstname.lastname@example.org' if input from UX is needed.