Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The way domain_admin_form_alter() replaces $form['options'] makes it impossible to edit the publishing options.
With "access published checkbox on domain" you can access the "Published" checkbox but "Promoted to front page" and "Sticky at top of lists" are always hidden and set to 0.
I need normal users to create content with the default setting taken from the content-type settings.
Solution (for me)
Permission:
1) access published checkbox on domain
2) access promote checkbox on domain
3) access sticky checkbox on domain
If an option (as checkbox) is not available the content-type default setting should be used.
I could have a go at this, but I'm not sure what you are planing for domain_admin_nodeapi()
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | domain_admin_872558_clean.patch | 4.27 KB | brt |
| #2 | domain_admin_872558.patch | 4.2 KB | brt |
Comments
Comment #1
nirbhasa commentedI would be very grateful if you did submit a patch, Im quite tied down right now. I cleaned up the nodeapi, so now it should be straightforward to extend the behaviour for both sticky and promote in domain_admin_nodeapi and domain_admin_formalter
Note that the published checkbox has the behaviour you are looking for, it passes the default values if the user doesnt have the permissions
Comment #2
brt commentedI've created a patch. Only bit of your domain_admin_nodeapi() code I don't get is where $default->status is set. Do we need it for a specific reason?
Comment #3
brt commentedI forgot to say the patch is against cvs HEAD.
I also cleaned up the formating of my code.
Comment #4
nirbhasa commentedCommitted, with minor cleanups. Thanks!
Im not sure why the $default->status was there (I wrote it a while ago) - lets leave it out for now and see how we get on.