This is unexpected.
Can I ask, from what version to what version you updated, and if you have a backup of the working site?
If such backup exists, I would suggest to deploy it locally and confirm it works as expected on the outdated version.
Then, enable your working space to debug the website (for example, enable WP Debug in the install, to log errors)
Check that all is running smooth and is not showing errors.
If there are no errors, and all is running smooth, make sure to update WordPress in case it’s outdated, then Types to it’s the latest version by applying the file downloaded from here.
Don’t update thru the installer or plugin > update area.
Update manually in the Local server.
If now the same issue happens, start over again and this time, exclude other software, like plugins or theme (use Twenty Seventeen) and update again manually.
At this point, you would remain with the same testing site I have locally, where I see no such issues (I usually update existing test sites and re-use them at times like these to check).
However it might also be that the issue by then still happens, then it could be something I miss in my tests, or some other particular issue, Server, anything that is “unlike” any other install where this did or does not happen.
In that case I usually need to deploy such sites locally myself using a copy of it (Duplicator), but this is a bit difficult here in WordPress ORG forum, where I have no methods to let you provide me such data privately and securely, moreover I believe it is not allowed generally, I am not sure, to share such data here in this forum.
To note is that Types, as used here, will be removed by the end of this year.
Until then we do support it here and also try to solve issues if found (in the code).
Can you check what happens with the above steps?
