Non-core contributed modules

Enabling AJAX on 1.8.2+ caused Activity Locking to not work properly even after AJAX was disabled. Activities will not unlock when supposed to.

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 1.8.2
  • Fix Version/s: None
  • Component/s: Patch: Activity Locking
  • Labels:
    None
  • Environment:
    1.8.2+, problem occurs on Windows XP & Mac OS 10.5 and with all browser types.

Description

We enabled AJAX over the weekend on our avteconline.org server, maintained by remote learner. Since then Activity Locking v2.0 has not been working properly. So we disabled AJAX and that took care of some of the challenges but now none of the activities will unlock even after the prerequisites have been fulfilled. We can not make this work no matter what we do. This has effectively SHUT down some of our courses that are based on activity locking so would appreciate help at your earliest convenience. Remote Learner is working on assisting us with this. Can we just blame Shane Elliott? It was during his presentation in Alaska that we learned about this feature, of course he did not advise us to enable it on a production server we just got a little carried away by the moment Thanks for any assistance we can get. You can see an example of this at avteconline.org if you log in using ASTE2008/ASTE2008 and click on the Moodle Boot Camp 2007 course. Click on the Scavenger Hunt Quiz and you will see that you can not access it without first clicking on the Scav Hunt Activity. Even after you click on the activity you still can not get into the Scav Hunt Quiz. We also created a brand new lock and that would not work either. You can also see that the ASTE2008 student can not get into the Tour Quiz even though they earned a 10/10 on the Scav Hunt Quiz as required by the Tour Quiz Lock.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Debra Burdick added a comment -

UPDATE. Nick at Remote Learner was able to fix our problem. Apparently after enabling AJAX we started encountering a problem with our logging database not getting written to so therefore the activity would not unlock since the logging database was not updated. Nick fixed this so it is now working. Whether or not enabling AJAX caused this or not, we do not know for sure but it is suspected.

Show
Debra Burdick added a comment - UPDATE. Nick at Remote Learner was able to fix our problem. Apparently after enabling AJAX we started encountering a problem with our logging database not getting written to so therefore the activity would not unlock since the logging database was not updated. Nick fixed this so it is now working. Whether or not enabling AJAX caused this or not, we do not know for sure but it is suspected.
Hide
Permalink
Anthony Borrow added a comment -

Debra - Thanks for the update. Perhaps you might encourage Nick to comment on the bug or what he did to fix it. That will help me to resolve it. Peace - Anthony

Show
Anthony Borrow added a comment - Debra - Thanks for the update. Perhaps you might encourage Nick to comment on the bug or what he did to fix it. That will help me to resolve it. Peace - Anthony
Hide
Permalink
Debra Burdick added a comment -

Good idea. I left a message for Nick to do just that. Thanks for the quick reply.

Show
Debra Burdick added a comment - Good idea. I left a message for Nick to do just that. Thanks for the quick reply.
Hide
Permalink
Nicholas McJetters added a comment -

This problem was caused a corrupt log table in the database. It is unclear if the table became corrupt at the same time or near the same time AJAX was turned on. The events in the log are used by activity locking to determine if the pre-req has been fulfilled and to unlock future activities. This behavior explains why already completed activities in the log were unlocked, however future activities completed after the log had become corrupt were not being recognized by the activity locking. Once the table had become corrupt, Moodle had stopped writing events to the log. Once the log has been repaired, events could be written to the activity log and activities may now be unlocked normally.

Show
Nicholas McJetters added a comment - This problem was caused a corrupt log table in the database. It is unclear if the table became corrupt at the same time or near the same time AJAX was turned on. The events in the log are used by activity locking to determine if the pre-req has been fulfilled and to unlock future activities. This behavior explains why already completed activities in the log were unlocked, however future activities completed after the log had become corrupt were not being recognized by the activity locking. Once the table had become corrupt, Moodle had stopped writing events to the log. Once the log has been repaired, events could be written to the activity log and activities may now be unlocked normally.
Hide
Permalink
Anthony Borrow added a comment -

Matt - Sorry for the delay in assigning this to you. I have it worked out now that new bugs for this block will automagically be assigned to you. Peace - Anthony

Show
Anthony Borrow added a comment - Matt - Sorry for the delay in assigning this to you. I have it worked out now that new bugs for this block will automagically be assigned to you. Peace - Anthony
Hide
Permalink
Matt Gibson added a comment -

Although this involves AJAX, its not the AJAX marking block, but the wider AJAX editing system and its interaction with the activity locking patch. Not my department I'm afraid I've created a new component - Patch: {none of the above} temporarily as there is no activity locking component to assign it to.

Show
Matt Gibson added a comment - Although this involves AJAX, its not the AJAX marking block, but the wider AJAX editing system and its interaction with the activity locking patch. Not my department I'm afraid I've created a new component - Patch: {none of the above} temporarily as there is no activity locking component to assign it to.
Hide
Permalink
Matt Gibson added a comment -

Hi Anthony,

I just noticed this bug was still in my to do list. Not sure who it needs assigning to, so I'm throwing it your way.

Matt

Show
Matt Gibson added a comment - Hi Anthony, I just noticed this bug was still in my to do list. Not sure who it needs assigning to, so I'm throwing it your way. Matt
Hide
Permalink
Anthony Borrow added a comment -

It looks like a few months ago I thought that Matt was handling this issue (don't ask me where I got that idea from or why I assigned it to him). I believe Bernard is handling the Activity Locking issues. In any case, it looks as though the issue was resolved for the reporter of the issue. I am not familiar with the AL code so I wanted someone more familiar with it to be aware of the issue and read what happened and how it was fixed just to make sure there was not an issue that they might wish to address. Peace - Anthony

Show
Anthony Borrow added a comment - It looks like a few months ago I thought that Matt was handling this issue (don't ask me where I got that idea from or why I assigned it to him). I believe Bernard is handling the Activity Locking issues. In any case, it looks as though the issue was resolved for the reporter of the issue. I am not familiar with the AL code so I wanted someone more familiar with it to be aware of the issue and read what happened and how it was fixed just to make sure there was not an issue that they might wish to address. Peace - Anthony

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.