Sakai default config is missing a huge number of config options
Description
Attachments
- 23 Jul 2013, 02:10 PM
- 18 Jul 2013, 05:36 PM
- 12 Sep 2011, 07:17 PM
- 12 Sep 2011, 06:24 PM
- 09 Sep 2011, 05:53 PM
is related to
relates to
Activity
Hudson CI Server August 1, 2013 at 1:50 PM
Integrated in kernel-trunk #691 (See http://builds.sakaiproject.org:8080/job/kernel-trunk/691/)
https://sakaiproject.atlassian.net/browse/SAK-21124#icft=SAK-21124 fixing the wysiwyg editor value to ckeditor by default (Revision 128011)
Result = SUCCESS
Matthew Jones July 29, 2013 at 10:52 AM
Looks like 127570 commenting out wysiwyg.editor reverted the editor to FCKEditor.
wysiwyg.editor=ckeditor
There's a comment about kernel.properties setting this to FCKEditor, so this should be changed in kernel.properties then?
Hudson CI Server July 26, 2013 at 4:32 PM
Integrated in portal trunk #1574 (See http://builds.sakaiproject.org:8080/job/portal%20trunk/1574/)
https://sakaiproject.atlassian.net/browse/SAK-21124#icft=SAK-21124 Fixing up default options for Sakai config (Revision 127575)
Result = SUCCESS
Hudson CI Server July 26, 2013 at 4:26 PM
Integrated in kernel-trunk #690 (See http://builds.sakaiproject.org:8080/job/kernel-trunk/690/)
https://sakaiproject.atlassian.net/browse/SAK-21124#icft=SAK-21124 fixing up property that cannot be blank (Revision 127689)
https://sakaiproject.atlassian.net/browse/SAK-21124#icft=SAK-21124 Fixing up default options for Sakai config (Revision 127574)
Result = SUCCESS
Hudson CI Server July 26, 2013 at 3:53 PM
Integrated in assignment trunk #697 (See http://builds.sakaiproject.org:8080/job/assignment%20trunk/697/)
https://sakaiproject.atlassian.net/browse/SAK-21124#icft=SAK-21124 Fixing up default options for Sakai config (Revision 127569)
Result = SUCCESS
The default config should contain all the configuration options which are available in Sakai so this is a 2 part ticket.
Part one is to identify every configuration option which is known to the configuration service on startup. Ideally figuring out where each of the values were loaded from and whether they were overridden. (probably via temporary logging)
Part two is to insert them into the default configuration file with as much documentation as is known.
Part three is to correct any configuration options which do not have an appropriate default defined in the service where they are used.