When enableing the module, Drupal tries to update instead of install
d3x - September 30, 2006 - 19:19
| Project: | Privatemsg |
| Version: | 4.7.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
When enableing the Privatemsg module, Drupal does not create the database tables needed, but rather thinks they are there and tries to update them. I extracted the needed CREATE's from the privatemsg.install and made a privatemsg.mysql which works for me (no guarantee it will work for others, but if you don't have any prefix for your tables it probably will work by showing the tables into the database before enabling the module.
| Attachment | Size |
|---|---|
| privatemsg.mysql | 1.26 KB |
#1
can anyone reproduce this? why wouldn't privatemsg.install be used?
please post more detail (drupal/privatemsg/mysql/php versions, reproducible from new install?)
#2
I am able to reproduce this.
I have reproduced this three times : http://drupal.org/node/109206
The only way to re-install for a newbie is to :
- make a fresh Drupal install
- install the module in that separate installation the
- copy the 3 tables over to ....
- your target Drupal install (where you had disable and deleted the tables...)
#3
see my explanation in the node linked above.