Translations are unpublished and can't be changed

Created on 11 March 2025, about 1 month ago

Problem/Motivation

Translations are marked with status 0, and it can't be changed.

Steps to reproduce

Enable translation. Create a translation. The status is 0.

Proposed resolution

Allow published status to be changed on the edit form.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States oknate Greater New York City Area

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @oknate
  • Merge request !55Expose published field β†’ (Open) created by oknate
  • Pipeline finished with Success
    about 1 month ago
    Total: 418s
    #446102
  • πŸ‡ΊπŸ‡ΈUnited States oknate Greater New York City Area

    I have added a PR to expose the published field. Please review.

  • πŸ‡¬πŸ‡§United Kingdom scott_euser

    scott_euser β†’ changed the visibility of the branch 3512340-translations-are-unpublished to hidden.

  • πŸ‡¬πŸ‡§United Kingdom scott_euser

    scott_euser β†’ changed the visibility of the branch 2.0.x to hidden.

  • πŸ‡¬πŸ‡§United Kingdom scott_euser

    Thanks for the contribution! The most common use case (I believe) is global settings for things that appear on all pages, so having published checkbox everywhere isn't ideal as it complicates the user interface when it normally does not matter (but of course that default for translation is unpublished is proper bug).

    So we have a precedent for optionally showing/hiding things in the UI like this:

    So I think on top of your current MR we should ideally:

    1. Maintain the status quo of published being hidden - ie, update hook setting hide_published true
    2. Let people opt-in to managing published status - ie, new hide_published in SiteSettingsConfigForm
    3. Default to published for new translations if managing published status is disabled - I believe in SiteSettingEntity field status can be with ->setDefaultValue(TRUE)

    Thank you!

Production build 0.71.5 2024