not keeping defaults: for other publishing options

Hi marcus7777,

I made a quick test by using an authenticated user who can 'administer nodes',
and was able to promote to a node to the frontpage.

Could you give more details?
- user permissions
- step to reproduce the issue

thanks

I have this same issue..
When a default value is set for the workflow settings of a content type, those settings are not maintained when a user with publish permission publishes the node. For example, the Story content type on my site has the "Promote to front page" option selected under the defaults, so when published, that node should, by default, display on the front page. However, that setting does not stick. A user with administer nodes permissions must edit that node and click the checkbox for "promote to front page" on that node.

quick idea:
do not "unset" the following lines of code in hook_form_alter in file publishcontent.module:

    unset($form['options']['promote']);
    unset($form['options']['sticky']);
    unset($form['options']['revision']);

instead, pass those (along with whatever default value each of those are carrying) as "hidden" form elements (sorry, no time to code the workaround for now). this approach should resolve the issue for those who don't care about the note below.

WARNING:
if this route is taken, someone [ not your everyday Joe though ;-) ], can submit this form with changed default values from the clientside and it will be accepted on the server. meaning: the user with publish/unpublish ONLY perms can now change the "promote" & "sticky" & "revision" item values as well, even though s\he doesn't have the explicit permission to do so.

feel free to correct any wrong assumptions I may have made ... cheers

buzzman, you have the right idea.
the better solution is to set $form['options']['promote']['#access'] = FALSE;.
if this patch works for y'all i'll get it in right away.

sorry, a tweak based on #750634: Incompatibility with Publish Content Module

use this one instead.

Agree with #2. In our case, we need there to be an audit trail that records changes to the node, and we have create new revision checked by default for this purpose. No new revision means Publish/Unpublish operations are not captured.

this is into dev, along with respect for "revision" defaults to address david's concerns in comment #6 - will roll a new release soon.