Updated: Comment #0

Problem/Motivation

If create content first, then turn on translation using the content language settings page admin/config/regional/content-language
during batch, get:


Updating translatability for the selected fields

An error has occurred.
Please continue to the error page

An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /drupal2/af/batch?render=overlay&id=3&op=do_nojs&op=do
StatusText: Internal Server Error
ResponseText: 

But only the first time, going back to the settings page and doing it again is fine.

Note:
@plach #1810386-52: Create workflow to setup multilingual for entity types, bundles and fields

Once all entities are migrated to the new Entity Field API, we are dropping the migration batch completely because then fields will always be stored

Maybe this is a postponed on the issue (a meta?) to migrate all entities to the new Entity Field API... #1818580: [Meta] Convert all entity types to the new Entity Field API

Proposed resolution

(description of the proposed solution, the rationale behind it, and workarounds for people who cannot use the patch)

Remaining tasks

Decide if we need to fix this now, or if it can wait.

User interface changes

No.

API changes

No.

Comments

plach’s picture

Proposed solution: wipe out all of this useless migration code ASAP :)

YesCT’s picture

Issue tags: -JavaScript, -Usability, -Accessibility, -aria

removing tags accidentally carried over from other issue.

YesCT’s picture

Status: Active » Postponed

I'll all for #1

does that make this..
postponed on #1818580: [Meta] Convert all entity types to the new Entity Field API?

or are there some other things too that will accomplish that?

YesCT’s picture

Gábor Hojtsy’s picture

Component: translation_entity.module » content_translation.module
YesCT’s picture

andypost’s picture

Status: Postponed » Closed (duplicate)