fix: resolve issue when updating or adding content type in draft mode

[ratorik]

fix: resolve Meilisearch issue with draftAndPublish enabled

When updating or adding an item with draftAndPublish enabled, the item is removed from Meilisearch, and the following error occurs:

error: Meilisearch could not add entry with id: 9: Transaction query already complete

This issue is described in #997. The item should update correctly without errors when draftAndPublish is enabled.

Pull Request

Related issue

Fixes #997

What does this PR do?

• Resolves the issue where items with draftAndPublish enabled are removed from Meilisearch and cause transaction errors.
• Ensures that updates to items are processed correctly when draftAndPublish is enabled.

[Strift]

Hello @ratorik, thanks so much for your contribution. 🙌

Would it be possible to add a test for this addition, so we can avoid any regression in the future?
This would also serve as a way to document the expected behavior.

[ratorik]

Hey @Strift,

Thanks for your feedback! I'll look into adding a test for this to help prevent regressions. That said, as mentioned in the ticket by @daandegooijer, the best long-term solution might be to revamp the lifecycles and align with the Strapi documentation. Since this was just a quick fix, maybe it makes sense to address the broader issue instead? Let me know what you think!

[Strift]

Hi @ratorik,

I think it's better to submit this small fix first, and then work on the broader fix in a second step. Refactoring a bigger part of the codebase will make the review process more heavy. As a result, changes would get deployed more slowly.

So I'd recommend adding the tests for this PR and then working on the revamp.

If you have the bandwidth to work on it, a broader fix would be welcome. Just consider that it could take me and other contributors a longer time to review it.