mysql query can not see db_prefix of table "signup". I suggest a simple correction: it should be "{signup}".
It seems to work here. Sorry for a possible mess when operating here, since new around, and also moderately new with Drupal.
Kauko

CommentFileSizeAuthor
#1 1020758-1.signup-table-prefix.patch947 bytesdww

Comments

dww’s picture

dww
we/he/they
commented
Title: Ends up in an error on line 643 in signup.module » Missing table prefix in query on line 643 of signup.module
Version: 6.x-1.0 » 6.x-2.x-dev
Component: User interface » Database
Assigned: kaukoheikkila » Unassigned
Status: Active » Patch (to be ported)
StatusFileSize
new 1020758-1.signup-table-prefix.patch947 bytes

This was introduced via #856604: Make event signups visible on user registration form. I committed the attached patch to DRUPAL-6--1 and HEAD. So, it'll be fixed in 6.x-1.1, or you can grab the latest code from CVS, or you can apply this patch.

For future reference, the issue tags feature needs better documentation and help text (and frankly, should be hidden more by default). But, here's some of the idea:
#917880: Write a handbook page about how issue tags are intended to be used

Bumping this over to the D6--2 branch for Joachim...

jpcwebb’s picture

jpcwebb commented

This bug seems to have reappeared in v1.0 after updating from RC6...

dww’s picture

dww
we/he/they
commented

@jpcwebb: Did you read comment #1?

"So, it'll be fixed in 6.x-1.1, or you can grab the latest code from CVS, or you can apply this patch."

It didn't "reappear". It was a new bug introduced between RC6 and 6.x-1.0.

jpcwebb’s picture

jpcwebb commented

my bad, sorry

bewhy’s picture

bewhy commented
Version: 6.x-2.x-dev » 6.x-1.0
Status: Patch (to be ported) » Reviewed & tested by the community

This patch fixed my problem (thanks a bunch). I changed the status from "to be ported" to "reviewed & tested by the Community" but I'm not sure if it needed to be reviewed by two people or not. I'm throwing caution to the wind.

I'm seeing that ddw bumped this to the 6.x-2 version for joachim, but since there's no 6.x-2 version on the project page, i'm moving this back to 6.x-1 because that's where the bug is. I'd suggest creating another issue for the 6.x-2 version if need be (i.e. Joachim didn't get to this)

dww’s picture

dww
we/he/they
commented
Version: 6.x-1.0 » 6.x-2.x-dev
Status: Reviewed & tested by the community » Patch (to be ported)

@BeWhy: Please read the comments I've made here. The bug fix is committed to the 6.x-1.x branch and will be available in 6.x-1.1 (whenever that's released). Meanwhile, if/when joachim wants to start maintaining the 6.x-2.x branch, this bug needs to be fixed there. If you're having trouble with 6.x-1.0, use the 6.x-1.x-dev release or deploy directly from the 6.x-1.x branch of Git. Or wait for 6.x-1.1.

Cheers,
-Derek