How do I not 'save and edit' EVERY time... [#789574]

Could someone tell me how I would do this. I have an audio upload form using save_edit, however...once redirected to the edit page I no longer want the button to be the save_edit but rather the normal save/submit button (I dont want both options).

To sum up.

1. On audio upload form -user hits save and edit- form redirects to edit page (to fill in the gaps, getid3 etc).
2. user is on the edit page, wants a save but instead of a save and edit form, as he/she wants to return to the..normal node view.

Hope that makes sense....

How do I do this?

Thanks

Comments

Comment #1

himerus commented 4 May 2010 at 17:25

Assigned:	Unassigned	» himerus
Category:	support	» feature

What you are actually thinking of isn't currently built into the module, but I DO like the sound of it....
Currently, you can simply disable the save & edit functionality on any node type, but not have it disable AFTER a usage of save & edit...

I am turning this to a feature request, and will consider how best to implement it...

What would need to be considered is this:

If you hit save & edit once... the node "should" (via options) be marked as unpublished for the moment...
This then enables the publish button, which is just a quick save that marks the node as published. This would still need to be present.
However, removing that save & edit button should not be an issue afterwards as after an initial save & edit which unpublished the new node into "draft" mode, any subsequent usage of the default save button would not change the published state, but would also not redirect back to the edit form. (this would be fine in your usage)

I think potentially adding an option (per node type) to disable the save & edit button after it is used should be okay. This would however have to flag each node type in the variables table further to show that we just want it there once (only on new node creation page, NOT on a node edit page (once a NID is present)

I like the idea, but might be a bit before I can get to it. If anyone would like to submit a patch quicker than I can implement, it would be appreciated!!

Comment #2

himerus commented 4 May 2010 at 17:27

Wait... one last thing to clarify your point...

If you just need them to return to the node page, they can use the publish button or the default save button. All this while the save & edit button is still present... the primary functionality there is just intercepting the redirect and returning to the edit page rather than the node, but the other options WILL still redirect to the node again.

Comment #3

katy24 commented 4 May 2010 at 19:18

Adding the option to disable the save and edit would be ideal.

Hopefully you can work on this because at the moment I'm having two buttons (Save & Edit, Save & Publish) but this is not ideal for the end user as it gives them an extra button to choose from, unnecessarily.

Thank you.

Comment #4

Ive commented 8 June 2010 at 13:16

It's possible to edit the "Text to use for default Save button: *" It would be great if it wat possible to disable the Save Button. For now I use the sign "-" in stead of "Save" so users kind of ignore the button. Giving the options:
"Save and edit" "-" "Preview" "Publish"