https://docs.moodle.org/35/en/api.php?action=feedcontributions&user=Dilettante&feedformat=atomMoodleDocs - User contributions [en]2024-03-28T08:56:57ZUser contributionsMediaWiki 1.39.6https://docs.moodle.org/35/en/index.php?title=User:Mike_Strong&diff=13529User:Mike Strong2006-07-30T00:18:31Z<p>Dilettante: </p>
<hr />
<div>Hi!</div>Dilettantehttps://docs.moodle.org/35/en/index.php?title=Moodle_version_history&diff=13528Moodle version history2006-07-30T00:16:33Z<p>Dilettante: added 1.6.1 reference</p>
<hr />
<div>==Release History==<br />
<br />
See [[Release_Notes|Release Notes]] for more details.<br />
<br />
==Moodle 1.0==<br />
*Moodle 1.0 - 20 August 2002<br />
*Moodle 1.0.1 - 26 August 2002<br />
*Moodle 1.0.2 - 2 September 2002<br />
*Moodle 1.0.3 - 5 September 2002<br />
*Moodle 1.0.4 - 10 September 2002<br />
*Moodle 1.0.5 - 27 September 2002<br />
*Moodle 1.0.6 - 26 October 2002<br />
:: 1.0.6.1 - 6 Nov<br />
:: 1.0.6.2 - 11 Nov<br />
:: 1.0.6.3 - 14 Nov<br />
:: 1.0.6.4 - 25 Nov<br />
*Moodle 1.0.7 - 9 December 2002<br />
*Moodle 1.0.8 - 7 January 2003<br />
*Moodle 1.0.9 - 30 May 2003<br />
<br />
==Moodle 1.1==<br />
*Moodle 1.1 - 29 August 2003<br />
*Moodle 1.1.1 - 11 September 2003<br />
<br />
==Moodle 1.2==<br />
*Moodle 1.2 - 20 March 2004<br />
*Moodle 1.2.1 - 25 March 2004<br />
<br />
==Moodle 1.3==<br />
*Moodle 1.3 - 25 May 2004<br />
*Moodle 1.3.1 - 4 June 2004<br />
*Moodle 1.3.2 - 9 July 2004<br />
*Moodle 1.3.3 - 16 July 2004<br />
*Moodle 1.3.4 - 11 August 2004<br />
<br />
==Moodle 1.4==<br />
*Moodle 1.4 - 31 August 2004<br />
*Moodle 1.4.1 - 12 September 2004<br />
*Moodle 1.4.2 - 5 November 2004<br />
*Moodle 1.4.3 - 21 December 2004<br />
*Moodle 1.4.4 - 7 March 2005 <br />
*Moodle 1.4.5 - 7 May 2005<br />
<br />
==Moodle 1.5==<br />
*Moodle 1.5 - 5 June 2005<br />
*Moodle 1.5.1 - 8 July 2005<br />
*Moodle 1.5.2 - 16 July 2005<br />
*Moodle 1.5.3 - 11 November 2005<br />
*Moodle 1.5.4 - 21 May 2006<br />
<br />
==Moodle 1.6==<br />
*Moodle 1.6 - 20 June 2006<br />
*Moodle 1.6.1 - 20 July 2006<br />
<br />
==Moodle 1.7==<br />
*Moodle 1.7 (September 2006?)<br />
<br />
==Moodle 2.0==<br />
*Moodle 2.0 (Early 2007?)<br />
<br />
[[Category:Administrator]]<br />
[[Category:Developer]]</div>Dilettantehttps://docs.moodle.org/35/en/index.php?title=Blogs&diff=12128Blogs2006-06-19T14:02:18Z<p>Dilettante: changed "other" to "of"</p>
<hr />
<div>{{Template:Blogs}}<br />
{{Moodle 1.6}}<br />
<br />
Blogs allow students, teachers and administrators to have a public web log. This online journal has various settings to control who can read them.<br />
<br />
Many companies and organisations on the web provide blog sites and they are generally free. The largest company to do this is blogger which is owned by Google. There are also many Open Source web applications that can be downloaded and installed freely. The most common of these is Wordpress.<br />
<br />
Blogs in Moodle are user based - each user has their own Blog. Admins, Teachers, and users can create Tags - Admins can create site level tags, Teachers can create Course level tags, and users can create their own list of tags.<br />
<br />
When a blog entry is created, a user can select which tags they wish to associate with their new entry. - multiple tags can be selected. Users can also select who they want the blog entry to be available to - (depending on the global settings of the site.)<br />
<br />
==See also==<br />
<br />
*[[Elgg]]<br />
*[http://www.blogger.com Blogger.com]<br />
*[http://www.wordpress.org Wordpress]<br />
*[http://en.wikipedia.org/wiki/Weblog Wikipedia on Blogs]<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=44830 Blogs and comments] forum discussion<br />
*[[Blogs development]]<br />
[[Category:Teacher]]<br />
[[Category:Blog]]</div>Dilettantehttps://docs.moodle.org/35/en/index.php?title=Backup_and_restore_FAQ&diff=4866Backup and restore FAQ2006-02-06T18:35:06Z<p>Dilettante: </p>
<hr />
<div>;Site backups<br />
:Site backups, as explained in [[Upgrading_Moodle#Backup_important_data|upgrading Moodle]], are recommended in order to have all data saved with the best confidence and the shortest recovery time.<br />
<br />
;Course backups<br />
:Course backups, configured on the [[admin/backup|backup]] page, are more expensive in terms of time and CPU usage. The recovery time to have your site running again is longer. Course backups are useful for obtaining "fresh" copies of courses to be re-used or distributed individually, however they should never be used as a primary backup system (unless your hosting doesn't allow the preferred site backups). In order to make scheduled backups, you have to setup CRON to run periodically. Have a look at [[Installing Moodle#Set_up_cron|Set up cron]] for details.<br />
<br />
===How do I backup my whole Moodle site?===<br />
<br />
There are two main things you need to make a copy of - the database and the uploaded files. The Moodle scripts themselves are less important, since you can always download a fresh copy if you have to.<br />
<br />
There are many ways to do such backups. Here is an outline of a little script you can run on Unix to backup the database (it works well to have such a script run daily via a cron task):<br />
<br />
cd /my/backup/directory<br />
mv moodle-database.sql.gz moodle-database-old.sql.gz<br />
mysqldump -h example.com -u myusername --password=mypassword -C -Q -e -a mydatabasename > moodle-database.sql<br />
gzip moodle-database.sql<br />
<br />
For the files, you can use rsync regularly to copy only the changed files to another host:<br />
<br />
rsync -auvtz --delete -e ssh mysshusername@example.com:/my/server/directory /my/backup/directory/<br />
<br />
===Error: An error occurred deleting old backup data===<br />
<br />
This part of the backup (or restore) procedure tries to delete old info, used in previous executions, performing the following tasks:<br />
<br />
* Delete old records from "backup_ids" table: Check the table exists, repair it and try again.<br />
<br />
* Delete old records from "backup_files" table: Check the table exists, repair it and try again.<br />
<br />
* Delete old files from "moodledata/temp/backup": Delete the dir completely and try again.<br />
<br />
There are various ways of repairing tables, including using MySQL Admin.<br />
<br />
===XML error: not well-formed (invalid token) at line YYYY===<br />
<br />
This problem can appear at any point in the restore process. It's caused when the XML parser detects something incorrect in the backup file that prevent correct operation. Usually, it's caused by some "illegal" characters added in the original course due to some copy/paste of text containing them (control characters, or invalid sequences...).<br />
<br />
The best method to handle this issue is:<br />
<br />
* Unzip the problematic backup file under one empty folder.<br />
<br />
* Open the moodle.xml with Firefox. It will show you where (exact char) the problem is happening.<br />
<br />
* Edit the moodle.xml file with some UTF8-compatible editor and delete such characters. Save changes.<br />
<br />
* Test the moodle.xml file again with Firefox until no error was displayed.<br />
<br />
* Zip everything again (all the folder contents but the folder itself!).<br />
<br />
* Restore the course. It should work now.<br />
<br />
Also, if possible, it's highly recommended to solve those problems in the original course too from Moodle itself. Once "repaired" there, problems will be out if you create new backup files in the future.<br />
<br />
=== Some of your courses weren't saved!! ===<br />
<br />
There are two possible causes of this problem:<br />
<br />
1. Error - this happens when the backup procedure has found an error and so hasn't finished the backup of a particular course. These are "controlled" errors and the scheduled backup continues with the next course.<br />
<br />
2. Unfinished - this happens when the backup procedure dies without knowing why. When the cron is next executed it detects that the last execution went wrong, and continues skipping the problematic course. A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), or if there is some exact point were all the courses are breaking (generally internal zip libraries, try to switch to external executables instead).<br />
<br />
== See also ==<br />
<br />
*[http://moodle.org/mod/forum/view.php?f=128 Using Moodle: Backup and Restore]<br />
*[http://download.moodle.org/modules/integrations.php Moodle Download: Integrations] - MySQL Admin for download<br />
<br />
== External links ==<br />
<br />
*[http://www.databasejournal.com/features/mysql/article.php/10897_3300511_2 Repairing Database Corruption in MySQL]<br />
<br />
[[Category:Administrator]]<br />
[[Category:FAQ]]</div>Dilettante