Introduction

The Cloudpress integration works seamlessly for the most part, but there are a few issues you need to be aware of when using Cloudpress or evaluating whether Cloudpress will work for you. This document discusses these known issues and how to mitigate them.

Restoring a Webflow backup breaks the Cloudpress integration

Description

When you configure a Webflow connection in Cloudpress, you specify the CMS Collection to which Cloudpress exports content. To keep track of this Collection, Cloudpress stores the unique ID of that Collection as reported by Webflow (hereafter referred to as the Collection ID).

When you export a document to that Webflow Collection, Cloudpress stores the unique ID for the Collection item it creates (hereafter referred to as the Item ID). Whenever you re-export a document, Cloudpress updates the Collection item with the Item ID previously stored.

If you ever restore a Webflow site from a backup, these Collection IDs and Item IDs will change - effectively breaking our Webflow integration.

If you try and export content after restoring from a backup, you will see the following error in your export logs:

An unexpected error occurred while processing the job. “Resource wasn’t found”

Error when exporting from Webflow

You can fix this error as described in the mitigation section below.

Since the Item IDs also change after restoring a Webflow backup, whenever you re-export a previously exported document, Cloudpress will no longer be able to find the originally exported item in your CMS collection to update it. It will therefore create a new item, resulting in duplicate items.

For more information, refer to the following items from the Webflow website:

Mitigation

The best mitigation is not to restore your Webflow site from a backup. However, if you do restore a backup, you must do the following:

  1. Reconfigure your Webflow connection by going to the Content Model tab on the Connection detail page, and selecting the correct values for the Webflow site, CMS Collection, and Body field.
  2. If you re-export previously exported documents, you will end up with duplicate items in your CMS collection. Delete the previously exported item and use the newly exported item from this point forward.

Editing rich text fields may break some formatting

Description

If you add items like tables or embeds to a document, Cloudpress will export those items correctly to Webflow. However, if you edit the rich text field manually, the formatting of these items may break, resulting in wrongly formatted text.

To demonstrate this is action, here is a sample table as defined in a Notion document.

A table in a Notion document

When this document is exported to Webflow, the table will be added to the rich text field.

The exported table in the Notion designer

The table does not appear correctly in the Webflow rich text editor, but if you publish the page, the table will be displayed correctly.

The exported table on the published site

However, if you make any changes to the rich text field, the table display will be messed up:

The table is messed up after editing the rich text field

The reason this happens is due to a limitation with the Webflow API that we use to export content. It does not allow us to correctly mark special blocks of code where you will normally use the HTML Embed Code Editor when you add these items manually.

Mitigation

You must not edit the rich text field to update the content created by Cloudpress. Instead, make changes to the original document and re-export it to Webflow.