Closed (fixed)
Project:
Translation Management Tool
Version:
8.x-1.x-dev
Component:
Source: Entity
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
8 Aug 2014 at 12:25 UTC
Updated:
9 Mar 2015 at 09:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
leksat commentedNow I'm 100% sure that this is a bug.
From the entity_translation documentation:
Comment #2
leksat commentedChanged priority to major.
Result:
Comment #3
leksat commentedThe patch filters out entities with LANGUAGE_NONE source language.
Comment #4
miro_dietikerFully agree with your description, this seems a severe bug.
Please consider: All bugs, especially such major ones, are required to provide test coverage.
:-)
Comment #5
leksat commentedAdded tests and an additional check in the TMGMTEntitySourcePluginController::getData() method.
Comment #8
berdirThanks, committed to 7.x-1.x.
Comment #9
miro_dietikerComment #10
sasanikolic commentedPorted to 8.x, fixed the link of the source entity and the source entities with undefined source language are not displayed anymore.
Comment #11
berdirLooks good.
There is one thing that I forgot, 8.x also has other special languages that we should exclude. Like LANGCODE_NOT_APPLICABLE. Instead of hardcoding it, I think we should compare it with the languageList() from the language manager, that's the same list as we're using in tmgmt_content_get_translatable_entities().
The at least the list test should then be extend to also include an entity with that language code.
Comment #12
sasanikolic commentedExcluded the entities with not applicable languages and made the test.
Comment #14
sasanikolic commentedComment #15
berdirYou still need to update this to use a @language placeholder.
Comment #16
sasanikolic commentedChanged the placeholders.
Comment #17
berdirYou don't need both conditions here, the first one is a subset of the second and also covered with that (because not specified is not in the list of languages).
Also, the %entity change in the first message was wrong.
Avoid changing existing code that is not really related to an issue. This will actually conflict with #2427153: Replace deprecated calls, but this needs an update anyway.
Comment #18
sasanikolic commentedComment #19
sasanikolic commentedNeeds review...
Comment #22
sasanikolic commentedComment #23
berdirCommitted.