Resource settings

2006-07-13T06:57:32Z

Diggers2004:

If your theme has a large header then the ''resource_framesize'' variable should be increased to prevent horizontal and vertical scrollbars.

The "Display a Directory" option gives the error "Cannot create another instance of this resource" if MySQL5 is being used to with the moodle database due to an issue with reserved words. MySQL 4.i.18 supports all features of tghe resource module.

[[Category:Administrator]]
[[Category:Resource]]

Talk:Activity modules administration

2006-07-06T12:57:57Z

Diggers2004:

Why were the instructions re. module installation removed ??? Were theuy wrong? If so, could someone correct them. Were they moved ? If so where to ? Stephen Digby

Activity modules administration

2006-07-06T12:53:41Z

Diggers2004: /* Module configuration */

Location: Administration >> [[Configuration]] >> Modules

==Module configuration==
To install additional modules into moodle:
* dowload the module (usually as a compressed "zip" file)
* extract and.......

*[[Assignment configuration|Assignment]]
*[[Chat configuration|Chat]]
*[[Database configuration|Database]] (1.6)
*[[Forum configuration|Forum]]
*[[Glossary configuration|Glossary]]
*[[Hotpot configuration|Hotpot]] (1.6)
*[[LAMS configuration|LAMS]] (1.6)
*[[Quiz configuration|Quiz]]
*[[Resource configuration|Resource]]
*[[SCORM/AICC configuration|SCORM/AICC]]

[[Category:Administrator]]
[[category:Modules]]

2.3:Talk:Update profile

2006-05-05T06:08:26Z

Diggers2004:

===Edit User data===
The Edit user data form allows each user many options in terms of identifying themselves to others and receiving information from the moodle server.

=== Edit User Data Fields in SQL database===
Some moodle managers may like to acces the SQL database directly to set options for all users at once e.g. change authentication.
Some may set some options for all users and then disable the code in moodle that allows them to be changed back e.g. Set all email addressses to "Hide my email address from everyone" and then disable the drop down box that allows this setting to be changed. This may be necessary in many schools where it is unsuitable to allow users to see "home" email addresses for other users or teachers.

* '''id''' e.g. (1420) - unique moodle reference to all content added by this user e.g. even wiki page contributions. If user data is excluded from backups, all wiki content will also be excluded.)
* ''' 'auth''' e.g. (manual) - Most common alternatives are: '''LDAP''' (checking with another network LDAP server. Avoids having to update data on two seperate servers; '''Email''' - allows users to create new user accounts as long as they have an email address i.e. user accounts are completely open. Access to courses can still be controlled through '''''enrolment keys''''' - Variety of additional authentication options
* ''' confirmed''' e.g. (1)
* ''' policyagreed''' e.g. (0)
* ''' deleted''' e.g. (0)
* ''' username''' e.g. (van0012)
* ''' password''' e.g. (a81608423f3d5e1b69bda1c0e4195d95) - encrypted version of real password
* ''' idnumber''' e.g. ()
* ''' firstname''' e.g. (Billy)
* ''' lastname''' e.g. (BEEK)
* ''' email''' e.g. (z@b.com)
* ''' emailstop''' e.g. (0) 0=This email is enabled; 1=This email is disabled
* ''' icq''' e.g. ()
* ''' skype''' e.g. ()
* ''' yahoo''' e.g. ()
* ''' aim''' e.g. ()
* ''' msn''' e.g. ()
* ''' phone1''' e.g. ()
* ''' phone2''' e.g. ()
* ''' institution''' e.g. ()
* ''' department''' e.g. ()
* ''' address''' e.g. ()
* ''' city''' e.g. (Melbourne)
* ''' country''' e.g. (AU)
* ''' lang''' e.g. (en)
* ''' theme''' e.g. ()
* ''' timezone''' e.g. (99)
* ''' firstaccess''' e.g. (0)
* ''' lastaccess''' e.g. ()
* ''' lastlogin''' e.g. ()
* ''' currentlogin''' e.g. ()
* ''' lastIP''' e.g. (210.15.218.148)
* ''' secret''' e.g. ()????
* ''' picture''' e.g. (1)
* ''' url''' e.g. ()
* ''' description''' e.g. (Student)
* ''' mailformat''' e.g. (1)1=
* ''' maildigest''' e.g. (0)0=No digest. Single email per forum post; 1=Complete. Daily email with full posts; 2=Subjects. Daily email with subjects only
* ''' maildisplay''' e.g. (2) 0=Hide my email address from everyone; 1=Allow everyone to see my email address; 2=Allow only other course members to see my email address
* ''' htmleditor''' e.g. (1)0=Use standard web forms (e.g. plain text) 1=Use HTML editor (some browsers only)
* ''' autosubscribe''' e.g. (1)0= Yes when I post, subscribe me to that forum; 1=No, don't automatically subscribe me to forums
* ''' trackforums''' e.g. (0)
* ''' timemodified''' e.g. (#######)

2006-04-22T22:56:45Z

Diggers2004:

Need a definition of non-standard blocks !!

Do they means that they won't run on standard moodle installs ?
Do they means that they will cause incompatability problems on standard moodle ?
Do they mean that they won't integrate with upgrades ?

I don't touch them because of the above presumptions. [[User:Stephen Digby|Stephen Digby]] 06:56, 23 April 2006 (WST)

2006-02-18T21:59:26Z

Diggers2004:

==Moodle wiki purpose==

To provide a way for students, teachers and other Moodle participants to create an organic, on-line document collaboratively.

==Key features==

# Pages can be created and linked using simple wiki methods.
# All Moodle text formats can be supported.
# Editing and viewing can be restricted by Moodle roles (i.e. currently, Students, Groups, Teachers).
# Images can be easily inserted into the text of a wiki.
# Attachments can be made to wiki pages.
# Must be fully compliant with Moodle backup and restore.
# Must be fully compliant with Moodle logging and activity tracking.
# Must provide a method of grading (see assignment module). Grading should be optional on a per-wiki basis.
# Allow inporting of external documents to create a wiki or add to an exiting one.
# Allow exporting to an external document.
# Allow refactoring/moving/deleting pages with appropriate permissions
(from Martin's list):

==Basic Operation==
'''Create the wiki:'''- Log in/ Turn editing on/ Add and activity/ Wiki
- Fill in wiki parameters (Leave defaults and experiment later. Evcerything except the inital page fields can be changed.)
'''Adding pages:'''
- Edit the first (& only page)/ Type the name of the new page you want within square brackets/ Click Save. The new page link is displayed beside a question mark./ Click the question mark to open the new page for data entry.
- pages can be added from any page.
(Suggestion: On your start page, type "PageIndex" and perhaps "Site Map" and/or "Newest Pages" so that the user is alerted to these options immediately on entering the wiki. They also appear on the "Choose wiki links" drop down at the top of the wiki window.
The wiki is one of the most powerful tools within moodle suitable for many administartive and teaching functions such as:
# the bast way to deliver you school administrative manuals i.e. teachers manual; student manual
# the best way to encourage students to build and debate a shared summary of your whole course content as you work etc etc

Currently some wiki features such as export & strip pages do not work reliably.
Also the moodle editor, does not handle hyperlinks correctly within a wiki. i.e. All links must be manually placed within square brackets rather than embedded as HTML links.
==Design Objectives==
* The Wiki should support exactly the same text formats in Moodle core as you find everywhere else (see weblib.php for standard functions, eg format_text). ie Moodle format, HTML format, Markdown, etc. Any new formats need to go in the core so they are available everywhere, and this needs to be discussed very well. We only JUST removed the old Wiki-like format to reduce confusion with the current Wiki and I don't want more of this confusion from a rushed implementation.

* Linking should support both CamelCase and [Bracket] styles, and also automatic linking on the fly (a la Glossary).

* Upgrading from the old system to any new one should be seamless and problem-free (this includes restoring old backups from 1.4, for example).

* The idea with eWiki was to build on the work of the eWiki team in future. Unfortunately, so many hacks needed to be made to their monolithic script that this became almost impossible. I would like to see a lot of thought put into a very cleanly-designed architecture for the Wiki in future, something that is easy to extend and maintain (and also to use).

* I really like MediaWiki, as this Wiki is becoming a defacto standard (for good reason) and it would be good to be compatible in some way with it. Perhaps we can use part of it as a library for us. However, the Moodle Wiki is a COMPONENT within the larger Moodle system and has a very different focus to MediaWiki (which is designed for large standalone web sites) ... much thought should be given to making our Wiki work very closely with other modules, rather than another module that tries to do everything itself. It should do exactly what it needs to do and no more.

* Support for media in a very clean way is a must. This is probably my biggest criticism of the current eWiki version ... attaching images and video etc is really awkward and doesn't look good.

==See also==

*[http://moodle.org/mod/forum/discuss.php?d=21493 Wiki development] forum discussion
*[[Dfwiki]]
[[Category:Developer]]