Bug 33655 - allow admins to hide "enable experimental features" option
Summary: allow admins to hide "enable experimental features" option
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: difficultyInteresting, easyHack, skillCpp
: 31928 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-28 07:48 UTC by Michael Meeks
Modified: 2016-02-18 16:37 UTC (History)
9 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Meeks 2011-01-28 07:48:13 UTC
As summary says; a request from our Brazilian admin friends is that we should be able to hide this check-box.
Comment 1 Rainer Bielefeld Retired 2011-01-28 08:56:02 UTC
And who is WE? Admins?
And how should that work? Can we get a concrete suggestion like  "In user installation add an option 'Hide ...'" or similar? 

I disagree with that idea, and without a comprehensible motivation this is definitively not a "major" issue.
Comment 2 Olivier Hallot 2011-01-28 14:17:57 UTC
We admins are those who are responsible for very large deployments in corporations, where any glitch has a cost of several calls for the help desk.

Experimental features are good for home hackers, developers or home users, but may turn into a nightmare for IT managers, if their users start questioning what are those "unstable" features. 

<sarcasm> As one may already know, end-users are *never* wrong, "everything was fine yesterday", "I did nothing and it broke by itself", "I always did that way and now it doesn't work anymore". etc... </sarcasm> 

So if admins can hide unstable features to the end-user, they will avoid users breaking their installation or calling the help desk. 

Note that I am not asking to remove the unstable option, just configure the option of its visibility. The default for example should be "on" (displayed).
Comment 3 Björn Michaelsen 2011-12-23 11:47:30 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 4 Florian Reisinger 2012-08-14 14:00:31 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:01:38 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 14:06:21 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:08:23 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 8 sasha.libreoffice 2012-08-23 08:00:53 UTC
But what decision? Explanations from Comment 2 makes sense. But what to do?
Comment 9 Michael Meeks 2012-08-23 08:23:43 UTC
I guess we should re-open this. I guess Olivier wants a new setting to hide the "enable experimental options" option in the settings dialog.

That shouldn't be so hard to create. That options dialog is here:

cui/source/options/optgdlg.cxx

We should interrogate the config item using:


unotools/source/config/configitem.cxx:
Sequence< sal_Bool > ConfigItem::GetReadOnlyStates(const com::sun::star::uno::Sequence< rtl::OUString >& rNames)

cf. it's use in svl/source/config/cjkoptions.cxx

to populate the IsReadOnly flags.

And we should add an IsExperimentalReadOnly helper to svtools/inc/svtools/miscopt.hxx

Then we should hide the UI check-box in optgdlg.cxx if it is set read-only in the config.

Olivier - any chance of a patch with that ? otherwise making an EasyHack.
Comment 10 Björn Michaelsen 2013-10-04 18:47:51 UTC
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.

see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Comment 11 Robinson Tryon (qubit) 2013-10-23 18:41:14 UTC
Removing comma from whiteboard (please use a space to delimit values in this field)
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard#Getting_Started
Comment 12 Andras Timar 2013-10-23 18:58:08 UTC
It is possible to hide the entire Advanced page, or it is possible to disable the checkbox on it by editing configuration files. If it is enough, I can give the details. From LibreOffice 4.2 it is even possible via Group Policy under Windows.
Comment 13 bfoman (inactive) 2013-10-24 19:33:26 UTC
(In reply to comment #12)
> I can give the details. From LibreOffice 4.2 it is even possible via Group
> Policy under Windows.

Please do so - is there a wiki article about this topic?
Comment 14 Michael Meeks 2013-10-24 20:29:04 UTC
Andras - if so, sounds awesome & we should just close this then I guess. Do we have a GPO template for that ? :-)
Comment 15 bfoman (inactive) 2014-01-15 16:45:47 UTC
(In reply to comment #12)
> It is possible to hide the entire Advanced page, or it is possible to
> disable the checkbox on it by editing configuration files. If it is enough,
> I can give the details. From LibreOffice 4.2 it is even possible via Group
> Policy under Windows.

Please add the details in this bug. Thanks. Therefore adding you to CC list.
Comment 16 bfoman (inactive) 2014-01-15 16:46:26 UTC
*** Bug 31928 has been marked as a duplicate of this bug. ***
Comment 17 Robinson Tryon (qubit) 2015-12-14 05:03:40 UTC
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyInteresting SkillCpp)
[NinjaEdit]
Comment 18 Andras Timar 2016-02-09 16:42:39 UTC
See:
https://libreoffice-from-collabora.com/windows-group-policy-admx/
You can disable this, and many other settings with this ADMX template.
Comment 19 Robinson Tryon (qubit) 2016-02-18 16:37:28 UTC
Remove LibreOffice Dev List from CC on EasyHacks
(curtailing excessive email to list)
[NinjaEdit]