I have had a call with Lauren Jeffcoat where we have realized together that any modification done in WordPress didn't seem to save properly ever since I have installed the WPML plugin. At least, if I go on an try to translate a post, page or any type of content, the spinner icon will be visible in the element list but it would spin forever until I end up refreshing the page.
Link to a page where the issue can be seen:
hidden link
I expected to see:
The gearlwheel icon showing up instantly, confirming that my modification took place as expected.
Well, it happens if, let's say, I try to modify a Post and hit "Update". The button will turn into the spinner but the page will load forever until I get a HTML 500 server error.
The same goes for the pages that I try to translate manually using the WordPress Editor. If I go back to the pages/posts list as shown above, the spinner indicating that the page is currently translating won't stop spinning.
I have been suggested to increase the WordPress Memory Limit, which I did, but it doesn't seem to have solved the issue. I have also tried turning off the CDN in my hoster service GoDaddy in order to see if the wp-config.php file had effectively been updated, but to no avail.
A) When saving/updating the WP post and server returns a 500 error
B) When saving post and WPML icon is spinning
Did I understand it correctly? If so we will need to open new ticket for your other issue, as we limit 1 issue per ticket, let me know please.
2) Are you using translate everything or translate some from WPML > Settings, if so you can not mix methods of manually translating via WPML editor and or WP editor.
Yes, you did understand correctly. So, you are saying I should open a new ticket for the A) 500 error, am I getting you right?
As for your second question, I went to WPML > Settings and the current setting is set to Translate What You Choose. Is that what you meant?
As for switching from WPML editor and or WP editor, what I was doing so far was clicking on the cog icon AND switching to WordPress Editor, yes. Could that be what is causing the issue?
A) I think this might not be related to wpml, please first check if it still happens when wpml is disabled. If so, contact hosting support otherwise let us know or open a new ticket for this.
B) Yes, you shouldn't be doing that and mixing editors, if you are using wpml editor to translate then you should use that or otherwise you should disable it by clicking WordPress editor and continue to manually edit 2nd language page.
If you are trying to use wpml editor, please try to go to WPML > Translation management and send 1-2 pages for translation to yourself. Then go to WPML > Translations > take and translate and let me know if that works.
« If you are trying to use wpml editor, please try to go to WPML > Translation management and send 1-2 pages for translation to yourself. »
Ok I will try that, but in the meantime can I « stop » the current translations still going on and try again using the right way to translate my posts? (let's say through the WPML Editor only)
Otherwise, could it be possible to grant you with my WordPress site credentials so that you could log in and have a look for youself? The is no sensible data whatsoever on our site (no user account, etc.) si there is no security issue.
Ok so I went to WPML > Translations and saw the post that were still waiting for a translator. What I did is I stopped them, went back to WMPL > Translation Management and switched back to Automatic Translation. I then bulk started the translations.
Since I am now using the automatic mode the posts should translate by themselves, right? How long is the process supposed to take? Because it's now been several minutes that I have launched the thing and it is still processing.
New threads created by Dražen and linked to this one are listed below:
great, and yes if you have canceled the jobs and then enabled automatic translation it should translate automatically in the background.
If the number is not lowered after a few minutes and translation are not delivered it could be they are stuck and something is causing issue, we would need to check on this.
We limit 1 issue per 1 ticket, to keep things clear and easy to follow. I have opened a new ticket for your new issue:
