Contents

Version history - Plugixa Exam

Every edit to a question is kept, by default. That sounds like a convenience and is really an audit feature.

The question it answers

Somebody queries a mark from three months ago. The question has been edited twice since. Without version history you can see what it says now, which is not what they were asked.

With it, you can see what the question was at the time, and settle the query on what actually happened.

How it relates to frozen papers

The two work together and are not the same thing.

What it protects
Frozen paper A sitting in progress. Editing an exam or a question does not change it under whoever is answering
Version history The record afterwards. What the question said when a given attempt asked it

The first means an edit never disrupts a live exam. The second means an edit never quietly rewrites history either.

How many versions are kept

All of them, by default. versioning_keep caps retention, and 0 - the default - means keep everything.

Set a cap only if the volume genuinely becomes a problem, and understand what you are trading: the whole value of this feature is being able to answer a query about a paper somebody sat months ago, and a cap is what decides how far back “months ago” can reach.

Review workflow

Versions carry an approval status, so a question can be drafted, reviewed and approved rather than going live the moment somebody saves it. Useful where more than one person writes into the same bank.

Troubleshooting

Symptom Usual cause
No history on a question It has not been edited since versioning was switched on.
A version cannot be restored Restoring creates a new version rather than rewinding. The old one stays in the record.
The list is very long Every save is a version. That is the point; filter by date, or cap it with versioning_keep.
Old versions have disappeared versioning_keep is set to something other than 0.

What to do next

Quick Links

Plugin page Changelog