Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Student projects/Admin page cleanup.

Student projects/Admin page cleanup: Difference between revisions

From MoodleDocs
mNo edit summary
 
(105 intermediate revisions by the same user not shown)
Line 1: Line 1:
Right now, I'm trying to work on a more "logical" reorganization of the settings accessible via the admin page. Slowly getting there... Please use the talk page to leave me any comments, I'll be checking it regularly.
{| style="color:black; border: 2px solid red; width: 100%; height: 20px;"
| <center>'''Source code now available on CVS (web access [http://moodle.cvs.sourceforge.net/moodle/moodle/ here])'''
Please note the statuses on this page are out of date. For the latest issues and bugs, check the [http://tracker.moodle.org/ Moodle bugtracker]</center>
|}


== Current Admin Layout (from 1.5) ==


Admin
== Key Project Tasks ==
*Configuration
**Variables
***Interface
****lang (select)
****langmenu (select)
****langlist (text)
****langcache (select)
****locale (text)
****timezone (select)
****country (select)
****framename (text)
****themelist (text)
****allowuserthemes (select)
****allowcoursethemes (select)
****allowuserblockhiding (select)
****showblocksonmodpages (select)
****tabselectedtofront (select)
***Security
****displayloginfailures
****notifyloginfailures
****notifyloginthreshold
****secureforms
****loginhttps
****runclamonupload
****pathtoclam
****quarantinedir
****clamfailureonupload
***Operating System
****gdversion
****dbsessions
****sessiontimeout
****sessioncookie
****zip
****unzip
****pathtodu
****slasharguments
****proxyhost
****proxyport
***Maintenance
****longtimenosee
****deleteunconfirmed
****loglifetime
***Mail
****smtphosts
****smtpuser
****smtppass
****noreplyaddress
****digestmailtime
****allowemailaddresses
****denyemailaddresses
***User
****sitepolicy
****fullnamedisplay
****extendedusernamechars
****autologinguests
***Permissions
****teacherassignteachers
****allowunenroll
****allusersaresitestudents
****showsiteparticipantlist
****forcelogin
****forceloginforprofiles
****opentogoogle
****maxbytes
****messaging
****allowobjectembed
***Miscellaneous
****maxeditingtime
****debug
****perfdebug
****enablerssfeeds
**Site Settings
***Full site name
***Short name for site
***Front page description
***Front page format
***Include a topic section
***News items to show
***Your word for teacher
***Your word for teachers
***Your word for student
***Your word for students
**Themes
***Select a theme
**Language
***Update language pack from moodle.org
***Check for missing strings
***Edit strings (per file)
***Edit help documents
**Modules
***Hide/show (per module)
***Delete (per module)
***Specific settings (per module)
**Blocks
***Hide/show (per block)
***Multiple (per block)
***Delete (per block)
***Settings (per block)
**Filters
***Active/Inactive filters (and order)
***Text cache lifetime
***Filter uploaded files
***Filter all strings
**Backup
***Include modules
***Metacourse
***Users
***Logs
***User files
***Course files
***Messages
***Keep x files
***Schedule SMTWTFS
***Time to execute
***Save to
**Editor Settings
***htmleditor
***editorbackgroundcolor
***editorfontfamily
***editorfontsize
***editorkillword
***aspellpath
***editorspelling
***fonts in editor's dropdown menu
***editorhidebuttons (hidden buttons)
**Calendar
***adminsseeall
***startwday
***weekenddays
***upcoming_lookahead
***upcoming_maxevents
***timezones
***timezone update/import
**Maintenance Mode
***enable/disable
***message
*Users
**Authentication
***(still looking into the different authentication methods)
**Edit User Accounts
***browse/edit/delete/add/search/alphasort users
**Add a New User
***(links to 'edit profile' for a new user)
**Upload Users
***import file
**Enrolments
***(still looking into different methods of enrolment)
**Enrol Students
***links to different courses (chosen via plain list) in admin mode
**Assign Teachers
***links through course cateogries to choose a course
**Assign Creators
***list to select from existing users
**Assign Admins
***list to select from existing users
*Courses
**shows course categories
**add/view/move/rename/delete catgories
**add a new course
**delete a course/other tasks (double-check what exactly they are)
*Logs
**live logs
**filter by date/site/participant/activity
*Site Files
**upload a file
**rename/delete/move to folder/delete files
**make a folder
*Environment
**evaluates current server environment for future moodle versions


== Proposed Structure ==
* <strike>'''(done)''' [[Student projects/Admin page cleanup/XML file format|Design XML DTD]]</strike> '''(done)''' [http://betaserv.vkm.ca:82/moodlemindmaps/moodle_admin_classes.png Design OO format for admin]
* '''(almost done -- 2 issues remaining)''' [[Student projects/Admin page cleanup/Admin block|Design new admin block]]
* '''(done)''' [[Student projects/Admin page cleanup/Reorg|Reorganize and port Moodle admin settings to OO structure]]
* '''(done, except for possible bugs)''' [[Student projects/Admin page cleanup/Admin subpages|Code script for displaying and accepting input from new admin interface]]
* '''(done)''' [[Student projects/Admin page cleanup/Bookmarks|Build a per-user bookmarking system for admin settings]]
* '''(done)''' [[Student projects/Admin page cleanup/Upgrade|Code the necessary PHP to highlight changed settings after an upgrade]] (see admin/upgradesettings.php)


Coming soon...
== Remaining Issues ==


== Random Ideas ==
* <strike>Find a good way to mark settings that are set on initial install</strike>
 
* <strike>Find a good way to display settings that are added (or set to default values) during an upgrade</strike>
* I mentioned (in my proposal) using XML to store the hierarchy. I still think this is ideal (after all, XML seems to lend itself to hierarchical data), but I think there are a few ways to expand this. Notably, along with the settings, we can store
* <strike>Figure out how user_is_editing() should work in admin/pagelib.php</strike>
# whether a setting should appear on the initial (installation) config page (granted, this'll require a rewrite or modification of the initial config page)
* <strike>Specify the $paramtype for all admin_setting_configtext objects and children</strike>
# if a new setting has been set to the default because of an upgrade, then we can have a config page that appears when upgrading which shows only the flagged, new variables (i.e. those that were set to defaults)
* Specify the $role for all admin_externalpage and admin_settingpage objects
* Site settings and editor settings could be grouped together (but I won't jumble up settings between the two of them; they'll just have the same parent in the hierarchy).
* Specify explicit $precedence values for all admin_externalpage, admin_settingpage, and admin_category objects
* Logs and Site Files sections look good as-is... probably won't make very many changes there
* Fix non-language-specific strings, and add required langfile strings
* Will try to improve on course administration interface (ideas to come soon)
* <strike>Work out a way to handle gd_version</strike>
* (Sort of) redo the user management interface so that we can get rid of the "Assign Teachers", "Assign Admins", etc. options on the main admin page (i.e. have a single link to a "User Management Interface" and do everything else from there.
* Consider adding icons and/or custom names for admin bookmarks
 
* Fix icons in admin_2 block to be theme-dependent
== Random Questions ==
* Find out if admin_2 block can be set up as an HTML list (and still work with Javascript)
 
* Fix admin/pagelib.php to include admin_2 and admin_bookmarks as default blocks
* There are no settings for specific filters? They're only active or inactive?
* For the course management section, allow view-only-mode? (i.e. the mode in which you don't edit categories)
* When it comes to the hierarchical menu, I mentioned JavaScript-based... custom-written or is there already some sort of open source framework for collapsible JavaScript hierarchies?
* Work out which files can be safely removed from the admin dir
* See if we can eliminate the old admin block (bear in mind it's still used on course pages)


== Links ==
== Links ==
Line 197: Line 36:
* Get back to the [[Student_projects | Student Projects]] listing.
* Get back to the [[Student_projects | Student Projects]] listing.
* You can get my official SoC app [http://vkm.ca/?s=soc2006-moodle-app here].
* You can get my official SoC app [http://vkm.ca/?s=soc2006-moodle-app here].
* My sample moodle setup (for fooling around & such) is [http://demoserv.vkm.ca:822/moodle here].
* My sample moodle setups are <strike>[http://demoserv.vkm.ca:822/moodle here for 1.5]</strike>, <strike>[http://betaserv.vkm.ca:82/moodle here for 1.6]</strike> and [http://betaserv.vkm.ca:82/moodle17/moodle here for 1.7 beta].


[[Category:Developer]]
[[Category:Developer]]
[[Category:Project]]
[[Category:Project]]

Latest revision as of 04:39, 21 September 2006

Source code now available on CVS (web access here) Please note the statuses on this page are out of date. For the latest issues and bugs, check the Moodle bugtracker


Key Project Tasks

Remaining Issues

  • Find a good way to mark settings that are set on initial install
  • Find a good way to display settings that are added (or set to default values) during an upgrade
  • Figure out how user_is_editing() should work in admin/pagelib.php
  • Specify the $paramtype for all admin_setting_configtext objects and children
  • Specify the $role for all admin_externalpage and admin_settingpage objects
  • Specify explicit $precedence values for all admin_externalpage, admin_settingpage, and admin_category objects
  • Fix non-language-specific strings, and add required langfile strings
  • Work out a way to handle gd_version
  • Consider adding icons and/or custom names for admin bookmarks
  • Fix icons in admin_2 block to be theme-dependent
  • Find out if admin_2 block can be set up as an HTML list (and still work with Javascript)
  • Fix admin/pagelib.php to include admin_2 and admin_bookmarks as default blocks
  • For the course management section, allow view-only-mode? (i.e. the mode in which you don't edit categories)
  • Work out which files can be safely removed from the admin dir
  • See if we can eliminate the old admin block (bear in mind it's still used on course pages)

Links

Retrieved from "https://docs.moodle.org/19/en/index.php?title=Student_projects/Admin_page_cleanup&oldid=16153"
Powered by MediaWiki