Login
Home CMS Documentation Home CMS 10 DITA Processing Pipeline in Ingeniux CMS Authoring and Editing DITA Content Oxygen Desktop Plugin Oxygen Desktop Plugin Authoring and Editing Special Plugin Topics Resolving No CSS File Specified Errors Verifying Frameworks Location

Verifying Additional Frameworks Directory Location

Prerequisites: Define a document type framework. See Resolving No CSS File Specificed Errors for details.
The Oxygen Desktop Plugin automatically generates an external location for additional frameworks in [Drive:]\Users\[name-of-user-on-machhine]\Oxygen\additional_frameworks.

CMS content contributors create custom frameworks when they edit document association types in the Preferences dialog. If contributors have a custom framework stored in the additional_frameworks directory when they start their Oxygen XML Editor application, then the system automatically syncs the custom framework in the external location.

Note
This folder is only available to the user with the Oxygen Desktop Plugin installed and not to other users on the machine.

Contributors can perform a test to verify that the Oxygen Desktop Plugin references the additional frameworks location.

To verify the additional frameworks location:
  1. Open the Oxygen XML Editor application.
  2. Select Options > Preferences in the tool bar.

    Options > Preferences

    The Preferences dialog displays.
  3. Click Document Type Association > Locations in the Preferences dialog.

    Document Type Association Locations Preferences

  4. Ensure that Global Options displays as selected in the bottom-left area under the Additional frameworks directories list.
  5. Ensure that the [Drive:]\Users\[name-of-user-on-machhine]\Oxygen\additional_frameworks displays in the Additional frameworks directories list.
  6. Open your machine's file explorer, and navigate to [Drive:]\Users\[name-of-user-on-machhine]\Oxygen\additional_frameworks. Ensure that your additional framework(s) display in the folder.
    Troubleshooting
    If the expected frameworks don't display in the locations list or in the additional frameworks directory folder, then see Resolving No CSS File Specified Errors for details to create a framework and set the storage location to External. After creating the framework, restart the Oxygen XML Editor application so that the Oxygen Desktop Plugin copies the new framework to the directory.

    Additional Frameworks Directory

  7. Navigate to Document Type Association in the Preferences dialog of the Oxygen XML Editor UI.

    Document Type Association Preferences

  8. Ensure that Global Options displays as selected in the bottom-left area under the document type list.
  9. Locate the framework in the Document Type Association list, and ensure that the Enabled checkbox displays as selected.
    Important
    If the framework is disabled, then Oxygen XML Editor doesn't apply the framework for DITA content items with associated templates.
  10. Select the framework, and click Delete.
    The Delete dialog displays.
    Warning
    Ensure that your framework's storage location is set to a child folder of [Drive:]\Users\[name-of-user-on-machhine]\Oxygen\additional_frameworks. Otherwise, the system will permanently delete the framework. See Resolving No CSS File Specified Errors for details to set the framework location.
  11. Click Yes to confirm the deletion.
  12. Restart the Oxygen XML Editor application.
  13. Return to Document Type Association > Locations in the Preferences dialog of the Oxygen XML Editor UI, and ensure that the additional framework location displays in the list.
  14. Return to Document Type Association in the Preferences dialog of the Oxygen XML Editor UI, and ensure that your custom document type framework displays in the list.
    Note
    The system syncs with your additional frameworks location and automatically re-generates the framework in the Document Type Association list.
  15. Open a DITA content item associated with a custom template, and ensure that No CSS File Specified errors don't display to verify that the system references the custom framework.