Checklist

So I changed the permissions for all the files to 0644 and the folders 0755, but that made no difference, sadly.
I'll have to rethink what I can do ...

If that is the only error message, then you should probably fix the permission on the file as it suggests that your server is kicking up a fuss over the permissions.
If that doesn't help, then I'm not sure what to suggest.

Sorry for my vagueness, Davo.
Here's what happens:
- Add checklist activity -> give name and description. No other changes to settings -> Save and return to course
- Checklist appears
- When I click on the Checklist activity, I get a white screen with the same error message that Dimo reported.
- Debugging does not produce any additional info.
- Server log report as in my previous message.
Does the server log report give a clue? The view.php permission is set to 0666. In contrast, view.php files of other activities are 0644.

David,
I'm afraid there isn't much for me to go on there. I have the plugin working fine locally with Moodle 2.5.1.
You haven't told me what you have to do to produce the error - does it appear when you try to add a checklist to a course, when you click to view a checklist, when you view a course with a checklist in it, or do you have to do something else to trigger the error.
Does it affect existing checklists only, or just ones that were added since you completed the upgrade?

Davo,
I get the same error as Dimo, again using mdl 2.5.1.
All debugging in moodle does not add info, but the server log reports:
[Mon Sep 09 15:38:15 2013] [error] [client 62.238.42.176] SoftException in Application.cpp:256: File "/home/moodle/public_html/mod/checklist/view.php" is writeable by group, referer: http://mysite/course/view.php?id=131
I have already uninstalled and reinstalled the activity mod and the block.

Dimo - I have it working fine with a local install of Moodle 2.5.1.
I suggest you increase the debugging level on your system and then check the logs to see if a more helpful error message appears.

Hello,
This is one of my favourite plugins. It works fine on our moodle 2.2.3 school, but now we have a problem with the new moodle 2.5.1 school. The instalation of mod_checklist seems to be ok, but I can't set the plugin. It returns:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@myschool.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Any help will be greatly appreciated.

Thanks for that German.
As I had some other (Moodle 2.5) fixes to push through as well, I've released a new version. The language strings should now be on AMOS, if you wanted to update the es_mx language pack.
Davo

Hi Davo,
This is a great plugin.
I think it will be even better if you add the following English language string along the lines of:
$string['modulename_help'] = 'The checklist module allows a teacher to create a checklist / todo list / task list for their students to work through.';
The modulename_help string is the explanation a teacher gets when he chooses to add an activity by way of the activity chooser in Moodle 2.3 upwards. Most Moodle core plugins and many addons already have such a string.
I hope you can add this new english language string. The es_mx translation for that string might be 'El módulo de lista de cotejo le permite al maestro crear una lista de cotejo / lista de pendientes / lista de tareas, para que los estudiantes trabajen al respecto.'
Thanks again for another great plugin.

As I don't have any java code in the checklist plugin, it's more likely to be a javascript problem. Please use http://tracker.moodle.org to report any issues like this - try to give as much details as possible about how to reproduce it and I will look to see if I can put together a fix.

Having an issue with IE8 only. Seems to work in firefox, chrome, even IE9 but version 8 displays errors on page. A closer look at the errors and appears to be in /mod/checklist/updatechecks24.js. This is the message Message: 'checked' is null or not an object
Line: 63
Char: 25
Code: 0
Appears to be java related. Anybody come across this or have any ideas?

@Aaricia - Thanks.
Reviews are only available for 'trusted reviewers'. I'm not quite sure who is on that list at the moment (but I've not seen that many reviews on plugins).

I was going to add a review for the plug-in, but it does not allow to write a review, I don't know why.
I just want to mention that this is a smart reliable plug-in which is easy to configure and use.
At the Medical School of the University of Dundee, we are using the checklist to monitor our students' progress through the academic modules.
The possibility of downloading an xlx spreadsheet is extremely useful for us.
We certainly recommend the plug-in. We haven't encountered any bugs so far.

Hello again, Davo.
I have been asked to freeze the first column of the html table generated by the cheklist, 'View Progress' option, the column with the names of the students. We would like the column to remind fixed, while rows scrolls horizontally,
I believe that the names column is generated in file locallib.php, in line 1867:
// First item is the name
$output .= ''.$item.'';
There is not an straightfoward way to freeze this column: I can use
I thought that one of the easiest ways could be the following solution:
http://jsfiddle.net/emn13/YMvk9/
I just wanted to share it with you in case that you are also trying it. Freezing the usernames column in the report could be very helpful for administrators

update. If I log in as Student Test, the last access still keep showing 'Never',
It is not the first time that I can see this pitfall in Moodle: that when you log as if you were a student it does not update database logging entries for that student.
I thought that this doesn't happen in Moodle 2.0, but I did happen yesterday in our Test server, for Moodle 2.2.4