Forum Discussion
Annie_Murphy
10 months agoOccasional Contributor
hello
When this happened in the summer I reverted back to 3.44, starting this past week 3.44 also started to get the same error.
So I upgraded to 3.49 skipping the earlier version that started the error originally.
Not sure how one determines if they need to upgrade to the newer version but in my case I was trying to fix the authorization issue.
I am not really sure that telling me not to upgrade is a good solution to my issue but thank you anyway for your response.
Related Content
- 3 years ago
- 3 years ago