Comments on: Drupal’s “Promote to Front Page” option is a bit borked

By: Jason

Jason — Tue, 30 Nov 1999 00:00:00 +0000

I’m not sure how this is going to come through. If you want to change the node.module the change is below and starts on line #1302. I’m not sure how familar with the code you are.

// Add the admin-specific parts. if (user_access('administer nodes')) { $output .= '

';

    $author = form_textfield(t('Authored by'), 'name', $edit->name, 20, 60);

    $author .= form_textfield(t('Authored on'), 'date', $edit->date, 20, 25, NULL, NULL, TRUE);

    $output .= '';

    $output .= form_group(t('Authoring information'), $author);

    $output .= "
\n";

    $output .= "

\n";

  }

    $output .= '';

    $node_options = variable_get('node_options_'. $edit->type, array('status', 'promote'));

    $options .= form_checkbox(t('Published'), 'status', 1, isset($edit->status) ? $edit->status : in_array('status', $node_options));

    $options .= form_checkbox(t('In moderation queue'), 'moderate', 1, isset($edit->moderate) ? $edit->moderate : in_array('moderate', $node_options));

    $options .= form_checkbox(t('Promoted to front page'), 'promote', 1, isset($edit->promote) ? $edit->promote : in_array('promote', $node_options));

    $options .= form_checkbox(t('Sticky at top of lists'), 'sticky', 1, isset($edit->sticky) ? $edit->sticky : in_array('sticky', $node_options));

    $options .= form_checkbox(t('Create new revision'), 'revision', 1, isset($edit->revision) ? $edit->revision : in_array('revision', $node_options));

    $output .= '';

    $output .= form_group(t('Options'), $options);

    $output .= "
\n";

    $extras .= implode('
', node_invoke_nodeapi($edit, 'form admin'));

    $output .= $extras ? ''. $extras .'
' : '';

  //}

By: D'Arcy

D'Arcy — Tue, 30 Nov 1999 00:00:00 +0000

Jason, thanks for the ideas! I’ll give it a shot first thing in the AM. Both of the sites that need this are still running 4.6.5 - I didn’t want to push 4.7b3 into full production yet (although I did sneak it into a project, so I guess I will have a 4.7-series site in production - but that one doesn’t require this granularity).

Thanks again! Much appreciated!

- D’Arcy

By: Jason

Jason — Tue, 30 Nov 1999 00:00:00 +0000

Actually better yet, remove line #1672, #1686-#1694 removing the if statement completely. If you are working with something other than beta 3 let me know and I can forward the change.

By: Jason

Jason — Tue, 30 Nov 1999 00:00:00 +0000

I thought of two possible options since Drupal core does not afford you that granular of permissions.

The first is to create a taxonomy called “Promote to Front Page” and require it on new content with “unpublished” set as the default. Then you can change your front page in your config to a custom node.

The second requires you to edit the core node.module line #1683 in Drupal 4.7 beta 3. Just copy that line down somewhere between line #1688-1693 where the user section is defined. This does require you to maintain a fork though.

Maybe there are some other ways, but I couldn’t think of any off the top of my head.

By: Ignas

Ignas — Tue, 30 Nov 1999 00:00:00 +0000

OT: This page looks bad on Firefox browser. Some other pages looks ok, some not.

By: dnorman

dnorman — Tue, 30 Nov 1999 00:00:00 +0000

Ignas - yeah this page looks borked. Likely something in the first comment blew out the structure of the page. The comment is useful, though, so I’d rather live with a bit of noise for now. I’ll see if I can clean it up, but I think this is the only page affected, so it’s not a site-wide thing.

By: dnorman

dnorman — Tue, 30 Nov 1999 00:00:00 +0000

ah. easy fix. just encoded the brackets in the code in the first comment. better… Thanks for the heads-up!