The publishing options module allows you to create your own custom options. It creates a three tables to work off of and link nodes to their respective promotion options.
Once the module is installed you can go to `/admin/config/content/publishing-options` so you can add, edit or delete options and link them to the respective content types the user wants to make them available for. You can also do this when creating a content type in `/admin/structure/types` and choosing promotion options for the content type being created or edited.
You can also go to `/admin/people/permissions#module-publishing_options` and select user roles that have permissions to use the functionality.
Drupal comes default with "Promoted to front page" and "Sticky at top of lists". The Publishing options module allows you to create your own custom options. It integrates with the Views module and has plugins for field, filter and contextual filter.
Originally, I made this module because the Custom Publishing options module on Drupal.org was not updated to work with D8. Recently, I went through and updated my module to work with D9 as well. I would like to resubmit for security approval from Drupal because I was informed in issue https://www.drupal.org/project/pub_options/issues/3067093#comment-13805427 of the need for it with regards to D9.
I hope this time around it passes security. Please let me know if there is anything I can do to help. I would love for this module to be fully vetted by Drupal.org.
Similar Modules:
https://www.drupal.org/project/pub_options
git clone --branch '8.x-1.2' https://git.drupalcode.org/project/pub_options.git
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | Screenshot 2021-12-02 093838.png | 19.08 KB | geocalleo |
| #4 | Screenshot 2021-11-30 092020.png | 12.98 KB | geocalleo |
Comments
Comment #2
geocalleo commentedAdded module details
Comment #3
avpadernoThank you for applying!
The master branch isn't used in Drupal.org projects and needs to be removed. The other branches have wrong names (which are for tags) and need to be removed too. A correct branch name is 8.x-1.x, or 1.0.x, or 1.x. Before deleting branches, a new branch needs to be created and made the default one.
Comment #4
geocalleo commented@apaderno, apologies about that and thank you for the speedy reply! I had the branch available. I've switched the branch to the 8.x-1.2. Added a screenshot for confirmation on my end.
One question, to be sure and to be safe, so I delete the master branch completely or am I able to leave it on there as long as I have the 8.x-1.2 branch set?
Comment #5
geocalleo commentedUpdating git instructions with new branch.
Comment #6
avpaderno@geocalleo None of the branches shown in that screenshot have a correct name, and they need to be removed. A correct branch name is 8.x-1.x, 1.0.x, or 1.x. The x isn't meant to be a placeholder for a number; it's the string that must appear in the branch name. Differently, it would be a tag name.
Yes, the master branch should be removed.
Comment #7
geocalleo commented@apaderno, I am so sorry! I completely misunderstood. I have now corrected the issue. I added branch '8.x-1.x' and removed master and all other branches. The one thing I am not able to delete is the tags but from what I understand, that just tracks the releases of the module.
I've included a screenshot again.
And again, thank you so much for the help.
Comment #8
geocalleo commentedSwitching status to "needs review" based on instructions in https://www.drupal.org/node/539608#s-application-workflow.
Comment #9
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Comment #10
geocalleo commentedGreat news! Thank you! I will go over the documentation you posted and also jump in and help out with the review process as well. Also, it's no problem at all regarding the time frame. Thank you for your time in helping get this module reviewed.
Thanks again and happy holidays!