Needs work
Project:
Messaging
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
11 Jan 2012 at 17:04 UTC
Updated:
16 Jun 2015 at 11:47 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
digibrill commentedAnother error on running update.php
Failed: DatabaseSchemaObjectExistsException: Table messaging_simple already exists. in DatabaseSchema->createTable() (line 652 of C:\wamp\www\includes\database\schema.inc).
Comment #2
jlea9378 commentedI just saw the first error you mentioned when trying to upgrade from Messaging 6.x-2.4
to Messaging 7.x-1.0-alpha2+1-dev (2012-Mar-04).
Comment #3
digibrill commentedI am not running it any longer.
Comment #4
valthebaldAttached patch solves the issue
Comment #5
danepowell commentedConfirmed, #4 fixes this error.
Comment #6
rsbecker commentedI hate to reopen this, but #4 doesn't fix the problem after migrating from D6 because there does not appear to be a language field in the messaging_store table. When I deleted that field from the fix it worked. It is possible some D6 versions of messaging had the field, I guess.
Comment #7
mermentau commentedI found the same problem as #6 with the language field as I too am upgrading from Drupal 6. In addition in my code I found that in my version 6 code for the module the messaging_store table had the first field named mqid where the 7 version of the module needs mgid for the field in the messaging_simple table.
Comment #8
www.ePortfel.com commentedI confirm above problems with installing on Drupal 7.26.
To install the module I added language column to messaging_store as fifth column of definition:
I also replaced all 'mgid' references in module to be 'mqid'.
Then it installed successfully, however I am afraid to activate and use so unreliable version.
Comment #9
damienmckennaComment #10
damienmckennaClarifying that this only affects upgrading a site from D6, it won't affect a site that was never upgraded from D6 and never had the module installed before.