- 🇨🇦Canada scor Toronto
Fixed with cb135b46dc858320ab2c08ed29815c3fe5f954fb
Automatically closed - issue fixed for 2 weeks with no activity.
The Acquia Lift module renders content and sends it over to the Content Hub via the acquia_contenthub_publisher module, however the Personalization service does not make any use of the entity dependencies: only the main entity CDF and its rendered CDF entities are used. Some user may want Personalization without syndicating all their content for ease and performance reasons.
Even when the "Push personalizing content only" is enabled, the export still happens via the native CH Drupal queue, we just don't wait for the queue to be run by cron/drush later, we run it right away. Because the entity being exported is placed into the queue in the form of (entity_type, UUID), by the time we kick off the queue processing in the subsequent request, we're losing the context of our acquia_lift_publisher scenario, and the processing is handled by the CH module with full dependency calculation, which is unnecessary for some users who have complex data structures.
To solve this problem I'd like to include some context in the queue item with a new optional parameter called "calculate_dependencies", and the dependency calculation is made conditional on that parameter defaulting to TRUE the way it works today OOTB.
Review patch.
none
New optional parameter called "calculate_dependencies" in queue data items.
New optional parameter called "calculate_dependencies" in queue data items.
Fixed
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Fixed with cb135b46dc858320ab2c08ed29815c3fe5f954fb
Automatically closed - issue fixed for 2 weeks with no activity.