Hi all,

after updating my postgres-based system to the latest release of Drupal (7.20) and some other module updates (token, css_injector, biblio), I expected an "website encountered an unexpected error" case... I found that disabling (as I could not log in any more, by moving the module directory) the botcha module, I could get the site up again.

I could not see much useful information in the server log. Drupal´s log gives the error messages (sorry, in German here):

PDOException: SQLSTATE[42P01]: Undefined table: 7 FEHLER: Relation »botcha_points« existiert nicht LINE 3: botcha_points b ^: SELECT b.botcha_type AS botcha_type FROM {botcha_points} b WHERE (form_id = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => search_form ) in botcha_get_form_id_setting() (Zeile 69 von /var/www/drupal/7.x_sites/all/modules/botcha/botcha.inc).

I try a translation as such:

PDOException: SQLSTATE[42P01]: Undefined table: 7 ERROR: Relation »botcha_points« does not exist LINE 3: botcha_points b ^: SELECT b.botcha_type AS botcha_type FROM {botcha_points} b WHERE (form_id = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => search_form ) in botcha_get_form_id_setting() (Line 69 of /var/www/drupal/7.x_sites/all/modules/botcha/botcha.inc).

Any idea what is going wrong here?

Thank you, cheers,
Lars.

Comments

Nitty-Gritty’s picture

Nitty-Gritty commented

Hi,

Thanks, Lars, for the tip to move the botcha module directory in order to allow log in!

I also get the same error having updated Drupal to 7.20.

Error

The website encountered an unexpected error. Please try again later.
Error messagePDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'nzbc_db.botcha_points' doesn't exist: SELECT b.botcha_type AS botcha_type FROM {botcha_points} b WHERE (form_id = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => user_login ) in botcha_get_form_id_setting() (line 69 of /home/nzbc/public_html/sites/all/modules/botcha/botcha.inc).

permaculturegeek’s picture

permaculturegeek commented

I also had this problem when upgrading our site to 7.21 (and botcha from 1.4 to 1.5). It left the site in an error state (for anonymous users) for 48 hours, because everything looked fine while I was logged in as webmaster (thank goodness for persistent logins).

For me the fix was to upgrade to 3.2 (the project page does not explain this huge jump in version numbers or why 1.5 thinks it is up to date).
The uninstall link didn't work. I needed to delete the botcha folder from modules then expire the cache before I could upload the new version via the autoinstaller. In order to enable it without error I had to go in to MyPHPadmin (take a backup) then drop all the existing botcha tables. Fairly drastic, but it worked.

iva2k’s picture

iva2k commented
Version: 7.x-1.5 » 7.x-2.0
Category: bug » support
Status: Active » Fixed

7.x-2.x and 6.x-2.x code does not use {botcha_points} table, there is an update function that removes it when you run update.php. The only scenario I can think of is leaving old files from previous version when saving new module. This qualifies as installation error and needs to be cleaned by removing old files first, then unzipping the new module into a clean space.

Status: Fixed » Closed (fixed)

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