Needs work
Project:
Translation Overview
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Dec 2008 at 23:34 UTC
Updated:
22 Mar 2016 at 15:39 UTC
Jump to comment: Most recent
Comments
Comment #1
drewish commenteddefinitely an improvement but it seems like we should also remove columns for languages that were removed when the module was disabled.
Comment #2
eMPee584 commentednot my problem: i don't disable languages ;)
Comment #3
drewish commentedi can sympathize i don't disable translation_overview ;)
Comment #4
toemaz commentedMy use case: I often enable/disable languages so the patch is for sure a good start, but as Drewish mentioned, not complete yet.
Comment #5
gagarine commentedSame problem on 7.x. This is a problem when we try to enable this module with feature.
Comment #6
drtrueblue commentedFor the sake of clarity, I want to be sure I understand the problem. Apologies for any redundancy.
In the event a language is added when translation overview is not enabled, and the module is later enabled, there is likely to be a conflict. Is that correct?
If so, can someone kindly confirm if the above patch applies to 7.x-2.x-dev?
If so, are there any plans to develop a patch for when a language is removed?
Lastly, it seems like the safest approach is to keep translation overview enabled whenever adding or deleting languages. Is that correct?
Thank you kindly.
Comment #7
JimDeLaHunt commentedI encountered the same problem with a Drupal 7.x (about 7.11) site from 2013, which I upgraded to 7.26 just now. I added a language, and Translation Overview did not add a corresponding column to the
translation_overview_prioritytable. This led to PDO Exception errors when visiting the Translation Overview page, and when adding Article content.The workaround of disabling, uninstalling, reinstalling, and reenabling Translation Overview worked for me.
In the introduction of this project's page, there is a recommendation that Drupal 7 users switch to Translation Management Tool instead. That module will be carried forward to Drupal 8, this one will not, apparently.
Comment #8
stefan.r commentedIf anyone wants to fix this, feel free to post a patch and I will look at it!