Jump to:
| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | node system |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
| Issue tags: | SettingsAPI |
Issue Summary
I was going through #518434: "Create New Revision" the default drupal behavior for nodes and other similar issues and realized that there is no point in arguing over what should be the default, but rather offer the means to define defaults per setup. This way everyone would be happy. So, how about simply providing a way for people to:
a) mass-view and mass-change these settings (revisions, published etc)
b) define the default they like for their new content types.
Part a. above is perfectly being taken care of by Content type overview (should be in core IMHO). It saves people of having to edit each content type one-by-one + adds an overview of content types' settings. Let me know if there's a better/alternative way or module.
Now, for part b. I have not found a solid solution yet. Again, let me know if I missed something or point me to any existing issue filed for this.
Comments
#1
...also let me know if you think that it is best I should file separate issues for my requests above ;)
#2
The Util module has a sub-module to do these changes as well. It's not complete yet, but the bulk of the function is there and you're welcome to submit a patch to fix it.
#3
There you have it. Nancy is talking about the Util project and its 'Type Defaults' feature. This would/will cover part b. mentioned in #0 (wish I could edit issues descriptions to add that info there). I say 'would cover' because #596236: Type default doesn't do anything still stands.
@Nancy: I wish I could 'talk drupal' so I can help out but I'm not fluent (yet).
Also, here's the issue concerning the future of the module in D7: #584548: Initial port of Util module to D7
So, we (kinda) have alternatives to do this, but lets leave the issue open so these features get in core someday.
#4
Subscribing and tagging (as a potential piece of a SettingsAPI solution).
#5
Marking this as a dupe of #923736: Add generic mechanism for "update all existing" when settings are changed. which is a more generic representation of this problem across core.