Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I also need it? Are you ok with it when I co-maintain or take over the project? Could you add me to CVS? I have an account. NEed it urgently for an upcoming project.
I updated CVS with a version that breaks the table update into two parts, one to drop the key and one to add it. If the drop fails, manually skip the 6001 schema version and apply the 6002 update when you're prompted to update the database. That should do it.
This is due to an old bug where the table schema was set to have a primary key, but the updates never made that change. So some installs have the key and some do not (doh!). I can't see a quick and easy way to check for a primary key at the moment, so this should work for now.
I'm looking into why the question nodes wouldn't show up now. I think it may have to with me capitalizing "Question" as a node type in this release (to be more Drupal-like). Though, the underlying type should still be "question" so it should take it.
To clarify, they are showing up for me on my live site (macgeekery.com) and I'm looking into situations where they might not show up. I have yet to run into it.
Hi , i still have the problem , the questions are not showing in admin/content/question , and also it sends me a warning after sending a question, i use Postgresql
* warning: pg_query(): Query failed: ERROR: column "admon" does not exist in /usr/share/drupal6/includes/database.pgsql.inc on line 138.
* user warning: query: INSERT INTO question_queue (questioner, quid, question) VALUES ("admon", 1, "test) in /usr/share/drupal6/modules/question/question.module on line 427.
I have not tested this module on PgSQL, nor do I really have the ability to. However, it appears to be complaining about a perfectly valid line of SQL. I'd verify that the table schema matches that defined in the install file; perhaps something didn't work in the upgrade for PgSQL.
Comments
Comment #1
AccessiveApps CreditAttribution: AccessiveApps commentedI also need it? Are you ok with it when I co-maintain or take over the project? Could you add me to CVS? I have an account. NEed it urgently for an upcoming project.
Thanks
Patrick Przybilla
Comment #2
codepoet CreditAttribution: codepoet commentedI'm only now to the point where there are enough other modules ported to 6 that I can move my sites over to it. I can look at porting it over soon.
Comment #3
codepoet CreditAttribution: codepoet commentedWorking on this now.
Comment #4
codepoet CreditAttribution: codepoet commentedA basic update to 6 is now in CVS; the next dev refresh should catch it. I'll cut a beta of it soon.
Comment #5
korayal CreditAttribution: korayal commentedI'm on the latest dev. When trying to update the database, I got this error;
Can't DROP 'PRIMARY'; check that column/key exists query: ALTER TABLE question_queue DROP PRIMARY KEY
The primary key is "qid" and it's set to auto_increment, Mysql doesn't drop the field before removing the auto_increment attribute.
Also after the update, my existing question pages are still empty. For example:
http://www.hecatomber.org/node/2050
Comment #6
codepoet CreditAttribution: codepoet commentedI updated CVS with a version that breaks the table update into two parts, one to drop the key and one to add it. If the drop fails, manually skip the 6001 schema version and apply the 6002 update when you're prompted to update the database. That should do it.
This is due to an old bug where the table schema was set to have a primary key, but the updates never made that change. So some installs have the key and some do not (doh!). I can't see a quick and easy way to check for a primary key at the moment, so this should work for now.
I'm looking into why the question nodes wouldn't show up now. I think it may have to with me capitalizing "Question" as a node type in this release (to be more Drupal-like). Though, the underlying type should still be "question" so it should take it.
Comment #7
codepoet CreditAttribution: codepoet commentedTo clarify, they are showing up for me on my live site (macgeekery.com) and I'm looking into situations where they might not show up. I have yet to run into it.
Comment #8
korayal CreditAttribution: korayal commentedAfter the last dev all looks OK :) Thanks.
Comment #9
darumaki CreditAttribution: darumaki commentedWhy not just use http://drupal.org/project/faq works great
Comment #10
virgil85 CreditAttribution: virgil85 commentedHi , i still have the problem , the questions are not showing in admin/content/question , and also it sends me a warning after sending a question, i use Postgresql
* warning: pg_query(): Query failed: ERROR: column "admon" does not exist in /usr/share/drupal6/includes/database.pgsql.inc on line 138.
* user warning: query: INSERT INTO question_queue (questioner, quid, question) VALUES ("admon", 1, "test) in /usr/share/drupal6/modules/question/question.module on line 427.
Comment #11
codepoet CreditAttribution: codepoet commentedI have not tested this module on PgSQL, nor do I really have the ability to. However, it appears to be complaining about a perfectly valid line of SQL. I'd verify that the table schema matches that defined in the install file; perhaps something didn't work in the upgrade for PgSQL.
Comment #12
tanoshimi CreditAttribution: tanoshimi commentedNo further information and error can't be recreated, so marking this as fixed.