If by user, you mean me, then you got support here on the forum, the correct fix was to roll back to 2.1.8 and wait for a hotfix that addresses your issue.
There is a hotfix out now for this issue.
If by user, you mean me, then you got support here on the forum, the correct fix was to roll back to 2.1.8 and wait for a hotfix that addresses your issue.
There is a hotfix out now for this issue.