Enabling the ask-a-question block takes over all pages on the site

Confirmed, I get this too.

This is the same issue: http://drupal.org/node/437408, but it was marked as fixed. (Should we re-open that one or keep this new one for the 2.0 release?)

Sorry, I just found this after having reopened http://drupal.org/node/437408 possibly that should be closed and point to here as a duplicate. I too can confirm this is a problem, not sure what the fix is.

Thanks,

Izzy

I am having the same issue here. Took my whole site down today. As this is a known issue which will down peoples sites without any known fix, I suggest that it is certainly reopened as an issue, but also that something is added to module download page. This is not something you expect of a final module release and should be taken very seriously.

Just noticed this as well, I enabled the "faq ask" block on all pages and it disabled the entire site. The block is calling this function at line 132:

/**
 * Get the ask question form.
 */
function faq_ask_page($tid = NULL) {
  drupal_goto('node/add/faq', 'ask=true');
}

which redirects the page to the "add a faq form" rather than actually displaying a form. Of course, if you're using this block on every page it will by definition cause an infinite loop as it will try and display the block again. I commented the line out for now just to get back in and disable the module, I couldn't see an easier way to get the form to output in the code.

As an alternative, I'm looking into using the "form block" and "form filter" module as discussed here to replicate the same functionality.

http://drupal.org/node/179393

Just uplaoded a patch to fix this and implement a ask a question block here: #421818: Faq_Ask block redirects
/Sten

Assume this is OK with the 6.x-2.x-dev version running.

[#421818 and #437408 are related to this issue]

Nope, it's not OK. :) Version 2.0 needs to become version 2.0.1 or even a 2.1 asap, because I just deployed this 'stable' module on a mega-company's intranet and it effectively killed all navigation on the site when an employee enabled that block to see what it would do. I'll tell you what it does. Every page on the site becomes the ask-a-question form.

That form *does* look good and all, but I'm sure this is not the desired behavior. ;)

Can I help you in releasing an updated version? Oh, and I'm going to open another somewhat related issue in regards to the module not removing it's block(s) from the block table upon un-installation. That step alone would at least allow admins to recover their site by disabling and un-installing the faq_ask module. For reference, I'll link to that ticket ticket from here.

There is a version 6.x-2.1-beta1 available. Would you be able to try that one out and give me feedback on how that works?

Oh, sure. I didn't see it on the project's download section, and drush didn't tell me it was there either, so I've already upgraded this site to 2.x-dev. Live dangerously, I say! ;)

I'm deploying through the dev and test servers now, to see how things do. Will report back.

[edit 20100614] Correction. I just got told not to deploy a -dev version. :( I'll switch to the 2.1-beta1 and let you know how *that* one goes! :)

[edit 20100614] Hah! The beta1 tag and the -dev version turned out to be identical, save for the .info file, (of course). I'm not gonna tell anyone what I've deployed. Buah hahh hha! (ok, ok, I'll commit the beta1 .info file. :)

Fixing my reversion of the issue's version number; back to 2.1-beta1.

Changing the title.

Confirming this issue for the recommended release "faq_ask-6.x-2.0".

Upgrading to "faq_ask-6.x-2.1-beta2" runs the following updates:

 faq_ask module
 6101 - description not available
 ...
 CREATE TABLE {faq_ask_notify} (                                                                                                                             [success]
 `nid` INT unsigned NOT NULL,
 `email` VARCHAR(128) NOT NULL,
 PRIMARY KEY (nid, email),
 INDEX nid (nid, email)
 ) /*!40100 DEFAULT CHARACTER SET UTF8 */

This fixes the issue for me.

Changing version & status accordingly.

Thanks & greetings, -asb

Confirming the RTBC status of this issue. The "world-domination" tendencies of the submit-a-question block have been neutered.

Good. Time to make a proper 2.1 version...

/Sten