In the process of importing content into a subscriber site, the entity exported from the publisher site is recreated on the subscriber site as a local copy. Content Hub imports all the dependencies of the entity, such as taxonomy terms, file attachments, or paragraphs.
The following table lists the methods for importing content into a subscriber site:
| Method | Description |
|---|---|
| Manual syndication | Select the specific entities to import into a subscriber site using Publisher’s Dashboard. Manual syndication provides flexibility for publishers and subscribers to directly control the content imported to a site. |
| Automatic syndication with filters | Create saved filters that automatically syndicate content based on criteria such as taxonomy term, entity type, or bundle. The filters are assigned to specific subscriber sites, and those sites import new entities that match the criteria when they are exported to Content Hub. |
When a subscriber connects to the Content Hub service, they need to import content. The subscriber can import content either by manual syndication or by updating the saved filters to attach a new subscriber.
The following process automatically updates the previously imported content:
Manual or automatic syndication is only used to establish the initial relationship between an entity and a subscriber.
To configure your Drupal site as a subscriber:
acquia_contenthub_subscriber module through the Drupal admin interface.The following are the ways to process the import queue:
To clear the import queue on a subscriber site:
To process the import 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 process the import queue manually, Acquia recommends you to use Drush. Acquia provides the ach-import Drush command for processing the queue.
Important:
Using Drush instead of the Drupal UI avoids the risk of PHP timeouts when working with large datasets.
To process the subscriber import queue, run the following command:
drush acquia:contenthub-import-queue-run --uri=https://site_uriFor information about the command options, see acquia:contenthub-import-queue-run.
To manually process the import queue using the Drupal UI:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
To process the import 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 process the import queue manually, Acquia recommends you to use Drush. Acquia provides the ach-import Drush command for processing the queue.
Important:
Using Drush instead of the Drupal UI avoids the risk of PHP timeouts when working with large datasets.
To process the subscriber import queue, run the following command:
drush acquia:contenthub-import-queue-run --uri=https://site_uriFor information about the command options, see acquia:contenthub-import-queue-run.
To manually process the import queue using the Drupal UI:
If this content did not answer your questions, try searching or contacting our support team for further assistance.