Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I installed the module and got the following error in the admin conf page.
* user warning: Table 'XXXX.episodes_behavior' doesn't exist query: SELECT COUNT(DISTINCT filename) FROM episodes_behavior WHERE detected = 1237151342 in /usr/local/webapp/XXXX/sites/all/modules/episodes/episodes.admin.inc on line 127.
* user warning: Table 'XXXX.episodes_behavior' doesn't exist query: SELECT COUNT(DISTINCT module) FROM episodes_behavior WHERE detected = 1237151342 in /usr/local/webapp/XXXX/sites/all/modules/episodes/episodes.admin.inc on line 131.
I tried uninstalling and reinstalling, and the error persisted.
The table does exist, but perhaps lacked the proper permissions? I regranted full permissions to the db user without any change in the error.
GRANT ALL PRIVILEGES ON XXX.* TO 'XXX'@'%' IDENTIFIED BY 'XXX' WITH GRANT OPTION;
I think went into my mysql gui tool and explicitly gave select permissions to that table and the error persisted.
Drupal 6.10
MySQL database 5.0.32
PHP 5.2.0-8+etch13
Comments
Comment #1
wim leersEh … I'm somewhat puzzled by this. If the table exists, then why can't it write to it?
And I'm not sure how this could ever be caused by a module, which simply uses a normal install procedure (hook_schema() and drupal_install_schema() called from hook_install())? What if you install another database-enabled module?
Comment #2
ezraw commentedYeah, it's odd. I installed fivestar and votingapi just now without any problems, and had installed multiple modules successfully before installing Episodes. I'll try it again with a clean version of 6.10 and see what happens.
Comment #3
ezraw commentedI tried again on a pretty clean 6.9 install on the same server, and I get the same errors. I'll try to disable all the modules and see if that helps.
Comment #4
wim leersI've reinstalled Episodes plenty of times myself and it always worked. So I really have no idea… I tried it again just now (reinstall + run cron + visit admin/settings/episodes/behaviors) to be sure and again no problems.
Comment #5
wim leersAre you perhaps doing some multisite or db prefixing stuff? On-the-fly database switching? Or nothing fancy at all?
Comment #6
ezraw commentedI did a completely fresh download and install of core, and only added hierarchical select and episodes and it did install just fine (yay!), so it's not the server or your code.
I'll have a look at the query logs on the other environments and see if anything looks amiss. I don't think I had anything special, definately not a multi-site install or using prefixing.
Comment #7
ezraw commentedI wonder if this could be a false error. When I look at the episodes_behavior table on the site that gives the error, the table is populated with 44 rows.
Comment #8
wim leersGreat :)
I'll gladly welcome your feedback regarding anything except admin/settings/episodes. I know that that form is horrible in its current state. I'll only accept feedback on that if it's suggestions on how it should work.
Comment #9
wim leersThe d.o infrastructure messed up here …