Technical Issues

An Error Icon Appears in the Top-Left Corner of the Tasks Manager View

If an error exception is detected, a warning icon () will be displayed at the top-left corner of the Content Fusion Tasks Manager view. Clicking the icon will display details about the particular exception in the Results panel at the bottom of Oxygen XML Editor/Author. If you need to report a problem to the Oxygen technical support team, right-click the entry in the Results panel and select Report problem. This opens a dialog box that allows you to select and configure information that will be sent to the technical support team.

Connection to the Server Cannot Be Established

If this message is displayed at the top of the Content Fusion Tasks Manager view, it means that there was a problem connecting to the server and more details should be displayed in the Results panel at the bottom of Oxygen XML Editor/Author. To report this problem to the Oxygen technical support team, right-click the entry in the Results panel and select Report problem. This opens a dialog box that allows you to select and configure information that will be sent to the technical support team.

Connection to the Server Cannot Be Established (Your Account No Longer Exists on the Oxygen Content Fusion Server)

If this message is displayed at the top of the Content Fusion Tasks Manager view after you try to upload a task, it means that there is a problem with your user account (for example, if you chose to delete your account in the Profile page). To solve this, click Connect to open the Oxygen Content Fusion interface in your most recently used browser, then click on SIGN UP and follow the instructions to re-create your account. After verifying your email address, don't forget to click the Authorize button in the Oxygen Content Fusion interface.

Connection to the Server Cannot Be Established (There was a Problem Establishing the Secure HTTPS Connection)

If this message is displayed at the top of the Content Fusion Tasks Manager view when you try to connect to the server, it means that there is a problem with the HTTPS certificate configuration of the server. You should contact your system administrator to solve this issue. To work around this problem, in Oxygen XML Editor/Author, go to Options > Preferences > Network Connection Settings > HTTP(S)/WebDAV and enable the Automatically accept a security certificate, even if invalid option.

Uploading a Review Task Takes Too Long

When uploading a review task that contains DITA files, along with the files explicitly selected for review, the task also contains the DITA map and all the files referenced from it (directly or indirectly). For large projects, this set of files is also large and can take a long time to upload.

To improve the loading time, go to Options > Preferences > Plugins > Oxygen Content Fusion Connector and enable the Upload only resources that are directly referenced in the files to be reviewed. option.

When this option is enabled, only resources such as other topics and images that are directly referenced from the files to review are uploaded. This may lead to a smaller set of files, but there are some limitations:

Images Not Being Displayed in Documents Within Review Tasks

For review tasks that are created in the Tasks Manager in Oxygen XML Editor/Author, if images are not displayed in the visual editor (in the browser interface), it is mostly likely because the source DITA map was not uploaded in the review task. The DITA map must be specified in the DITA Context section for the image references to be uploaded.

Review Task Details Not Available

If you see this message in the Oxygen Content Fusion interface when clicking on the name of a task, it means that the task has been deleted from the server by the Content Author.

Oxygen XML Editor/Author Needs More Memory to Upload the Task

If uploading a task fails and the error message suggests that a possible cause may be that Oxygen XML Editor/Author needs more memory to upload the task, see How to Increase the Amount of Available Memory.

Get Changes Warning: The following resource was not created

When merging changes, if this message appears in the Results panel at the bottom of Oxygen XML Editor/Author, it means that a new external resource was detected in the list of changed files. You can try to create it manually with the content displayed in the Get Changes dialog box.

Get Changes Warning: The original folder of the uploaded files cannot be found

When merging changes, if this message appears, it means that the original file(s) could not be found in the location where they were at the time the task was uploaded to the Content Fusion server. If you know the new location of the folder where the original file(s) now reside, click Choose directory and select that folder (in this case, the merge tool will perform a three-way comparison between the original file(s), your changes after the task was uploaded, and the incoming changes). You can also choose an empty folder and the incoming files will be saved to that folder (in this case, the merge tool will only offer the option of accepting the incoming changes without any comparison).

Reviewers see Variable Key References Expanded as an Unexpected Value

Since the Oxygen XML Web Author editor that the Reviewers use to proofread and make changes to uploaded files is a lightweight version of Oxygen XML Editor/Author, it does not have all of the features that the Content Author has access to. For example, in Oxygen XML Editor/Author, the Content Author can select which value they want to see expanded for defined variable key references. In the Oxygen XML Web Author editor, the Reviewers will only see the first value that is detected.

Reviewers See Missing Images and Links Pointing to Missing Files

If a Content Author uploads a file that contains references to images or links to other files, but only the main file was added to the review task, the images and linked files are considered missing and cannot be rendered in the visual editor. This issue can be solved by adding the image files and linked files to the review task along with the main file so that they are all uploaded to the Oxygen Content Fusion server.

For DITA files, you can specify a Context DITA Map when creating the review task and all the files referenced from the DITA map will be included in the review task and uploaded to the server.

Sign-up Email Confirmation Messages Not Being Received

When signing up for Oxygen Content Fusion, if you do not receive the confirmation emails, there is an option in the server configuration to disable these emails. The server administrator can go to the Content Fusion Adminstration Page and in the Mail tab, select the Disable e-mail address validation on sign-up option.

Information Presented by the Content Fusion Connector Add-on is Not Up to Date

Updated SSL Certificates but the Server Still Shows Browser Warning

Task Repository Fails to Export When Creating a Backup

Failed to download tasks repository: 17 java.io.IOException: HTTP error code: 500

<html><body><h1>Whitelabel Error Page</h1><p>This application has no explicit mapping
for/error, so you are seeing this as a fallback.</p><div id='created'>
Mon Aug 26 05:38:22 GMT 2024</div><div>There was an unexpected error 
(type=Internal Server Error, status=500).</div></body></html>

This could be caused when the jgit tool cannot open repositories during the backup process because some .git/refs/heads have been moved to the .git/packed-refs file, causing repository corruption.

If you encounter this issue, an administrator can do the following:

1. Stop Content Fusion.
2. Create a backup of the /fusion/data/temp/tasks directory.
3. Execute the following script with the sudo bash patch-packed-refs.sh command:

   #!/bin/bash
   
   # Directory containing git repositories
   REPO_DIR="/fusion/data/temp/tasks"
   
   # Loop through each repository in the directory
   for repo in "$REPO_DIR"/repo-*/; do
       # Define the path to the packed-refs file
       PACKED_REFS_FILE="$repo.git/packed-refs"
       
       # Check if the packed-refs file exists
       if [ -f "$PACKED_REFS_FILE" ]; then
           # Read the packed-refs file line by line
           while IFS=" " read -r sha ref; do
               # Skip lines that start with #
               if [[ $sha == "#"* ]]; then
                   continue
               fi
   
               # Create the path to the reference file
               REF_PATH="$repo.git/$ref"
               REF_DIR=$(dirname "$REF_PATH")
   
               # Create the directories if they don't exist
               mkdir -p "$REF_DIR"
   
               # Write the sha1 to the reference file
               echo "$sha" > "$REF_PATH"
   
               echo "Unpacked $ref in $repo"
           done < "$PACKED_REFS_FILE"
           
           echo Removing packed-refs
           rm "$repo".git/packed-refs
       else
           echo "No packed-refs file found in $repo"
       fi
   done

4. Start Content Fusion.
5. Let it run for a few minutes and check the logs for stack-traces.
6. Stop Content Fusion.
7. Create a Content Fusion Backup.