Closed (cannot reproduce)
Project:
Drupal core
Version:
8.0.x-dev
Component:
content_translation.module
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Nov 2012 at 07:34 UTC
Updated:
20 May 2015 at 23:28 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
yesct commentedThis 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.
Comment #2
-enzo- commentedI just reproduce this error, please give me few minutes to write down the steps by step to reproduce the error
Comment #3
-enzo- commentedHow 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
Enable translation for entity with data
2. If your entity is empty create some content to add a translation.
3. Disable the entity translation
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
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.
Comment #4
-enzo- commentedComment #5
-enzo- commentedComment #6
yesct commented@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.]
Comment #7
plachI 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.
Comment #8
gábor hojtsyComment #8.0
gábor hojtsyUpdated issue summary. Added new remaining tasks
Comment #9
jhedstromThis was bumped to 'Major' a year after being marked 'postponed'. Is this still an issue?
Comment #10
jhedstromAs per #7, I don't think this is an 8.x issue anymore.
Comment #11
plachDefinitely not :)