Exporting content in Acquia Content Hub

With a publisher connected to the service, you can begin exporting content. The process updates one or more of the nodes in your website and queues them for export to your subscribing websites.

  1. Sign in to your publishing website as an administrator.
  2. In the admin menu, navigate to Manage > Content.
  3. Select the check boxes next to all the content.
  4. Use the bulk update process to re-save the content.
  5. To see the number of enqueued items, go to Configuration > Web Services > Acquia ContentHub > Export. The content hasn’t yet exported to the Acquia Content Hub service, and won’t until there is a subscribing website.

You can also configure scheduled jobs that run at predefined intervals to process the export queues. For more information, see Configuring scheduled jobs for import and export.

Processing the queue

Acquia Content Hub requires Drush 9 or later.

Drush is the easiest and most reliable method to perform queued tasks. To process your publishing queue, use the following Drush command, replacing [$URL] with the domain name for your website.

drush queue:run acquia_contenthub_publish_export --uri=[$URL]

The command processes the export queue, calculates all necessary dependencies for your data, and sends the data to the Acquia Content Hub service. The --uri= parameter provides the canonical URL of your website, and is required to syndicate various types of data to your subscribing websites. Without a canonical URL, subscribing websites can’t find the canonical representation of items like files for import.

Exporting content with embedded entities

Users can export content with embedded entities by using the Entity Embed and URL Embed modules. The embedded entities can be, but aren’t limited to:

  • PDF files
  • External links
  • Images
  • Multimedia files

When exporting an entity, Acquia Content Hub checks the entity and all its dependencies. It compiles a list of required dependencies for the entity prior to exporting the entity to the Acquia Content Hub service. All dependencies must be accessible to the service to create the full dependency list.


If a user attempts to export content while the embedded entity is inaccessible, the import process will fail.

Publishers must ensure all embedded entities are available to Acquia Content Hub. The reasons an embedded entity may be inaccessible include:

  • Non-existing links
  • Rejected links, due to some rate limiting policies on the linked website
  • Private assets such as pdf files, images, audio, video

Exporting content with the API

Acquia Content Hub includes a Drupal Batch API page in the Drupal administrative interface to export content. Content must be queued as described. You can use Drush or visit the administrative interface to process the queue manually.

This user interface can be found in the Acquia Content Hub settings in Drupal, and is only recommended for testing purposes. Content with multiple levels of dependencies on other content shouldn’t be indexed from the user interface. Use the Drush command to perform indexing.

  1. Sign in to your publishing website as an administrator.
  2. Go to Configuration > Web Services > Acquia Content Hub > Export.
  3. Click Export Items.

A progress bar displays. When it is complete, the queue has exported.

Excluding data from the queue

By default, the publishing website exports all data. You must exclude certain types of data from export due to security concerns or other reasons. Excluding data from the queue isn’t supported in the Acquia Content Hub user interface; exclude data using the Acquia Content Hub API. See Excluding data from the export process.


The queueing process is one way in which Acquia Content Hub identifies data for export. The dependency calculation process identifies items which would normally not add to the export queue. Missing items are often indicative of potential architectural problems on the publishing website, and should be investigated.