Issue 98988 - safe mode — for a more reliable Extension Manager
Summary: safe mode — for a more reliable Extension Manager
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: DEV300m41
Hardware: All All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-02-07 08:18 UTC by Graham Perrin
Modified: 2013-08-07 15:31 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Graham Perrin 2009-02-07 08:18:13 UTC
Please see discussion at in 

> … This example points perfectly out that we need a feature 
> like a safe mode for extension … 
Comment 1 Graham Perrin 2009-02-07 08:24:39 UTC
To clarify: an Extension Manager that can not manage extensions (for any reason) is not a manager. 

A safe mode should allow to run without extensions, so that Extension Manager can be 
more reliably used for management. 


On Mac OS X: safe modes (of operating system, of applications) are sometimes (not always) achieved by 
holding the shift key when the OS or application is started.

On other OSes: other routes to safe modes may be preferred. 
Comment 2 Olaf Felka 2009-02-09 10:19:21 UTC
Sounds good but seems to be a complex problem to solve. Maybe we should rename
the extension manager. It might also a solution to disable the extension that
causes trouble. But checking the health of extensions costs perfomance.
Comment 3 frank.loehmann 2009-02-09 10:58:17 UTC
Set target.
Comment 4 Graham Perrin 2009-02-09 13:32:02 UTC
> a complex problem

My primary motive (motives of others may vary) is to be able to disable and/or uninstall any extension. 

In the example given I found myself unable to use the Manager for a particular extension.

> checking the health of extensions costs perfomance.

Taking responsibility for the consequences of installing any exension, assuming imperfection of an 
extension, my main wish would be to disable or uninstall.

I would treat health checking by OOo as a separate enhancement. Checks would be nice to have, but 
less important than the ability to uninstall.

> It might also a solution to disable the extension that causes
> trouble. 

Might that be less or more complex than a safe mode that (temporarily) disables all extensions, to 
allow uninstallation of any one extension?

Thanks for comments/consideration. 
Comment 5 Mathias_Bauer 2009-04-15 18:00:14 UTC
Setting target to 3.2, but keeping the "requirements" owner is a bad idea. If we
want to have that in 3.2, we should form an iTeam for this feature.

As I understood the original requirement, the user should be able to start OOo
without his extensions. That should be easy. But I assume that a user also will
be able to deinstall an extension so that she can restart OOo without "safe
mode". And this might become more complicated. Anyway, I think we need input
from all sides here, including development. And that means: we need an iTeam and
an issue owner driving the feature.