We're seeing a lot of errors with this errorcode using the plagiarism_turnitin plugin: 'There has been an error with your submission: The due date for this assignment has passed and late submissions are not allowed.'

this status also returns a 'success' as the statuscode so the current interface shows the turnitin id string and no error messages or status notification to the user.
here's an example from the db:

23310 226022 67785 2827d1cc17e6d7076481ac4635140f561726bff3 448636397 0 success 1
0 0 1409830538 file 0 There has been an error with your submission: The due date for this ass
ignment has passed and late submissions are not allowed.

we've fixed this on the turnitin side with this particular assignment and managed to get reports generated in Turnitin for those files but the scores don't update in Moodle. I think the entries are picked up by the list of $submissions in cron() as the orcapable and similarityscore fields are null and the statuscode is 'success' but the records aren't updated with the new score from turnitin.

I don't think the files are included in $readsubmissions = $response->getSubmissions(); even though the submissionid should be included in:
$submission->setSubmissionIds($submissionids);

looking closer to see if I can work out why but any pointers/feedback would be useful!

ah - it's a problem with:
...IS NULL AND orcapable != ?
where ? is replaced with the integer 0

with postgres a comparison with an integer using != excludes null values from the report.
so it should be something like this to include null values:
AND (orcapable != ? or orcapable is null)

also - if we're using sql to generate the submissions it would be more efficient to check for a valid cm in this first query rather than checking get_coursemodule_from_id on every submission returned. I'll send through a patch that does this for you to take a look.

doh - I need to keep up a bit better - looks like that null issue is already fixed in 80ab23e

We still need to investigate why the due date failure occured though.

looks like this occured due to re-use of an assignment from a previous year.

start date was set in Moodle but end date wasn't - it created the assignment last year and the due date Turnitin generated for that assignment had passed.

The old plugin I had checked for this sort of error and fixed up the due date on the turnitin side automatically - not sure if that's possible.

here's a dirty hack that I haven't tested yet:
https://github.com/danmarsden/MoodleDirectV2/commit/caa1fcac4038c73e329c747c4c230009aa47a99a

John - is there a more reliable way of detecting this error rather than relying on the errormsg string returned from the API?

Hey John - did you have any other ideas on this one for ways to manage this a bit better than the patch I've added above?

Hi Dan, I haven't managed to look into this this further yet. I'm currently unsure how it occurs though as in the 2 places we perform a submission we sync the assignment immediately before. When we sync the assignment we edit the start date so it can't be more than a year in the past in Turnitin. If no due date is set in the assignment it would be set to a month from now in Turnitin. I'll do some more investigating.

Hi Dan, is this still an issue for you. The dates that sync with Turnitin have been tweaked slightly for 2014012409. Late submissions is now always set to true as well to avoid any potential conflicts.

cool - makes sense to always allow late submissions on the turnitin side and just let moodle handle the submissions. If that is forced accross all existing and new assignments it should sort it. We've left that hacky patch in place so I'm not sure if it's still an issue but next time I update their site I'll remove the hack.