A final update on this project.
On Tuesday 3rd July we carried out the final synchronization of data between our and ULCC’s Moodle and pointed moodle.arts.ac.uk
to UAL servers, making Moodle live on our own systems.
A number of issues were identified, which we were not able to test during the development or User Acceptance Testing stage. A summary of these issues is below, but they are all now resolved. (As part of the work, we have increased the security of Moodle and this will prevent embedded content from displaying in certain circumstances. Details of this, and how to manage the problem is at the bottom of this blog post.)
The other good news is that the Web Services team have successfully recruited to the post of VLE Application Support Analyst and Fardin Amiri is due to start with the Web Services team, 7 August. Fardin will be a great boost to the team, providing vital resource to support the in-house provision of our Moodle platform.
That’s not the end for Moodle: we still have the SITS integration and the 2018/19 rollover scheduled next week. We are, however, in a strong, and exciting position in terms of what we can now consider to do to continue improving the experience and service for all staff and students that rely so much on Moodle for teaching and learning.
Summary of issues:
- Loss of connection to Blackboard Collaborate: Resolved
- Unable to send external emails: Resolved
- Course list not displaying correct hierarchy. Resolved
- SSO for Workflow and MyBlog not working Resolved
- Un-enrolling users – In Progress – this is not a bug or an issue with Moodle but related to the SITS project. This will be resolved when we switch on the data feeds from SITS next week.
- New student applicants not showing as enrolled in Moodle: – In Progress – this is not a bug or an issue with Moodle but related to the SITS project. The Registry team are still working on enrolling new applicants in SITS and this work is expected to be complete by the end of July ready for pre-sessional activities in Moodle starting in August.
As part of moving Moodle in house we have also increased Moodle’s security and implemented https. Content that has been embedded in Moodle sites using iframes may not display if the content comes from a third party webiste which doesn’t allow or support https.
It’s important to note that this is not Moodle or the UAL environment which is preventing this from working – it’s actually the browser. The reason for this behaviour is that it’s seen as a security risk to mix http and https content in one page.
As many browsers are now moving to support https many websites will be converting their sites accordingly, so this problem will gradually be less and less of a problem. If embedded content isn’t working because https isn’t supported, then the only option is to use a regular link to point to the content, rather then embed it into a Moodle site.
Moodle is now fully back in service and colleagues are able to edit their course sites. If there are any issues or problems in using Moodle that you feel have arisen from this recent work, please do report these to email@example.com for the team to investigate.