After some initial feedback on my Save & Edit module for Drupal 6, I've decided to push forward with attempting to get support for the feature to be included in Drupal 7 as a core item. I've recently figured out an issue with a bug that was preventing me from feeling it was complete, and now with that done, I'm ready to push to get it accepted as a desired feature, and move forward with creating a patch that will put it in core.

How to help get this in D7 core...

Please visit drupal.org/node/500890 to show your support for the module, and post feedback related to getting it in core.

Here is the original post on drupal.org regarding the issue.

I would like to start off a "paper trail" of my efforts to get Save & Edit functionality in Drupal 7 core. This will be my first time proposing a feature or discussing a feature that I actually plan to implement myself, and provide patch(es) for, so keep that in mind.

Outline

I recently created the Save & Edit module for D6. This module adds some simple functionality to the node adding/editing interface. I have received some great feedback so far on the module, and now hate it when I come to a site where I can't Save & Edit to avoid losing any changes. The following features are what it currently does, and with the items I would likely need to trim out for a core patch marked through, and important core features bolded.

• Add a Save & Edit button to node add/edit forms of selected node types
• Customize button texts and weights
  • This, while nice would not be a part of core. It is easy enough to form_alter and change the weights and titles of buttons without having this as a built in feature. Makes sense to remove it for "trimming" the code down.
• Allow the ability to select preference for "Auto-Unpublishing" a node when the Save & Edit button is used.
  • This currently has 2 settings. (1 to ALWAYS auto-unpublish, and 1 to ONLY unpublish on new nodes)
  • I think only the setting for auto-unpublish on NEW nodes is actually valid. The other setting was there just in case, but doesn't seem to have a likely use case.
  • When this option is enabled, a new "Publish" button is added to the form as well helping a user quickly identify that the node is unpublished, and needs to be published in order to be visible. This can still be modified using the normal checkbox to publish or unpublish, but I felt this was needed for usability to quickly understand that a node is not "active"

Now with the features lined out that are current, and should IMHO go into core, what I need is the appropriate path to take in developing this. It is obvious that little "trim" features like this don't get some crazy configuration page under admin/settings, thus why features like custom titles and weights would be removed. It seems to me that with the minimal features that are likely valid for core, that the configuration options (enable/disable & auto-unpublish setting) should likely reside under the content type editing pages. Something that by default would be an enabled feature, but the ability for users to toggle at will.

Feedback

I guess now my next step is to see that this is a desired feature, that there is some community feedback that really thinks this really would be a good addition to core, and not just a feeling I have personally.

Please feel free to chime in with both feedback of if this should be in core or not and remain a contributed module AND a proper impelentation path that should be followed on exactly HOW the feature is integrated.

How to help get this in D7 core...

Please visit drupal.org/node/500890 to show your support for the module, and post feedback related to getting it in core.