Hi,

I recently installed userpoints and userpoint contributed modules into Drupal 5.7

When I run the update I got this error:

user warning: Unknown column 'upt.event' in 'where clause' query: SELECT DISTINCT(up.uid) FROM userpoints up INNER JOIN userpoints_txn upt USING(uid) WHERE upt.event <> 'expire' AND up.points > 0 AND upt.time_stamp < 1203356571 in /home/newmill/public_html/includes/database.mysql.inc on line 172.

Can someone help ?

Thanks in advance.

Hanly

Comments

jredding’s picture

jredding commented

It looks like 2 things

1) If you upgraded did you run update.php? The DB don't appear to be created correct, you could uninstall and reinstall to recreate the table structure ( you must uninstall not simply disable).

or

2) Did you install userpoints contributed module version 2 with userpoints version 3? these are not compatible. This error *seems* like it would be coming from the userpoints_expire contributed module and not from userpoints itself. userpoints_expire is NOT compatible with userpoints version 3.

Also this is a support request not a bug report.

shooommmm’s picture

shooommmm commented

Hi jredding,

Thanks for your quick reply. I think userpoints and userpoints contributed module are only compatible with the latest releases and similar version i.e. Userpoints contributed module 5.x-3.x-dev is compatible with Userpoints 5.x-3.x-dev.

I hope this will resolve the Db issue.

Cheers.

Hanly

jredding’s picture

jredding commented
Category: bug » support

umm. ya that's what I said as well as it being listed on both the project's frontpages. Use 3 with 3, 2 with 2 and don't mix them.

Good Luck.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Closed (won't fix)

Sorry for pinging the participants.

Now that Drupal 7 is out, there is no support for Drupal 5 and the
corresponding modules anymore. Therefore, I'm closing all old issues
which are still open.

I suggest you upgrade to Drupal 6 or 7 and figure out if you're feature
is still needed or the bug still exists and open a new issue in that
case.