Enabling throws DB errors

Why would the entries be there in the first place in a clean install of D7 and FAQ? I'll dig deeper based on what you said, but the names of the values having 'Test' in them gives me pause. Ah, such is dev.

Just on a hunch I removed the .test file from the files[] array in the .info file (commented it out) and it installed okay.

Permissions were able to be set. The first error I encountered was a WSOD related to the unanswered questions block, I forced a NULL return at the start of the block function to get past that on a temporay basis.

The next error I encounted was that the function drupal_goto() needs its query argument in an array, with each term being in an array as well. Here are my diffs so far (the original file is in the SAVE dir):

diff faq_ask.module SAVE/faq_ask.module 
181,182c181
< // JGB  drupal_goto('node/add/faq', 'ask=TRUE');
<   drupal_goto('node/add/faq', array('query' => array('ask'=>'TRUE')));
---
>   drupal_goto('node/add/faq', 'ask=TRUE');
204,205c203
< // JGB      drupal_goto("node/$node->nid/edit", 'ask=TRUE');
<         drupal_goto("node/$node->nid/edit", array('query' => array('ask'=>'TRUE')));
---
>       drupal_goto("node/$node->nid/edit", 'ask=TRUE');
1506,1508d1503
< // JGB Added this to prevent a WSOD when unanswered block is enabled.
<   return NULL;

When making custom changes to code like this I typically put my initials in a comment so I can quickly find my changes. Hope this helps. Will continue to try to track other errors, such as the WSOD when trying to preview or save a question from the FAQ Ask page. It seems to be connected to the form alteration.

I saw the categories displayed correctly, but I am encoutering a WSOD related to the alter_form_id_hook so far as I can tell. Also, the regular FAQ module add content page throws a WSOD with FAQ_Ask is enabled when trying to preview or submit a question and answer. The error is being thrown by the field module, but I am guessing it can be tracked back to the same issue that is throwing the FAQ_Ask error connected to forms.

Edit: Here is the error on the WSOD connected to previewing/saving in FAQ Ask:
Fatal error: Function name must be a string in /includes/form.inc on line 1390

Hee is the diff that resolves the WSOD when previewing/saving:

280,282c278,279
< // JGB This step is not needed as the value is ALREADY an array in D7
< // JGB   $temp_val = $form['#validate'];
< // JGB    $form['#validate'] = array($temp_val); // not needed
---
>     $temp_val = $form['#validate'];
>     $form['#validate'] = array($temp_val);

The problem came about because the value in $form['#validate'] is already an array if set, so no need to transform it again.

Now that I am past this I am getting a regular error message regarding fields, which seems to be the same one I get in FAQ with FAQ Ask enabled, so more fun and games.

Here is that message:

    * Warning: array_values() [function.array-values]: The argument should be an array in _field_filter_items() (line 494 of /modules/field/field.module).
    * Warning: Invalid argument supplied for foreach() in text_field_validate() (line 120 of /modules/field/modules/text/text.module).

Here is another bug that showed when I tried to unpublish a new question from the content admin screen:

Notice: Undefined property: stdClass::$revision in faq_update() (line 280 of /sites/all/modules/faq/faq.module).

To stenjo, GStegemann and future readers of these comments: Please forgive my somewhat ugly diffs and code postings. While I am no stranger to using Drupal or coding in other languages, I am new to PHP and Drupal code developing. You could say I'm old school. :)

That fatal error is corrected by the changes in my comment #7 above. The changes are made in faq_ask.module. There is actually a better way to do the logic, but I wanted to leave as much of the old structure intact to make finding it easier.

Bump because it looks like CiviCRM is going to have a working port to D7 in the next couple of months. The lack of a D7 version of CiviCRM has been a major show stopper for me on the political organization sites I run. But once that is in place, then the lack of other modules like this one will become a block point.

I presume D6 will be at end-of-life once D8 comes out, so there is pressure to move to D7 within 12 months or so. However, D6 is very robust and many of what I would call key modules are not working on D7 yet. I consider FAQ and FAQ_ask to be among those key modules.

I have gone about as far as I can on this for now given my time constraints. I believe the module maintainer has real-life circumstances to deal with as well. Can someone step up and finish the job of getting a stable, bug-free D7 version of FAQ and FAQ_ask in place so migrating to D7 is one step closer for many of us?

aagbsn: thanks, I'm not the most knowledgable on how the drupal ticket system works, I just try to make things work anyway I can. :)