This is related to issues like #1190 and #1475 and I think we kinda mentioned it a couple of times here and there. The point is that there is not a single-size-fits-all solution and we should provide site builders with the means to customize these options in order to fit their case.
#1475 is a meta-issue and it sorta focuses on the UI side of things. This issue here is about the underlying cogs that make things work though and it doesn't quite fit the UX spectrum (so not tagging as such)...
So, the idea is to:
- allow the default, out-of-the-box publishing options/flags to be renamed
- allow adding/removing publishing options
GitHub Issue #:
1742
Recent comments
Hi, Olafski, Thanks for your reply. Thank goodness we have the resources of Drupal 7 to look at when these questions arise -- questions new to me (yet another unknown part of Drupal /...
Color module aggressive search and replace custom css color values
Hi DonM, I guess there isn't an option for the color module to behave in another way, but there are workarounds: Don't use the color module, maybe even disable it, and use only...
Color module aggressive search and replace custom css color values
Thanks. I think, for me, the user-interface issue is that one uses (can only use) the "big" configure to add a first condition. And that made me think that I should use that same method to add...
Blocks (custom) not displaying in Harris sidebars with visibility condition set to more than one url path (node)