@alx359 Thanks for your quick responds!
I did some investigation.
It is a 504 mistyped it sorry.
The only console log I get is the following: “Failed to load resource: the server responded with a status of 504 ()”
And the following is on my screen: “504 Gateway Time-out
The server didn’t respond in time.”
The only difference I can find between the 2 are, the user information and one of the accounts has these additional rights: “edit_wplc_quick_response, edit_other_wplc_quick_response, publish_wplc_quick_response, read_wplc_quick_response, read_private_wplc_quick_response, delete_wplc_quick_response”
Btw, I tried turning the plugin off and then everything works fine. So that’s the reason for me posting this topic in the first place.
I also tested on a different domain (used a backup so same exact same website) that we have under construction, there it does “work”. It gets to the order page after almost 3 minutes of loading, I guess on the live enviourment it just throws a 504 because it’s taking to long. If I remember correctly the browser will autmaticlly throw a 504 if it takes to long. But now the question is Why does it take so long with the plugin active.
On the other domain I also tried turning off plugins 1 by 1 but still the same issue remains.
When reaching the orders page I get the warning in the chat: `wp.compose.withState is deprecated. Please use wp.element.useState instead.
i @ deprecated.min.js?ver=8778985ac0dfb16f24f8ef86d0718f43:2
w @ compose.min.js?ver=058697a4c5024045c81954f411ff6dba:2
(anonymous) @ index.js?ver=3.1.0:2
n @ index.js?ver=3.1.0:2
(anonymous) @ index.js?ver=3.1.0:2
(anonymous) @ index.js?ver=3.1.0:2`
But I always get this one so I dont think it has anything to do with it.
-
This reply was modified 3 years, 1 month ago by
zudofeathers.