Assignment not showing in Grade me block

[sulaganathan]

hi,

We are using grade me block 3.1.0.2 on Moodle 3.1 and apparently the assignment which needs grading is not showing on grade me block. Upon further research I found that the query failed to choose the assignment on below condition

SELECT bgm.courseid, bgm.coursename, bgm.itemmodule, bgm.iteminstance, bgm.itemname, bgm.coursemoduleid, bgm.itemsortorder, asgn_sub.id submissionid, asgn_sub.userid, asgn_sub.status FROM mdl_assign_submission asgn_sub JOIN mdl_assign a ON a.id = asgn_sub.assignment LEFT JOIN mdl_block_grade_me bgm ON bgm.courseid = a.course AND bgm.iteminstance = a.id LEFT JOIN mdl_assign_grades ag ON ag.assignment = asgn_sub.assignment AND ag.userid = asgn_sub.userid AND asgn_sub.attemptnumber = ag.attemptnumber WHERE a.grade <> 0 AND (ag.id IS NULL OR asgn_sub.timemodified > ag.timemodified) AND bgm.courseid = 37333 AND bgm.itemmodule = 'assign' and bgm.iteminstance='177990

_asgn_sub.timemodified and ag.timemodified seems to be same date time so that query failed _

ag.timemodified is modified when ran the Moodle cron with the below record

id assignment userid timecreated timemodified grader grade attemptnumber
793 519 12 1485174949 1485174312 2 -1.00000 0

Please check and let us know the workaround

[sulaganathan]

@jamesmcq Could you please check this

[blakekidney]

We are experiencing the same issue. The solution seems to be making the comparison a >= rather than just a >.

asgn_sub.timemodified >= ag.timemodified

The idea here is that time the assignment was submitted is greater than the time it was last graded. That way, if a student submits an assignment again after it has been graded, it will show up as needing to be graded again. The two timestamps should never be equal as it would always take longer than a second from the time it was submitted to the time it was graded. So, if the two timestamps are equal, that would indicate they were set systematically which is what I think is happening.

[jamesmcq]

Hi All - we've added this to our internal work list. I don't have a hard timeline but we expect to tackle it soon. Thanks for the report!

[sulaganathan]

@jamesmcq any luck on this?

[jamesmcq]

@sulaganathan Currently scheduled for a developer to work on next week. Should everything go smoothly we'd be looking at release Feb 20th.

[sulaganathan]

@jamesmcq Might I anticipate newer version on Feb 20th. Please let me know if any delay on this

[sulaganathan]

@jamesmcq Has the version released? Please kindly let us know

[jamesmcq]

@sulaganathan We do have a fix for this issue scheduled for release. We're a little behind but will have it available in the next few days.

[wbuk]

Please can you let us know when, we are using the very latest version of Moodle and apply the weekly updates to ensure as bug free as possible. Marking is a nightmare, we really need this to allow us to mark all the work easily,

[jamesmcq]

Hi All, new versions for 2.7, 2.9, 3.0, and 3.1 are now available. Please let me know if this resolves your issues. @wbuk @sulaganathan @blakekidney

[sulaganathan]

@jamesmcq Thank You so much for the update,

You meant to say we should use this version for Moodle 3.1

https://github.com/remotelearner/moodle-block_grade_me/blob/MOODLE_31_STABLE/version.php

Please confirm?

[sulaganathan]

@jamesmcq I don't see any new version with release date in recent days, I would request you to share the link of newer version.

[jamesmcq]

@sulaganathan See https://github.com/remotelearner/moodle-block_grade_me/releases - the first two numbers of the version string correspond to the Moodle version you are using. For example, if you are using Moodle 3.1, choose "v3.1.0.3"

[sulaganathan]

Thank you so much for the info.

[nickvarney]

This new patch 'appears' to be intermittently working for us. Using the v3.1.0.3 version on Moodle 3.1.4.
Is the detection of new submissions instantaneous or run via the cron?