This seems to trip a lot of people up (http://drupal.org/node/458404).

They want to attach an image to something that's promoted, say a story node.
The story is promoted, obviously.
But the image is promoted too because images are set to be promoted by default.
Result: image appears twice on the front page and it looks weird.

Possible ways to fix this:
- image_attach warns on install that you should maybe set images to unpromoted by default.
- attached images never promoted
- attached images never promoted if their attaching image is promoted
- setting to never promote attached images
- setting to not promote attached images if their attaching node is promoted.

Discuss :)

CommentFileSizeAuthor
#1 image-HEAD.default-node-options.patch1.52 KBsun

Comments

sun’s picture

Title: don't promoted images attached to promoted nodes » Don't promote image nodes by default
Component: image_attach » image.module
Category: feature » task
Status: Active » Needs review
StatusFileSize
new1.52 KB
joachim’s picture

Well I was thinking something more selective than that...
Might you not sometimes want regular images promoted and attached ones not? I suppose in that case you can install a module that exposes the promote flag to regular users.

sun’s picture

I've closed down several other issues similar to the one you referenced in the original post. The real, underlying issue is rather a Drupal core issue: For module-provided content-types, the "Promote to front page" option is automatically enabled, which does not make sense for 99% of all module-provided content-types. (Webform being another popular candidate)

I've used Image module on countless Drupal sites, but did not enable "Promote to front page" on a single one. (always had to disable manually)

Also, these node options are the default only. People can a) override the option per-node or b) change the default setting in the content-type.

I'd propose to fix this issue here. And move this issue to Drupal core's queue afterwards to change the default for D7.

sun’s picture

Status: Needs review » Fixed

Committed without that content-type description change (since that string is user-facing and translated on many sites already).

Status: Fixed » Closed (fixed)

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