Peter Ruthven-Stuart

Jordi,

Thank you for your reply.

I followed the above steps (minus step 2) and had no luck .

I restored one course into my experimental moodle site that contained one instance of a Wiki activity. I then installed Nwiki following the above steps (without step 2). On re-logging in to my experimental moodle I got the "wiki module needs upgrading" message and then a series of 'success' messages but no [continue] button at the bottom of the page: see attached PDF.

I then reloaded the page, and got these 'messages'

(mysql): SHOW TABLES

(mysql): SELECT * FROM mdl_modules WHERE name = 'dfwiki' LIMIT 1

dfwiki installed. Upgrading dfwiki (start) 

(mysql): SHOW COLUMNS FROM `mdl_modules`

(mysql): UPDATE mdl_modules SET name = 'dfwiki', version = '2006052502', cron = '2007053101', lastcron = '0', search = '', visible = '0' WHERE id = '23'

dfwiki installed. Upgrading dfwiki (end) 

wikis to dfwiki (start)-> 

(mysql): SELECT * FROM mdl_wiki

(mysql): SELECT * FROM mdl_wiki_entries WHERE wikiid='1' LIMIT 1

(mysql): SELECT * FROM mdl_modules WHERE name = 'wiki' LIMIT 1

(mysql): SELECT * FROM mdl_course_modules WHERE module=22 AND instance=1 LIMIT 1 

Reloading the page again gets the same messages. The only way to get back to the top page is to remove the NWiki module from the mod directory.

Just to make sure that Nwiki would install correctly into my system, I removed the course that contained the instance of a Wiki activity, so that there were no wikis in my system. This time, the installation was a success, so it seems that there is a bug in the migration process .

Any ideas?

My experimental Moodle is running on the following system:

PowerBook G4, Mac 10.4.10
moodle 1.8.3 (downloaded 29th Nov from CVS)
MySQL 5.0.24
php 5.2.1

Ludo,

Thank you for your quick reply.

I already have an experimental moodle 1.8.3 system setup, so will do as you suggest. However, before going ahead I'd like to check with you the order in which I should carry out the installation of and migration to Nwiki.

Is this order correct?:

1. Restore (install) courses containing eWiki activites into my experimental moodle system.
   
2. Via the moodle admin page, delete the eWiki activity module.
3. Remove the wiki directory (i.e. eWiki) from the mod directory on the server.
4. Install the various directories in the 'wiki_1.8_rev2007061102 Folder' into the correct locations in the experimental moodle directory on the server.
5. Access the admin of the experimental moodle via a web browser: at this stage I assume the system will recognise the existence of a new module (Nwiki) and create the relevant MySQL tables, and carry out the 'migration' process etc.
6. I will then be able to access the wiki activities in the courses and see that migration has been successful.
7. If 1 to 6 is a success I will then do the same with my production site.
   

How does that look? Are there any other steps I should carry out?

Hello Ludo,

Good to see that NWiki will become the default Moodle wiki, though looking at the roadmap I see that this will not be for another year.

So I wonder what you suggest? Should I continue to try and use the standard Wiki activity module (EWiki), which has more and more bugs (e.g. MDL-11816 & MDL-6144), or should I 'take the plunge' and download Nwiki? It seems that every time Moodle gets updated, another wiki function gets damaged. On the other hand, the NWiki module also seems to have a few bugs. I am especially concerned that if I switch to NWiki (which version?), will my present wikis made by students survive the migration?

I welcome any advice you have for this teacher in a quandary over how to proceed with Wikis.

I am using Moodle 1.8.3., Apache 1.3.33, php 5.2.1, & MySQL 5.0.24a.

Hello,

I am using the standard wiki in moodle 1.8.3 +. This bug has also been replicated in the Demo Moodle site (username "teacher", password "demo").

On older versions of moodle, e.g. moodle 1.8, it was possible to export a wiki as a zip file, which could be saved on a users hard disk. The zip file contained an HTML version of the wiki. This was a great feature since it allowed students to keep an off-line 'portfolio' of their work.

This feature (along with other features of the Wiki module) now appears to be 'broken'. In order to export a wiki, the user clicks on the -- Choose Wiki Links -- pull-down menu, and selects 'Export pages'. Then teachers or admin can choose where to export the wiki: to a directory in the course files, or a Downloadable zip archive. Click here to see an image of this export page. Students can not choose, and are only able to download their wiki as a zip archive.

However, on clicking on the [Export] button, the following appears at the top of the page (this is just a sample):

PK ����LR70�������� ���group.htmleQ�n� ��W2SZ��V�cKQG0�F��2$rT�� g�D����;�c�M>j ...

Click here to see a screenshot of this page.

Teachers can still successfully export wiki pages to the course Files diretory.

I do hope that this can be fixed (see MDL-11816) since it appears the new wiki (NWiki) will not be a part of the standard Moodle release until the end of next year - version 2.0. Or, should I take the plunge and install Nwiki now?

Hello Amanda and anyone else trying to use the default Wiki,

In the absence of a solution to this bug (files can't be uploaded) I have come up with a workaround.

Using the Database activity module I have created an 'activity' called 'File Bank'. Students upload their files to that, and then copy the URL for the file that they want to add or link to their Wiki.

Students then access their Wiki and use the icons in the HTML editor to either add links to files in the 'File Bank', or embed images that have been saved in the 'File Bank'. This seems to work better than the original method of adding attachments to wiki pages.

Hope this idea is of use to other moodlers.