Updated: Comment #N

Problem/Motivation

Steps to reproduce

  1. Install the standard profile without any languages
  2. Enabled content translation
  3. Add a new language
  4. Set the article content type to be translatable
  5. Create a new piece of article content
  6. Go to the field settings of the body field of the article content type
  7. Hit the "Enable field translation" link
  8. Confirm
  9. See the error message.

Proposed resolution

Remaining tasks

User interface changes

API changes

CommentFileSizeAuthor
#1 content_translation-2087975-1.patch1.9 KBdawehner
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Status: Active » Needs review
Issue tags: +Needs tests
FileSize
content_translation-2087975-1.patch1.9 KB

Something like this?

YesCT’s picture

YesCT CreditAttribution: YesCT commented
Issue tags: -Needs tests

might be related/dup to: #2019485: 500 Internal server error, during batch enable of translation from the content language settings page

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Status: Needs review » Reviewed & tested by the community

That is a duplicate of #2089853: TranslatableForm totally broken

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Status: Reviewed & tested by the community » Closed (duplicate)

ehem

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Issue summary: View changes

making the steps numbered