Open pjritee opened 9 years ago
If the student's submission shows up in the admin tool, then it's probably a bug in the "show submissions" feature (which was written before late submissions were implemented, so it's possible that a bug was able to creep in there).
If the submission shows up there, you can direct the student to the page http://csse1001.uqcloud.net/cgi-bin/mpt3/progress.py to let them know that the submission exists (it will show them the same thing that you see, but without the "allow late" features).
If the student's submission does not show up on that webpage, then there are a few possibilities: (a) the student has not properly attempted a submission (e.g. they thought they did, or they got the question correct without an internet connection and didn't submit later, etc.). (b) a bug in the server component which accepts submissions and records them (e.g. the server didn't store their submission for whatever reason). (c) a bug in the server component which retrieves stored submissions (there's a shared module on the server used by both the web interface and the JSON interface that the desktop app talks to).
It looks like progress.py and mpt_cgi.py use different support calls for submissions. Even if that's not ultimately the issue, we should probably refactor that.
On Monday, May 4, 2015, Jackson Gatenby notifications@github.com wrote:
If the student's submission shows up in the admin tool, then it's probably a bug in the "show submissions" feature (which was written before late submissions were implemented, so it's possible that a bug was able to creep in there).
If the submission shows up there, you can direct the student to the page http://csse1001.uqcloud.net/cgi-bin/mpt3/progress.py to let them know that the submission exists (it will show them the same thing that you see, but without the "allow late" features).
If the student's submission does not show up on that webpage, then there are a few possibilities: (a) the student has not properly attempted a submission (e.g. they thought they did, or they got the question correct without an internet connection and didn't submit later, etc.). (b) a bug in the server component which accepts submissions and records them (e.g. the server didn't store their submission for whatever reason). (c) a bug in the server component which retrieves stored submissions.
— Reply to this email directly or view it on GitHub https://github.com/CSSE1001/MyPyTutor/issues/162#issuecomment-98592197.
Probably best done when the whole support module is thrown out and replaced with a database.
Agreed.
You could even transition to something like django, which would let you get rid of the CGI scripts at the same time. (And I'm just a fan of django's ORM anyway.)
On 4 May 2015 at 16:44, Jackson Gatenby notifications@github.com wrote:
Probably best done when the whole support module is thrown out and replaced with a database.
— Reply to this email directly or view it on GitHub https://github.com/CSSE1001/MyPyTutor/issues/162#issuecomment-98599504.
Django does seem like the way to go
A student had some late submissions allowed and wanted to check if it was OK - I suggested looking at "Show Submissions" but apparently it shows it has not been submitted. My admin tool (that jgat wrote seems to be working fine)