Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Module brakes everything.
1) after unpacking module was ENABLED already - why? Ambiguous module name?
2) translation table was NOT created, leading to WSODs whenever I open ANY node
3) reinstalling through Devel interface makes nothing, since it possibly reinstalles system module
Comment | File | Size | Author |
---|---|---|---|
#7 | translation-1021434-6.patch | 806 bytes | plach |
#4 | translation-1021434-4.patch | 674 bytes | plach |
Comments
Comment #1
plachTranslation 2 is meant to replace the core Translation module so if it is already enabled you will find it already enabled and the
translation
table won't be created. We need an update function taking care of this.Comment #2
OnkelTem CreditAttribution: OnkelTem commentedUntil then, we should simply DISABLE core translation.module?
Comment #3
plachI'm afraid you'll need to remove the
translation
record from thesystem
table and then enable Translation 2 again.Comment #4
plachHere is an update function creating the schema and enabling the translation_node module (the contrib version of core translation).
Comment #5
plachbetter title
Comment #6
sunLooks good to me. However, this update must not run on existing sites.
I'd suggest a simple
if (db_table_exists('translation'))
wrapper.Comment #7
plachHere it is.
Comment #8
sunReady to fly, IMHO. :)
Comment #9
plachCommitted to HEAD. Thanks!
A new development snapshot will be available in 12 hours.