Bruno Kos
WPML Supporter since 12/2018
Languages:
English (English )
German (Deutsch )
French (Français )
Timezone:
Europe/Zagreb (GMT+02:00)
|
I'm afraid we cannot help further here, you can ask perhaps your hosting support to move to another server or to increase resources, given that you said that the issue started only after you moved the site to another server. We spent quite a lot of time debugging and finding the solution, but to no avail.
We had no other cases of this sort and we weren't able to reproduce this in our testing sites either.
|
samaan-habibM
|
sorry but the database error happened on your staging server when you asked me to try working on the translation on your staging server in order to debug the issue and I've send to you a screenshot of the error on your staging server which mean the issue is not from the hosting
|
Bruno Kos
WPML Supporter since 12/2018
Languages:
English (English )
German (Deutsch )
French (Français )
Timezone:
Europe/Zagreb (GMT+02:00)
|
It was a different error that sometimes occur on our CW because of its limited capacity and happens even before WordPress was initialized.
The error with max_user_connections we weren't able to reproduce.
|
samaan-habibM
|
no sir it's the same error I've working on both server and test the issue and got the same error on both of them which is differently has nothing to do with hosting
|
Bruno Kos
WPML Supporter since 12/2018
Languages:
English (English )
German (Deutsch )
French (Français )
Timezone:
Europe/Zagreb (GMT+02:00)
|
This error this different one and happens even before you get to WordPress site. What you can do is to perhaps only use WPML, String Translation and only a few necessary plugins on your website (such as WooCommerce), perhaps it will reduce the load on the database and the error may be gone. I suggest you try that.
We simply have no other advice and don't know how to help further on this matter.
|
