`CTA` model is not translatable but it is being used as such

[jhonatan-lopes]

The CTA model does not inherit from TranslatableMixin and, thus, is not translatable and should not allow for localisation/translation:

class CTABase(models.Model):
    name = models.CharField(
        default="",
        max_length=100,
        help_text="Identify this component for other editors",
    )

    header = models.CharField(
        max_length=500,
        help_text="Heading that will display on page for this component",
        blank=True,
    )

    description = RichTextField(help_text="Body (richtext) of component", blank=True)

    newsletter = models.CharField(
        max_length=100,
        help_text="The (pre-existing) newsletter to sign up for",
        default="mozilla-foundation",
    )

    translatable_fields = [
        TranslatableField("name"),
        TranslatableField("header"),
        TranslatableField("description"),
        SynchronizedField("newsletter"),
    ]

    def __str__(self):
        return self.name

    class Meta:
        abstract = True

class CTA(CTABase):
    class Meta:
        ordering = ["-id"]
        verbose_name_plural = "CTA"

However, manual translations seem to have been introduced in production. There are several copies of CTA instances in multiple languages:

It is necessary to determine whether the CTA model is still relevant for this task, as there are several other CTA models.

Tasks:

• Audit CTA models to determine which ones are still relevant
• Deprecate ones that are not relevant anymore
• Migrate data from deprecated CTA models into new ones
• Remove old deprecated models from codebase

┆Issue is synchronized with this Jira Task

[data-sync-user]

➤ Simon Acosta Torres commented:

Daniel Miranda You currently have https://mozilla-hub.atlassian.net/browse/TP1-357 ( https://mozilla-hub.atlassian.net/browse/TP1-357|smart-link ) assigned. Per the link, it seems this ticket should fulfill that other work. Do you think that is still valid in a way that this should be the priority over the other ticket or is it separate work that needs to be evaluated differently?

[data-sync-user]

➤ Daniel Miranda commented:

Hi Simon Acosta Torres ! After giving both tickets a look, I believe that we should finish this one first and then work on 357.