As far as we're aware (and we've delved in to the whole code chain), there is no way to retrospectively trigger the generation of the PDF versions from the student submission.
We found a way to "trick" it into happening by deleting specific database records in the files table (I don't have the exact details to hand) but this in our view is a *very* sketchy way to initiate this, and would like to see some sort of UI element (even it it capability controlled so *not* all users can do it) to "force" the regeneration.
As I said we did find some file records that seem to trigger it, so "in principle" we should be able to do this, we just haven't had the time to pick it up. *If there is a better* trigger for doing this we'd be open to those suggestions, but trying to understand the whole process with document converters, and then ghostscript and pages and images of pages and unstitiching PDFs made our brains really hurt
We found a way to "trick" it into happening by deleting specific database records in the files table (I don't have the exact details to hand) but this in our view is a *very* sketchy way to initiate this, and would like to see some sort of UI element (even it it capability controlled so *not* all users can do it) to "force" the regeneration.
As I said we did find some file records that seem to trigger it, so "in principle" we should be able to do this, we just haven't had the time to pick it up. *If there is a better* trigger for doing this we'd be open to those suggestions, but trying to understand the whole process with document converters, and then ghostscript and pages and images of pages and unstitiching PDFs made our brains really hurt