Drafts and publishing

Students and the judge always use a problem’s published version. Changes collect in a draft and reach students only when you publish. Editors of the problem can publish.

Versions

• A problem’s versions are numbered 1, 2, 3… The top of the problem page shows Version N · published with the date, or Version N · not published.
• A published version never changes. Every submission stays tied to the version it was judged against, so past results can always be explained.
• A problem has at most one unpublished version – its draft. A new problem starts as a draft of version 1.
• The app has no list of earlier versions: only the current one is shown.

What is kept where

Change	Kept until publishing	Seen by other editors
Title, statement, sample tests	Only in your browser	No
Time and memory limits, languages, input and output	Only in your browser	No
Hidden tests, test points and limits	In the server draft	Yes
Excel rules, starter workbook, uploads per student	In the server draft	Yes
Difficulty, sharing, collections, wiki pages	Applied at once, outside versions	Yes

The first change to tests or rules creates the server draft – a copy of the newest version (the notice says draft of version N started). Later changes edit the same draft. The tests page shows whether the draft holds unpublished changes.

Caution

Statement and settings changes kept in the browser are not visible on other computers and are lost if the browser’s data is cleared. Publish when you finish.

Publishing

1. At the top of the problem page, click Publish….
2. In Publish version N?, read:
   • that students who already submitted keep their results against the earlier version, while new submissions use the new one;
   • how many courses use the problem;
   • whether the draft’s test changes are published with it;
   • the Before publishing checklist.
3. Click Publish version N (or Keep editing).

If some checks are not met, the dialog says so (Some checks are not met. You can still publish.) and still lets you publish. An Excel task without rules worth points can’t be published.

After publishing:

• the new version holds the statement, sample tests, limits, languages, input and output, and the draft’s tests or rules;
• students who already have the problem see the new version at once, and new submissions are judged against it;
• earlier submissions are not judged again and keep their results;
• course lists show the new version’s title;
• staff submissions made while testing the unpublished version are deleted;
• the browser draft is cleared, and the header shows Version N published.

When publishing fails

Message	What to do
Someone published a newer version while you were editing…	Another editor published first. Your draft is kept in this browser; reload to continue from the new version.
Some settings are not valid: …	Fix the fields named (the time limit or file names, for example).
One of the chosen languages is no longer offered.	Change the languages in the Judging card.
Add at least one grading rule worth points before publishing.	Add rules to the Excel task (see Excel tasks).
Publishing failed. Your work is still here; try again.	Try again later.

Converted statements (“Needs review”)

Problems imported from the old system had TeX statements, which were converted to the new format automatically. When the conversion produced warnings, didn’t run or failed, the problem is marked Needs review and found with the filter of the same name in the archive.

Opening such a problem shows a warning strip above the statement (for example Converted from the old statement with warnings):

1. Expand Conversion notes to see which parts may be inaccurate.
2. Expand Original TeX and compare it with the statement in the editor.
3. Fix the statement.
4. Tick Conversion notes reviewed – this meets the item in the Before publishing checklist (the tick lasts for this visit only).
5. Publish. The reviewed statement is saved as a new version, and the Needs review label goes away.

Images in old statements often lack descriptions – add them in the editor (see Statement editor).