As shown in the screenshots, I ve set the defaults off on my content type. When I create a new node the defaults are not respected.

CommentFileSizeAuthor
#1 715800-fix-default-settings.patch7.55 KBneclimdul
print2.png19.24 KBdomidc
print1.png16.16 KBdomidc

Comments

neclimdul’s picture

neclimdul
He/Him
commented
Status: Active » Needs review
StatusFileSize
new 715800-fix-default-settings.patch7.55 KB

Defaults are kinda haphazardly ignored in quite a few places. This should fix things.

scott m. sanders’s picture

scott m. sanders commented

Subscribing: I can't review patch presently but do want this fixed.

jcnventura’s picture

jcnventura
Primary language English
commented
Status: Needs review » Fixed

It was working as designed.. Those were not default settings, but more of a type-wide configuration switch. I.e. if you disabled a setting in the type, it would disable that settings for all nodes of that type, regardless if of what you configured in that node.

That was done a long time ago, when I was a little less familiar with Drupal (and content types). I now admit it's confusing and against what Drupal normally does. I have extensively enhanced your patch so that those type-settings act as defaults only.

I've committed that fix to CVS. It should be in tomorrow's dev version.

João

neclimdul’s picture

neclimdul
He/Him
commented

Thanks! That explains why they appeared to work sort of inconsistently.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.