Closed (fixed)
Project:
Privatemsg
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 Sep 2008 at 11:17 UTC
Updated:
21 Oct 2008 at 10:13 UTC
Hi, I've installed privatemsg for Drupal 6, but get the following errors, and was wondering if it's a known issue or something that needs looking at in future developments.
Inbox page error;
user warning: Invalid use of group function query: SELECT MAX(pmi.mid) as id, pmi.thread_id, pm.subject, pmi.author, pmi.timestamp, MAX(pmi.new) as new FROM pm_message pm INNER JOIN pm_index pmi ON pm.mid = pmi.mid WHERE (pmi.recipient = 5) GROUP BY pmi.thread_id ORDER BY pmi.new desc, MAX(pmi.mid) DESC in /home/store/drupal6/modules/privatemsg/privatemsg.module on line 248.
sent items error
Can anyone shed any light on the problems here?
Thanks in advance for any help
Comments
Comment #1
VaZso commentedI think you should try to uninstall privatemsg first, then install this new version (if you have installed it before).
Anyway, it works for me on Drupal 6.
The only problem that prevents me using it is that I don't know how to set up the system to notify the user of new messages.
Does anybody know how to do it?
Edit: If you have messages in the database, I'm not sure it is a good idea to uninstall it...
Comment #2
mrtoner commented@briggsl: Uninstall and reinstall. I'm not seeing this error with HEAD, but if you installed it over an existing version you could see this. Remember, HEAD is not even close to ready for prime time, so the db schema is likely to change -- with no upgrade path.
See http://drupal.org/node/303485
@VaZso: We broke the notification on login a few weeks ago. Look for that to be fixed shortly. BTW, HEAD is not even close... :-)
Comment #3
VaZso commentedOk, thank you for the answers.
Maybe the best time to start working with privatemsg for D6 is the time when the first beta or rc come, because of the database.
I hope you will release it soon. ;-)
Anyway, I'm not sure if I will use the dev version or not.
Thanks your answer again.
Comment #4
naheemsays commentedprobably a little late, but afaik, there was not schema change. All that would be needed is to clear the cache.
Comment #5
udvranto commentedsubscribing.
Comment #6
naheemsays commentedheh, subscribing to the wrong issue! This one is (now) "fixed" (per comment 4) and there is no simple issue tracking development. Many issues with many patches. Come join us.
Comment #7
naheemsays commentedComment #8
briggsl commentedJust thought I'd add that we got this fixed, wasn't anything to do with the development snapshot and more to do with our PHP installation.
Few bugs, but all-in-all, good build so far. Thanks a bunch
Comment #9
prematurebaby commentedPrivatemsg is only for Drupal 5.
Comment #10
bneel commentedHow is going the port to drupal6.x-3.x ?
Ben, curious and excited to use this module with drupal6