-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
2.1.1 doesn't save workflow #65
Comments
Hi Daniel! Which Plone version, and does it behave this way on one of the shipped workflows?
|
can confirm with Plone 5.1.5 |
Hi Kim, it's plone 5.1.4.
I will need to check on shipped workflow later, unless @agitator can confirm.
Cheers,
Daniel
…On 15 February 2019 04:14:09 GMT, "T. Kim Nguyen" ***@***.***> wrote:
Hi Daniel! Which Plone version, and does it behave this way on one of
the shipped workflows?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#65 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Hey Kim, Ta, |
Ok thanks for checking! I will eventually find the time to take a stab at this and the 5.1 compatibility issue but I can’t promise when – sorry, crunched for other work
|
I'm testing with Plone 5.1.5 and Workflow Manager 2.1.1. I cloned the simple publication workflow. I edited the Pending Review state:
Both changes seem to be saved and persist. |
Hi Kim, thanks for persisting with this. I've checked and it seems to error more with Firefox not Chromium for me. I did reproduce it on a plain Plone site just now. When working with Firefox the Save button doesn't go red after you hit "OK", so I didn't realise that was required until using this with Chromium. I think there's 2 issues here
I think there's JS / CSS issues, I've noticed at least:
HTH! |
Not sure what I'm doing wrong, but if I do this:
=> then my changes in 3) are not there!
The text was updated successfully, but these errors were encountered: