Document ID XXXX.png has never been checked in. The server copy cannot be published.

From UPK wiki
Jump to: navigation, search

Contents


The following messages are generated during Publishing or Preview:

Status Task Name Type Path Comment Ref. #
Warning Player and LMS / Creating hotspot images Screenshot missing for the frame: xxx 0
Warning Player and LMS / Copying screenshots {Topic name} Topic /XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/XXX.png Document 'odlib:///XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/XXX.png' has never been checked in. The server copy cannot be published 0

Note that if you are publishing a document from your local repository, then the final message may appear as:

Status Task Name Type Path Comment Ref. #
Warning Player and LMS / Copying screenshots {Topic name} Topic /XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/XXX.png Broken link 0

Note the XXXX.png in the message.

Root cause

UPK thinks that there are more Frames in the Topic than there really are. Possibly the manifest.mfx file has become corrupted. However, it may also be a problem with the topic.xml file.

Resolution

Option 1: Correct the topic.xml file

Check out the Topic (identified in the message via its Document ID) and then go to the folder for this Topic in your Local Repository. First, check that the .png file mentioned in the error message does not exist in the Topic's folder, and that it is not listed in the manifest.mfx file. Assuming that this is the case, locate the topic.xml file and open it in Notepad (or other (pure) text editor). Search for the xxxx.png file specified in the message. You will probably find a section similar to:

     <Frame ID="F3151" Type="Explanation">
        <Infoblocks />
        <Screenshot xlink:href="3151.png" />
        <Actions />
     </Frame>

Assuming that there is no content other than a .png file in the <Frame> section, this is probably just a historical anomaly (the Frame was deleted from the Topic but UPK didn't delete it cleanly). Delete this whole <Frame> section, and then save your changes to the topic.xml file.

Go back ito the Library. Make a note of the number of Frames in the Topic (display the Frames column to see this). Edit the Topic, and make a small change to it (so that UPK doesn't just cancel the check-out when you check it in). Close the Topic Editor and re-check the number of Frames - you should see that it has decreased by 1. If it has not, you will need to try something else. Assuming the problem is now fixed, check in the Topic, and try publishing again.

Caution:
Take a copy of the topic.xml file first...

Option 2: Recreate the Topic

If correcting the manifest.mfx file does not work, then you will need to recreate the Topic. The easiest way to do this is to create a dummy Topic with only one Frame (the minimum) in it, then copy all of the Frames from the orriginal 'broken' Topic and paste these into the new Topic. The Start Frame and End Frame will be converted to Explanation Frames, but other than that all Frames, Custom Text, Alternative actions, Alternative Paths, Decision frames and so on will be copied over correcty. Don't forget to delete the one Frame held over from the dummy Topic, and re-specify all of the Topic properties.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox