Aaron Carlino

The issue is in `CMSMain.EditForm.js` (line 397): ``` js $('.cms-edit-form.changed').entwine({ onmatch: function(e) { // Commenting these two lines out fixes it. this.find('button[name=action_save]').button('option', 'showingAlternate', true); this.find('button[name=action_publish]').button('option', 'showingAlternate', true); this._super(e); }, onunmatch:...

Yeah, the problem is the change detection is all handled by a thirdparty library. All the CMS implementation does is add `.changed` to the form, and the entwine handlers watch...

Yeah, the only thing that is going to change the behaviour in CMSMain is merging my PR from years ago that updates on keyup.

Ah, right. In the spirit of merging imperfect code, right? I'm still keen to polish it a bit, but let's just see how we get on with it as is..

Yeah, it's been a usability killer for as long as I can remember. Let's put an end to it. :)

Thanks. If this is a legit fix, please submit a PR!

I think this was resolved here: https://github.com/unclecheese/silverstripe-gridfield-betterbuttons/commit/b78f3c7449651ba2acefe4000f161e17384fcad3

Can you please try the new `setRedirectURL()` method in c364d1fbc11a0438551499e12f8f7412013225b6 ? Let me know how that works and I'll tag a release.

Hi, @g4b0, I've implemented an API change on the master branch that will allow you to do what you're looking for. ``` php

Yeah, I'm aware of this. Not an easy thing to solve, and unfortunately, it has huge impacts on usabilty. :(