album function "Promoted to front page" problem

I'm searching for a fix for this too

I did a little testing and think I found the solution. This is a patch against the current CVS version of the module and was tested on Drupal 4.6.0.

Will this work with the album in Drupal 4.6.1?(non cvs) In the file defaults I had set pictures to not be promoted to front page along with a few other options. The other options stuck just it stubborly ignored my unticking of promote to front page.

Didn't try this fix, but looking at the code it's most likely all you have to do is change the line
$node->promote = variable_get("node_promote_$node->type", 1);
to
$node->promote = variable_get("node_promote_$node->type", 0);
at album.module

Again, I didn't try it -- I uninstalled the module before trying this fix - great module, but no good until users can erase/edit their albums...

Hi,

I was looking for a new solution for my blog and stumbled over Drupal. I was glad to see that new modules, which make photoblogging easier, are existing.
Well, during my tests I encountered the same problem.

I create a new album, upload some images and despite the configuration in "administer -> content -> configure -> content types -> image -> configure", where "Published" and "Promoted to front page" are disabled, all images of the album I created are published there.

Also, I thought that a gallery is ONE page full with images. The module creates a new node/page for EVERY image.

An improvement would be that an album is just one page, when you create one, but the images should be still accessable to other nodes like now. And the amount of images you want to upload should be configurable (currently 15 seems to be the default).

My current test installation is Drupal 4.6.2 (fresh installation) plus the additional modules from the download page: image, album, filemanager, folksonomy (all marked as -4.6.0.tar.gz).

Changing:

$node->promote = variable_get("node_promote_$node->type", 1);

To

$node->promote = variable_get("node_promote_$node->type", 0);

Fixed the problem for me.

Thank you Carlos Miranda Levy.

Darrell

Given that this issue has not been updated in 10 years or more, I am closing this ticket as won't fix as the original associated project is no longer available. However, if anyone feels this represents an issue that is still being encountered in the current version of Drupal, please reopen and/or provide additional comments and the appropriate project reference.