Closed (fixed)
Project:
Frequently Asked Questions
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Sep 2009 at 14:53 UTC
Updated:
2 Dec 2011 at 22:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
stella commentedAdded to the latest dev version. It will only be set when the module is first installed.
Comment #2
arbel commentedthanks,
what do you mean when the module be first installed? so it will remain defaulted to promoted to front page unless someone changes it?
Comment #3
stella commentedYes, you can override this setting for all new faq nodes created at
admin/content/types/faq. So the faq module will now have that option disabled by default, but an administrator can override the default setting by editing the content type.Cheers,
Stella
Comment #4
arbel commentedoh, ok great. that's what I was looking for. Thank you!
Comment #6
stella commentedReleased in faq 6.x-1.9.
Comment #7
davidhk commentedHi, I recently installed the 6.x-1.12 module, and found the same problem - that by default new faq nodes have 'Promoted to front page' enabled.
By the time I noticed it, the first few faq nodes I'd created had gone out in the RSS feed and to email subscribers. Ouch!
I'd like to see it disabled by default.
Regards, David
PS Apart from this hiccup, it's a very useful module for me. Thank you!
Comment #8
izmeez commentedThat seems to be a common Drupal trait that whenever new content types are created they have default settings of "Published" and "Promoted to front page". I don't know if there is a settings page to change that. Otherwise, it would be helpful if the module changed this for the faq content type. Of course once the content type is edited and the setting changed it does stick.
Comment #9
Steven Brown commentedThis was a simple patch to change the variable being set in the faq.install. Variable was changed from 'node_type_faq' to 'node_options_faq'.
Comment #10
drakythe commentedPatch applied to dev branch and worked perfectly.
Comment #11
staris commentedReviewed and tested the patch successfully.
Comment #12
Steven Brown commentedThis patch has been committed to the 6.x-1.x-dev branch. http://drupalcode.org/project/faq.git/commit/b444edd
Comment #13
Steven Brown commented