Follow up for #1831530: Entity translation UI in core (part 2)

Problem/Motivation

disabling translation of fields (with content) stalls and does not disable

Proposed resolution

none yet.

Remaining tasks

User interface changes

no changes needed.

API changes

no api changes needed.

Comments

yesct’s picture

This worked during most of the original et-ui issue, and so it might not actually be a bug.
Check to see if it's reproducible.
See if there is a test for disabling.

-enzo-’s picture

Assigned: Unassigned » -enzo-

I just reproduce this error, please give me few minutes to write down the steps by step to reproduce the error

-enzo-’s picture

How to reproduce the error:

1. Create any entity field and enable translation. the user interface will looks different if the entiry is empty or not

Enable translation for empty entity

how_to_enable_translation_field_for_empty_field.png

Enable translation for entity with data

how_to_enable_translation_field_for_field_with_data.png

2. If your entity is empty create some content to add a translation.

3. Disable the entity translation

how_to_disable_translation_for_entity_with_data.png

After click in disable translation you will get a batch process, but the process get stucked at 25% as you can see in the following images

batch_error_trying_to_disable_translation_entity.png

If you stop the process and check the translations, all translations are gone. So if you try again to disable the translation the process now is completed without any problems.

-enzo-’s picture

Assigned: -enzo- » Unassigned
-enzo-’s picture

Issue tags: -Novice +Needs tests
yesct’s picture

@plach I'm hoping you can take a look at this one.
It feels like something where you might look at it and think of where the problem might be coming from. Versus someone debugging for a long time to find it. What do you think? [edit: If you have a hunch, post some hints and we can find someone to look in the direction you suggest.]

plach’s picture

Status: Active » Postponed (maintainer needs more info)

I think this may be related to the EFQv2 conversion: basically all the code in translation_entity.admin.inc was converted from a single query looking for all the field values belonging to any entity_type to separate queries, one for each entity type which the field being converted is attached to. The logic is a bit trickier now, but this shouldn't hard to fix once we have the steps to reproduce it reliably. I could not yet.

I'd like to avoid spending too much time on this since, as I said many times, all the code in translation_entity.admin.inc is going to be blown away once Field API and Entity Field API are finally merged.

gábor hojtsy’s picture

Component: translation_entity.module » content_translation.module
Priority: Normal » Major
gábor hojtsy’s picture

Issue summary: View changes

Updated issue summary. Added new remaining tasks

jhedstrom’s picture

Issue summary: View changes

This was bumped to 'Major' a year after being marked 'postponed'. Is this still an issue?

jhedstrom’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

As per #7, I don't think this is an 8.x issue anymore.

plach’s picture

Definitely not :)