Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX (1.3): Better maintenance of state for the save draft + publish buttons #183

Open
wants to merge 2 commits into
base: 1.3
Choose a base branch
from

Conversation

patricknelson
Copy link

@patricknelson patricknelson commented Nov 6, 2018

Addresses to important issues I've identified:

  1. Going in to edit a record will not reflect if it has a publishable version or not (33a6fcc)
  2. Changing a record doesn't dynamically update the two submit buttons at the bottom like it should (8d4991a)

Granted #​2 is just a revert of another commit (245caaf), however, this functionality is entirely consistent with other Version'ed objects, i.e. SiteTree. I acknowledge that maintaining this functionality (i.e. button state updating if the form is modified in any way), however I believe that should be classified as a separate bug that should instead be addressed in silverstripe-cms, given it is more broad and consistency and, more importantly, visual feedback on current state is more valuable (in my subjective opinion).

…utton in case draft isn't consistent with live version (ALSO the case if "record is deleted from stage", i.e. draft doesn't exist)
@patricknelson patricknelson changed the title Fixes 1.3 FIX: Better maintenance of state for the save draft + publish buttons Nov 6, 2018
@patricknelson patricknelson changed the title FIX: Better maintenance of state for the save draft + publish buttons FIX (1.3): Better maintenance of state for the save draft + publish buttons Nov 6, 2018
@patricknelson
Copy link
Author

Bump!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant