Moodle Core’s announced a number of big changes to the Moodle gradebook for the 1.9.5 release. Among the changes:

• the student name column is now sticky (which means you can still see if if you scroll to the right to look at additional assignments).
• The categories page has been re-organized and color coded to make things easier to understand.
• Administrators can now reduce the number of grade aggregation methods.
• The Gradebook’s drop-down navigation menu can now be supplemented by tabbed navigation.

There’s a lot of stuff in there. We’re going to be delving into it on a test server just as soon as the code is released to CVS; I’m looking forward to seeing how our usability tests run with this new Gradebook.

The issue appears to be a change in the default settings for the wiki. Making the wiki configuration tweaks described in this Tracker report fixed the problem:

• MDL-10641 Wiki binary files option broken

To start, you need to understand how Moodle tolerates risks based on roles (defined under “Risks” in the Moodle Docs wiki.):

• Guest - only capabilities without any risks are allowed
• Student - certain capabilities with spam risks are allowed
• Teacher - certain capabilities with XSS and privacy risks are allowed
• Administrator - all capabilities are allowed

This is important because any custom roles you’ve created are evaluated based on the legacy role that spawned them. So if you start with a student role, and give it some more advanced teacher-like options that allow XSS capabilities, then Moodle will set a critical warning flag because its exceeded the capabilities normally associated with a student.

I need to doublecheck this, but I think that if you change the legacy role associated with the custom role in question to “teacher”, then your custom capabilities will remain the same, but the report will run against the more permissive teacher role. That said, you may not want to get rid of the warnings (since it is helpful to know what a “super student” role could get themselves into) but at least this write-up should help you understand them.

I’d love to see Moodle create a more user-friendly report that says something like:

• “Your role ‘Teacher Assistant’ is based on the legacy role ‘Student’. By default, students are not allowed to have capabilities that permit Cross Site Scripting (XSS), but your custom role allows the following XSS capabilities” — I’d then include a list of the problem capabilities.

You can contribute to improving the Security Report by reading/commenting on this tracker item:

• MDL-18078: Provide a feedback for the admin in order to explain him/her what to do to fix the security problem rised up by the security report

“overLIB 4.10 or later is required for the CSS Style Plugin”

A little searching revealed that this is apparently a problem with the browser’s cache; clearing the cache causes it to go away. If you’re proxying Moodle, you may need to clear the proxy’s cache as well. There’s no Tracker item for it; I thought of adding one, but this isn’t really a Moodle problem — it’s a browser one.

• moodle.org: Overlib problem (moodle thread discussing the problem and fixes)
• octette.cs.man.ac.uk overLIB 4.10 or later is required for the CSS Style Plugin

I experimented with using NanoGong to do this, but unfortunately it was just too unstable; the Java applet running it refused to save files on two of the three computers I tried it on … including computers on which it had worked.

COVCELLL has created the audio recording assignment that works with Moodle 1.9. I haven’t had a chance to try it yet, and would love to hear from anyone who has.

The problem comes when you try and delete that file — Moodle’s scripts can’t handle the special character, and refuse to allow you to move, delete or otherwise modify the file. Fortunately, a fix is coming in Moodle 1.9.5 thanks to the work of Charles Fulton of Kalamazoo College at Hack/Doc Fest III at Reed College in January 2009.

You can read about it in tracker here:

• MDL-237 Special characters left in filenames after unzipping

A patch is available via tracker. A fix will be available in Moodle 1.9.5.

It was removed to avoid licensing conflicts, but no fears — it still works with NextGEN, but now site admins (like me) need to go grab a copy of JW Image Rotator when they install/upgrade the plugin. This won’t affect your site or blog at Lafayette; I’ll be sure to include the file when we do the upgrade here.

The final Quicktime video is 960×600 pixels (about 50% of the original screen size) It is 1.04 minutes long, and 7.7 MB in size. I used the “Web - High” setting (H.264 video encoding at 850 kbits/sec. AAC sterio audio at 96 kbits/sec). The original video was full-screen; I didn’t attempt to do a full-size export.

Observations: ScreenFlow offers a lot more options than Silverback. For example, when doing the capture I could choose which of my Mac’s iSight cameras I wanted to use (the MacBook Pro’s built in iSight or the one on my external monitor) as well as which monitor to use (the MacBook’s or the external one). It includes 11 export options, and a number of video tweaking options within the program, including the ability to move/resize the picture-in-picture video and the ability to add on-screen text. I like Silverback for its fire-and-forget nature, but I think ScreenFlow offers us more long-term flexibility.

Download

http://wordpress.org/support/topic/251863?replies=1

Here’s what I suggested:

The Default Image Rotator location

The plugin attempts to guess the default location for the imagerotator.swf file based on the assumption that the plugin is installed as part of a standard WordPress installation. This makes the path something like:

http://www.example.com/username/wp-content/plugins/nextgen-gallery/imagerotator.swf

Unfortunately, in a WordPress MU install, the plugin is not located in the user’s directory; instead it’s in the main plugins directory. e.g.:

http://www.example.com/wp-content/plugins/nextgen-gallery/imagerotator.swf

It’d be great to have a global option that allows me to specify what the default path should be for all of the NextGEN galleries on the WordPress MU install.

Global “Disable Flash Uploader” option

The Flash uploader has been problematic on and off for a while. While 2.7 got it working on non-secure sites, there’s a known issue with Flash and https that prevents it from working in sites secured with https.

NextGEN allows users to disable the Flash uploader on a per-site basis, which is helpful, but I’d love a global option that would allow me to disable the Flash uploader site-wide.

If these options sound helpful to you, please drop by the forums and add your voice to the conversation.