Posted by takpar on April 7, 2009 at 2:48pm
Jump to:
| Project: | Conference |
| Version: | 6.x-1.2-beta2 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | zyxware |
| Status: | needs review |
| Issue tags: | prefix, table, user warning |
Issue Summary
reason
it is not used prefixes in queries.
solution
open conference.module,
replace every line like:
SELECT decision FROM conference_decision
with:
SELECT decision FROM {conference_decision}
note:
i opened this, as a new issue to help people quickly fix unwanted warnings.
finally thanks the author.
Comments
#1
This has been corrected in the latest release let us know in case of pit falls
Regards
Zyxware
#2
I think this bug can be safely closed: the code looks correct on the latest release.
Just a small, small, small fix would be to remove the extra spaces on line 1479:
1479c1479< $sql = "SELECT count(*) FROM { conference } c, { node } n where c.pnid = n.nid and c.pvid = n.vid AND n.nid = %d";
---
> $sql = "SELECT count(*) FROM {conference} c, {node} n where c.pnid = n.nid and c.pvid = n.vid AND n.nid = %d";
Regards.
#3
I had these issues with beta2. I did #2 and got that to fix just fine. The table it told me didn't exist was druapl_content_type_conference_paper. I ended up going into the settings and clicking the button to make another default and deleted the one I had and everything was fine. As it turns out it was mad because I changed the machine-readable name so my table was changed to reflect that instead (conference_paper -> project). I assume that is not the intended functionality as you are able to select the node you want anyway (this just lets you change the human readable one). The only thing is that right now you can't have more than one type that is a conference paper that I'm aware of so it may not matter.
Either way I just thought that you may want to know...
Thanks, I really like your module!
-Matt