I recently installed the Sign-up module on a brand new 6.14 and got the following error when I visit /drupal/admin/settings/signup

user warning: Table 'creobellum.signup_log' doesn't exist query: SELECT COUNT(*) as total, status FROM signup_log WHERE nid = 0 GROUP BY status in /etc/drupal/all/modules/signup_status/modules/signup_status_limit/signup_status_limit.module on line 141.

I noticed, it also put the following error on the homepage:
user warning: Table 'creobellum.signup_log' doesn't exist query: SELECT COUNT(*) as total, status FROM signup_log WHERE nid = 50 GROUP BY status in /etc/drupal/all/modules/signup_status/modules/signup_status_limit/signup_status_limit.module on line 141.
user warning: Table 'creobellum.signup_log' doesn't exist query: SELECT COUNT(*) as total, status FROM signup_log WHERE nid = 49 GROUP BY status in /etc/drupal/all/modules/signup_status/modules/signup_status_limit/signup_status_limit.module on line 141.

It looks like the table creation didn't happen.

I've since turned off signup, but I'm happy to assist in bug finding if required.

Comments

kentr’s picture

kentr commented

Confirm this bug.

Looks like the table is actually there (I see it when I access the database), but the table prefix isn't being used so signup_status_limit can't find it.

@wolffy.au: debugging would be awesome. do you know where to start?

kentr’s picture

kentr commented
Status: Active » Needs review

Oops. This is actually a signup_status issue. Duplicate of #593068: Missing {braces} around table name on line 141 of signup_status_limit.module 6.x-1.x-dev.

dww’s picture

dww
we/he/they
commented
Title: signup_log table not created » signup_log table not properly prefixed in signup_status_limit
Project: Signup » Signup Status
Version: 6.x-1.0-rc6 » 6.x-1.x-dev
Component: Database » Signup status limit
Status: Needs review » Closed (duplicate)

#593068: Missing {braces} around table name on line 141 of signup_status_limit.module 6.x-1.x-dev

kentr’s picture

kentr commented
Title: signup_log table not properly prefixed in signup_status_limit » signup_log table not created
Project: Signup Status » Signup
Version: 6.x-1.x-dev » 6.x-1.0-rc6
Component: Signup status limit » Database
Status: Closed (duplicate) » Fixed
dww’s picture

dww
we/he/they
commented
Title: signup_log table not created » signup_log table not properly prefixed in signup_status_limit
Project: Signup » Signup Status
Version: 6.x-1.0-rc6 » 6.x-1.x-dev
Component: Database » Signup status limit
Status: Fixed » Closed (duplicate)

In spite of the cross posting, this is still a signup_status bug and still duplicate. ;)

kentr’s picture

kentr commented

Hmm... I didn't mean to override your change - don't even know how that happened... Perhaps I was in the middle of editing my comment when you posted yours.

dww’s picture

dww
we/he/they
commented

Yeah, that happens semi-regularly. It's called "cross-posting". Two people reply to an issue at the same time and sort of undo each other's changes to the meta data. No real harm done... ;)

Cheers,
-Derek