COU-584 - Transfering unpublished content will leave the node in the external index

Created by Mikkel Holck Madsen 15 Jun 2017, 10:06:09 Updated by Claus Jensen 15 Jun 2017, 10:50:43

Subtask of: COU-521

Heres the scenario:

Some content has been synced between the two environments. i.e. from staging to live. If for some reason the content on staging gets unpublished, and then transfered to the live environment. It will update the caches and the document state in the backoffice. Unfortunatley it doesnt get around to updating the Lucene indexes. This means that if your code is dependent on the indexes to be up to date, it will show wrong results, as the indexes will contain items that has actually been unpublished.

When deploying Courier should look at the indexes, and remove it form the index, if the item has been unpublished.

Comments

Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty:

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version: 3.1.3

Sprint: Sprint 61

Story Points:

Cycle: 2