Algolia items get deleted when the "Deletion" field is empty

I have…

  • [x ] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • Regression (a behavior that stopped working in a new release)
  • [ x] Bug report
  • Performance issue
  • Documentation issue or request

Current behavior

When the “Deletion” field in an Algolia rule is not set, the item in the Algolia index still gets deleted.

Expected behavior

The item in the Algolia index should not be deleted unless I specify a condition in the “Deletion” field

Minimal reproduction of the problem

  1. Configure an Algolia rule so that an item gets created whenever you publish a new content item in Squidex Editorial UI
  2. Leave the “Deletion” field empty for the rule
  3. Create a new content item in Squidex and verify that it gets created in Algolia
  4. Delete the content item in Squidex - you will see that the item in Algolia gets deleted. The item in Algolia should not get deleted.

Environment

  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • [x ] Cloud version

Version: 7.0.0

Browser:

  • [x ] Chrome (desktop)
  • Chrome (Android)
  • Chrome (iOS)
  • Firefox
  • Safari (desktop)
  • Safari (iOS)
  • IE
  • Edge

Others:

I would say this has never been changed. Because initially this did not exist and there was a standard rule based on the event. And then a feature request has been added to add this condition as an extra feature, which obviously could not break the existing stuff.

Okay, so when would I use the “Deletion” field? Can you give me an example?

BTW, both ReviewDeleted and ReviewUnpublished delete the item from Algolia which is expected.

Only if you have some other cases, e.g. if you never want to delete something you could just return “false”.

Okay, good to know. Thanks! You can close this one now.