phpgroupware-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-tracker] [bug #5328] preferences usability issues


From: nobody
Subject: [Phpgroupware-tracker] [bug #5328] preferences usability issues
Date: Tue, 16 Sep 2003 20:56:53 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624

=================== BUG #5328: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5328&group_id=509

Changes by: Michael Totschnig <address@hidden>
Date: mer 17.09.2003 à 00:56 (GMT)

------------------ Additional Follow-up Comments ----------------------------
Maybe it might be even better to get rid of function verify_basic_settings, and 
implement the same feature in a safer way in function read_repository.



=================== BUG #5328: FULL BUG SNAPSHOT ===================


Soumis par: totschnig                 Projet: phpGroupWare                  
Signalé le: mar 16.09.2003 à 02:32
Category:  API - Preferences          Bug Group:  0.9.16RC1                 
Severity:  2                          Priority:  None                       
Resolution:  None                     Assigned to:  skwashd                 
Status:  Open                         Component Version:  None              
Platform Version:  None               Reproducibility:  None                

Summary:  preferences usability issues

Original Submission:  1) When an administrator sets default values in 
preferences, it is probably because he thinks these values will automatically 
be valid for new users. But this is not the case, since phpgroupware sets its 
own default values (in function verify_basic_settings) for new users that have 
not set there preferences which overide the default values the administrator 
provided.

2) In Preferences -> Change your settings -> Interface/Template selection the 
coexistence between the option "Use default" (the administrator set value) and 
"default" (the template set which is so called) is confusing . It would be 
better to rename the "default" template set.

Follow-up Comments
*******************

-------------------------------------------------------
Date: mer 17.09.2003 à 00:56        By: totschnig
Maybe it might be even better to get rid of function verify_basic_settings, and 
implement the same feature in a safer way in function read_repository.

-------------------------------------------------------
Date: mar 16.09.2003 à 14:13        By: totschnig
1) I am not sure what effect array_merge will have. I think, if there is a 
default value set by the administrator for some setting, phpgroupware must not 
set a value for this setting in the user's preferences.



2) this sounds reasonable

-------------------------------------------------------
Date: mar 16.09.2003 à 05:45        By: skwashd
1 There are 2 possibilities for solving this one:

 * array_merge() the 2 sets of values - quickest to implement

 * any sysadmin could be unset() in the app defaults array 

Any "preference"? :)



2 I agree about the template set name.  Maybe a name like "basic" or "simple" 
would be more accurate.  At the same time I think we should keep the current 
*/template/default dirs, just not display them in the available set.  This 
involves little work a couple of minor changes and then the "default" dir a 
real fallback default directory, which will still function as it does now.  I 
will propose this on the dev list for further discussion.  I don't think this 
can be changed in 16, but should be done in HEAD and available in the next 
major release, because of the impact of it.



Cheers


La liste CC est vide


Il n'y a aucun fichier attaché actuellement


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5328&group_id=509

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]