Use the following checklist to export content from a publisher:
S.No. | Task |
|---|---|
1 | |
2 | Create or update content on your publisher using standard Drupal processes |
3 | |
4 |
To configure your Drupal site as a publisher:
Content Hubacquia_contenthub_publisher module through the Drupal admin interface.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:
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.
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:
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:
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.
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.
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.
To clear the export queue on a publisher site:
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.
To view completed exports using the Publisher’s Dashboard:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Use the following checklist to export content from a publisher:
S.No. | Task |
|---|---|
1 | |
2 | Create or update content on your publisher using standard Drupal processes |
3 | |
4 |
To configure your Drupal site as a publisher:
acquia_contenthub_publisher module through the Drupal admin interface.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:
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.
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:
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:
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.
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.
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.
To clear the export queue on a publisher site:
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.
To view completed exports using the Publisher’s Dashboard:
If this content did not answer your questions, try searching or contacting our support team for further assistance.