FrameBook Checkout errors
- Resolution:
- To unlock the object, select the object in Contenta, then click .
- Issue/Problem:
- Error message from FrameBookCheckout:
- Explanation:
-
The container objects for the FrameMaker and graphic data objects are not in the same parent container in Contenta.
- Resolution
-
Make certain that the data and graphic objects are in containers under the same parent container in the Contenta Explorer hierarchy.
- Explanation:
- The graphic file does not exist in Contenta in the graphics container.
- Resolution:
-
Check that the graphic file exists in the graphics container under the same parent as the FrameMaker file/object that is being checked-out.
- Explanation:
-
The graphic file name case that is referenced in the FrameMaker file does not match the case of the object name in Contenta.
FrameBook Checkout extracts names from the FrameMaker document which may not use the same case as the graphic object name.
Note that FrameMaker is case-sensitive for graphic filenames. You can use one of the resolutions below to resolve the error.
- Resolution 1:
-
Capture the error message that display when Contenta tries to export the files—that is, the error message that contains the graphic filenames that cannot be found.
- Import/checkin the files to unlock them.
- Find the graphics in Contenta and rename the objects to adhere to the case of the filenames being referenced (the case and filenames in the error message screen).
- Export/checkout the files again. There should be no errors.
- Resolution 2:
-
Check-in the files to unlock them, delete them, then re-import making sure that you:
- Add the
-t4switch tosplit argsin the Dynamic Import configuration file (digui.cfg)—see the Dynamic Import/File Import topic.. - Validate the file contents, for example, that the references are valid and do not error, by opening the files in the FrameMaker application.—see the Before Importing topic.
- Add the
- Issue/Problem:
-
Checkout erroneously reports an error that there is no Mime Type or no Document Type in the property sheet field when there is valid data in the field.
- Explanation/Resolution:
-
Occasionally when checking-out an object, the focus has shifted to the parent object in the left pane of the Contenta Explorer interface. Although it appears that the object to be checked-out is selected in the right pane, focus has shifted to the left pane.
When the error(s) noted are seen, it is typically because the internal focus is on an object, such as a container object, that does not have these property sheet fields or there is no data in them because it is not required for that object type.
To change focus to the correct object, select the object to be checked-out again in the right pane then select the checkout option.
- Issue/Problem:
- Checkout reports an error that there is no Mime Type or no Document Type in the property sheet field when there is valid data in the field.
- Explanation/Resolution:
-
The checkout and edit tools require data in these fields. Right-click on the object to access the property sheet and enter valid data in the field. If you are unsure of the data to enter, contact your Contenta Project Manager for this information.
Information about these property sheet fields and how they are used by Contenta is included in the FrameBook Tool Setup topic in the Contenta Administration user documentation, and the Contenta Dynamic Import user documentation.
- Issue/Problem:
-
FrameBook Checkout/Edit; graphic objects with dots in their (original) filenames are not being found or exported.
- Explanation/Resolution:
-
Dots in graphic object names trigger a bug in FrameBook Checkout. While Dynamic Import preserves dots in filenames, checkout tool does not recognize them in graphic files/objects. When you open a file in FrameMaker that references a graphic with a dot in the filename, the referenced graphic file is reported as missing/cannot find file. Assuming that the FrameMaker file(s) have been checked out and reside in the checkout directory:
- If the referenced graphic was imported and exists in the Contenta repository, checkout the referenced file/graphic from Contenta. Skip this step if the graphic is not in the repository.
- Locate the referenced file/graphic on your system; if checked-out, locate it in its checkout folder.
- Copy the file from its location on your system to the graphic folder in the checkout folder where the FrameMaker file(s) that references it, is located. If the filename contains dots make sure you rename it without dots (except for the dot before the file extension).
- Open the FrameMaker file that contains the reference. When prompted to locate the missing file, indicate the file that you copied (and possibly renamed).
- If you checked-out the graphic from Contenta, check it in to unlock it in Contenta.
When you checkin the FrameMaker file(s) the referenced file is checked-in. If it already exists in the repository, know that a new graphic object is created. If you only want only one copy of the graphic in the repository, delete the new one that was created during checkin and replace (Reuse/Paste) it with the one that already exists in Contenta.
- Issue/Problem:
- Checkout reports locked objects and the only option is for check-out is read-only.
- Explanation/Resolution:
- If you run FrameBook Checkout and some or all of the FmBook or FmDoc objects are locked you get a warning message, for example:
This is expected behavior. If the object is locked it cannot be checked-out for editing. If you check-in the file it is unlocked and can be checked-out for editing.