My idea is:
When updating a translated email via the API (e.g., using PATCH to change isPublished), the link to its parent translation should be preserved. Currently, this relationship is lost, breaking the multilingual structure.
User story
As an API user,
I want to preserve the relationship to the parent translation when saving or updating a translated email via the API,
So that translated emails remain correctly linked and manageable within Mautic’s multilingual content structure.
I think these groups of people would benefit from this idea:
- Developers using the Mautic API
- Teams managing multilingual campaigns
- Integrators automating content management via API
Why I think they would benefit from this idea:
Losing the translation relationship leads to confusion and broken workflows in multilingual setups. Keeping the link intact ensures that translated content remains part of the correct hierarchy, improving maintainability and consistency across languages.
Any code or resources to support this idea:
Here’s a minimal example that reproduces the issue:
curl --location --request PATCH 'https://aivie.ddev.site/index_dev.php/api/emails/1/edit' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic ***' \
--data '{
"isPublished": false
}'
This removes the parent translation relation from email 1 (a translated email), even though that metadata was not modified in the request.
Are you willing to work on this idea?:
Yes, I’m happy to contribute, test, or help spec this out with guidance.
