Enable the acquia_contenthub_publisher module through the Drupal admin interface. When activating the acquia_contenthub_publisher module on an existing Drupal site functioning as a Content Hub subscriber, only the content exclusive to that Drupal site can be published. However, the content that is imported from other publishers cannot be re-exported. Each entity is limited to having only one publisher.
By default, Content Hub automatically adds content changes to the export queue when the content is:
Created or updated
Flagged as published
Draft or unpublished content is not automatically enqueued for export. However, it can be exported if:
The entity is a dependency of a published entity.
It has at least one revision for translation of a published entity.
The Content Moderation module and the Workflows module are used with translations.
Automatic addition of translated content
Draft or unpublished translations are automatically added to the export queue when the default language or parent entity is published. For instance, if the English translation of a node is published and the Japanese translation is still a draft, the draft is also exported.
Manual export mode
Note
The manual export mode is available in Content Hub 3.5.0 and later.
With the manual export mode, you can control when to add content to export queue. For example, if you require multiple approvals before the syndication begins, you can use the manual export mode and prevent content changes from being automatically added to the export queue.
To enable the manual export mode:
Go to Administration > Configuration > Acquia Content Hub.
Select the Export tab.
In the Export Control fieldset, enable the Enable manual export mode checkbox.
Click Save Export Settings.
After the manual export mode is enabled, content changes are not automatically added to the export queue.
To manually enqueue content entities to the export queue:
Go to Administration > Content > Acquia Content Hub Export Tracker.
(Optional) Filter the view by title, UUID, entity type, or status.
Add entities to the export queue:
To add a single row, click the Add to export queue button on the row.
To add multiple rows, select the checkboxes for the required rows, select the Add to export queue option from the Action dropdown, and then click Apply to selected items.
Note
Some entities cannot be added to the export queue directly. They are only exported when their parent entities are exported. The Content Hub Export Tracker view cannot override this behavior. For more information, see Eligible and ineligible entities.
Processing the export queue
The export queue is processed in the following ways:
To process the export queue asynchronously, Acquia recommends you to configure scheduled jobs. Additionally, you can set up the scheduled jobs to run on dedicated cron servers if your Drupal Cloud subscription provides such servers.
Purging the export queue
To clear the export queue on a publisher site:
Go to Administration > Configuration > Web services > Acquia Content Hub.
Click Export tab.
When the queue has items, locate Purge existing queues within the Run Export Queue section.
Click Purge to empty the export queue.
Excluding entities from export
The publisher exports all content by default. However, there might be a necessity to exclude specific types of content from export due to security concerns or other reasons. For more information, refer to Excluding entities from export.
Viewing completed exports using the Publisher’s Dashboard
To view completed exports using the Publisher’s Dashboard:
Navigate to the Publisher’s Dashboard interface.
Click Content.
Review the content on the Content page.
The page displays the available content entities within the Content Hub service.
Exporting content from a Content Hub publisher
Use the following checklist to export content from a publisher:
Enable the acquia_contenthub_publisher module through the Drupal admin interface. When activating the acquia_contenthub_publisher module on an existing Drupal site functioning as a Content Hub subscriber, only the content exclusive to that Drupal site can be published. However, the content that is imported from other publishers cannot be re-exported. Each entity is limited to having only one publisher.
By default, Content Hub automatically adds content changes to the export queue when the content is:
Created or updated
Flagged as published
Draft or unpublished content is not automatically enqueued for export. However, it can be exported if:
The entity is a dependency of a published entity.
It has at least one revision for translation of a published entity.
The Content Moderation module and the Workflows module are used with translations.
Automatic addition of translated content
Draft or unpublished translations are automatically added to the export queue when the default language or parent entity is published. For instance, if the English translation of a node is published and the Japanese translation is still a draft, the draft is also exported.
Manual export mode
Note
The manual export mode is available in Content Hub 3.5.0 and later.
With the manual export mode, you can control when to add content to export queue. For example, if you require multiple approvals before the syndication begins, you can use the manual export mode and prevent content changes from being automatically added to the export queue.
To enable the manual export mode:
Go to Administration > Configuration > Acquia Content Hub.
Select the Export tab.
In the Export Control fieldset, enable the Enable manual export mode checkbox.
Click Save Export Settings.
After the manual export mode is enabled, content changes are not automatically added to the export queue.
To manually enqueue content entities to the export queue:
Go to Administration > Content > Acquia Content Hub Export Tracker.
(Optional) Filter the view by title, UUID, entity type, or status.
Add entities to the export queue:
To add a single row, click the Add to export queue button on the row.
To add multiple rows, select the checkboxes for the required rows, select the Add to export queue option from the Action dropdown, and then click Apply to selected items.
Note
Some entities cannot be added to the export queue directly. They are only exported when their parent entities are exported. The Content Hub Export Tracker view cannot override this behavior. For more information, see Eligible and ineligible entities.
Processing the export queue
The export queue is processed in the following ways:
To process the export queue asynchronously, Acquia recommends you to configure scheduled jobs. Additionally, you can set up the scheduled jobs to run on dedicated cron servers if your Drupal Cloud subscription provides such servers.
Purging the export queue
To clear the export queue on a publisher site:
Go to Administration > Configuration > Web services > Acquia Content Hub.
Click Export tab.
When the queue has items, locate Purge existing queues within the Run Export Queue section.
Click Purge to empty the export queue.
Excluding entities from export
The publisher exports all content by default. However, there might be a necessity to exclude specific types of content from export due to security concerns or other reasons. For more information, refer to Excluding entities from export.
Viewing completed exports using the Publisher’s Dashboard
To view completed exports using the Publisher’s Dashboard:
Navigate to the Publisher’s Dashboard interface.
Click Content.
Review the content on the Content page.
The page displays the available content entities within the Content Hub service.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Content Hub