Write test that Config Entites created via API are created in Site Default language

Created on 26 November 2013, over 11 years ago
Updated 25 June 2025, about 1 month ago

Updated: Comment #0

Problem/Motivation

at #1966436: Default *content* entity languages are not set for entities created with the API β†’ we found out that there are some issues with default language assignment to content entities when created via the API.
Just to be sure we should also have some tests which make sure that config entities are created in the default language of the website when created via the API

Proposed resolution

- Write Test

Remaining tasks

- Write Test

User interface changes

None

API changes

None

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

language system

Created by

πŸ‡¨πŸ‡­Switzerland schnitzel

Live updates comments and jobs are added and updated live.
  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024