When a user logs in, he gets:
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'briarcli_d8.honeypot_user' doesn't exist: SELECT COUNT(*) AS expression FROM (SELECT 1 AS expression FROM {honeypot_user} hu WHERE (uid = :db_condition_placeholder_0) AND (timestamp > :db_condition_placeholder_1) AND (hostname = :db_condition_placeholder_2)) subquery; Array ( [:db_condition_placeholder_0] => 0 [:db_condition_placeholder_1] => 1544033106 [:db_condition_placeholder_2] => 73.121.26.183 ) in honeypot_get_time_limit() (line 294 of /home/briarcli/public_html/bcc/modules/contrib/honeypot/honeypot.module).

I also keep getting
Warning: in_array() expects parameter 2 to be array, null given in honeypot_form_alter() (line 64 of modules/contrib/honeypot/honeypot.module).
How do I fix these?

Comments

tjtj created an issue. See original summary.

SECarr’s picture

SECarr commented

This sounds like a database table did not get created during installation of the module. I'd recommend uninstalling the module, and reinstalling it.

geerlingguy’s picture

geerlingguy commented
Category: Bug report » Support request
Priority: Major » Normal
Status: Active » Closed (cannot reproduce)

@tjtj - Across thousands of sites (and dozens that I maintain in Drupal 8), I have not encountered any of the errors you seem to be encountering.

I'm closing this issue for now (see also, #3018005: honeypot warning); please produce the exact steps you're following that leads to this condition.

Are you downloading the module from Drupal.org? Are you downloading with Composer? If so, what command are you using? Are you installing via the Drupal UI? Are you installing with Drush? Are you installing by changing settings in the database? Does this happen when you are installing Drupal from an existing configuration? What version of Drupal are you using? What version of Honeypot are you using? (Are you using the dev release or a tagged version?).

Basically, I have not seen anyone else have these issues, nor can I reproduce them on brand new Drupal sites in my test environments, and it's also working fine in the Drupal CI test environments... so I'm guessing something with the way you're installing the module is the issue, and we can resolve that... but only if you post exactly what you're doing.