I had something similar on the site after the update. I solved the problem by rolling back to the old version. This is the best option when there is no time to search for a solution to the problem.
Edit History
I had something similar on the site after the update. I solved the problem by rolling back to the old version. This is the best option when there is no time to search for a solution to the problem.