Yesterday I ran comfort update from version 3.15.6+190108 to 3.15.7+190124. Today some unusual behavior was identified on that installation, though all is working properly on another installation in the same environment that had been updated to 3.15.7+190124 several days before.

1. When a new survey is created (Create a new survey > enter survey name > Save), the save button goes inactive but no action follows. The page just sits there and the new survey isn't created. However, the copy survey action still works as normal.
2. When a question is attempted to be edited (Structure > select question > Edit), instead of Display, Logic, Other, and Statistics loading on the bottom right, the entire page seems to load again in that same area (screenshot attached). There is a momentary pause, and then the load continues in a loop.

Any recommendations on how to sort things back out on this installation?

Just tested on Firefox and Chromium with 3.15.7/github : seems OK.

About 2 : you are the second one to report this issue : can you report the issue at mantis ?

And can you check if Global settings/general/Clear assets fix the issue ?

Release 3.15.7+ was released at two times with one fix different.

On Jan 22, 2019 with the wrong description "Release 3.15.6+190108".
Then again on Jan 24, 2019 with the correct description Release 3.15.7+190124.

3.15.7 was released on 22. Jan.
3.15.7 with one commit more was released on 24. Jan.



When everybody is comparing installations based on the version string there might is a difference.

Clearing the asset cache did indeed fixed both issues. Thanks! (Please relay this to the other user that reported 2.)

FYI, clearing the asset cache also led to:
* 504 Gateway Time-out. The server didn't respond in time.
* And the number in parenthesis after "Clear assets cache:" increased from (1) to (2).

That was actually my first gut instinct to try, but I cleared the asset cache on a test installation (which did not have these issues) first just because I had not used it before. But at the time I had hesitated to run it on the production server after the timeout and the increase in number.

What does the number mean that is next to "Clear asset cache"?

The number i the number you click on Clear asset cache.

Strangely : this must be automatically resetted when update a version

About 504 : yes it take time to redo all assets, but it take time one time