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
Line 188: Line 188:
# 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)
# 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)
* 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).
* 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).
* Logs and Site Files sections look good as-is... probably won't make very many changes there
* Will try to improve on course administration interface (ideas to come soon)


== Random Questions ==
== Random Questions ==

Revision as of 02:46, 1 June 2006

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.

Current Admin Layout (from 1.5)

Admin

  • 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

Coming soon...

Official SoC Application

You can get my official SoC app here.

Random Ideas

  • 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
  1. whether a setting should appear on the initial (installation) config page (granted, this'll require a rewrite or modification of the initial config page)
  2. 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)
  • 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).
  • Logs and Site Files sections look good as-is... probably won't make very many changes there
  • Will try to improve on course administration interface (ideas to come soon)

Random Questions

  • There are no settings for specific filters? They're only active or inactive?