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

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

plach’s picture

Translation 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.

OnkelTem’s picture

Until then, we should simply DISABLE core translation.module?

plach’s picture

I'm afraid you'll need to remove the translation record from the system table and then enable Translation 2 again.

plach’s picture

Status: Active » Needs review
FileSize
674 bytes

Here is an update function creating the schema and enabling the translation_node module (the contrib version of core translation).

plach’s picture

Title: `translation` table is never created upon installation » `translation` table is not created on upgrading from core translation

better title

sun’s picture

Priority: Critical » Major
Status: Needs review » Needs work

Looks good to me. However, this update must not run on existing sites.

I'd suggest a simple if (db_table_exists('translation')) wrapper.

plach’s picture

Status: Needs work » Needs review
FileSize
806 bytes

Here it is.

sun’s picture

Status: Needs review » Reviewed & tested by the community

Ready to fly, IMHO. :)

plach’s picture

Status: Reviewed & tested by the community » Fixed

Committed to HEAD. Thanks!

A new development snapshot will be available in 12 hours.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.