I'm getting a v strange error having installed beauty tips as part of a feature:
Table .beautytips_manager doesn't exist query: SELECT * FROM beautytips_manager in beautytips_manager.module on line 391.
(NB I have replaced the actual site name with in the error message.
I'm installing the three BT modules as part of a feature with settings exported to the database via strongarm. For some reason when I install the custom feature, the beautytips_manager table is not created in the database.
I'm going to try stripping the site back to bare bones and install from there to see whether I can track this through. I'll post more if I find anything.
Cheers,
Crom
Comments
Comment #1
Crom commentedJust in case anyone runs into the same error, what I think is happening is that calendar_multiday (which I am activating from within the same feature as I'm activating beautytips from) is knackering the feature install which means that beautytips never gets properly installed. What also happens is that this problem with the way I was doing it is that you can never install beautytips manager - I tried uninstalling and re-installing etc.
The way to do it is to add calendar_multiday in it's own separate features if you want or just activate it manually. This is a known problem with the module (6.x-2.4), see: http://drupal.org/node/999708
Cheers,
Crom
Comment #2
kleinmp commentedComment #3
Crom commentedApologies kleinmp,
This bug still stands and disregard my explanation in #1. Additionally my original report was a symptom of the underlying problem rather than the problem itself. The problem arises when installing the beautytips manager module under windows and occurs because default values are set within the schema. See here for a better explanation of the issue: http://bugs.mysql.com/bug.php?id=25520
For a similar bug see here: http://drupal.org/node/143881
If you remove the default values for 'content' and 'pages' within the schema function the module installs correctly under windows.
Sorry, no patch but here is the adjusted function from beautytips_manager.install
Cheers,
Crom
Comment #4
kleinmp commentedIt looks like this is the same issue as #195169: NOT NULL fields need default value. MySQL running in strict mode will not take a default value for text fields.
The solution they used was to not set a default value in the table definition and to ensure that the value of that field was always set to '' if empty. So, that will have to be done with this module.
Comment #5
kleinmp commentedComment #6
drewish commentedThe 7.x-2.x branch had this fixed as part of #1060970: Update beautytips manager to use Drupal 7. Fixing the title to make it clearer.
Comment #7
kleinmp commentedFixed this in the 6.x-2.x-dev with this commit.