Hi Mick.
Sorry to hear you’re having trouble with the post editor.
Once the post is in the published state, you should be able to check it out do some more post-editing. If that’s not the case, then it’s definitely something I’ll need to look into. Is this for your http://dev1.radfordmedia.com/ blog?
That error message you see pops up when you edit a post in WP, but our service doesn’t want to re-translate it because someone’s currently working on cleaning up the translated copy, and we don’t want to change it out from under them. When you get that message, you’ll need to re-publish once the post-editor has finished, or your local changes won’t get picked up on our side.
However, it sounds like in your case that you’re erroneously getting the message. When you can, please confirm the blog, and I’ll take a look.
Thanks!
Steve
Hey Steve,
The project is now on the live site which is El Musico
Also, just so I have this straight, two other questions:
1. Whenever changes are made to the post from the WP site does GTS re-translate the entire post with the machine translation?
2. Once the translation is approved/published by user (me) from GTS, does it still get crowdsource translation?
I ask these two questions because for some posts my client has their own translations that I’ve entered.
By the time I’m done picking your brain I’ll be an expert on this stuff… I’ll be asking you for a job ha!
Thanks!
Hi Mick.
The site looks great…glad to see you got it finished and launched!
To answer your questions:
1. Yes, currently the whole post gets re-translated. It’s on our todo list to automatically apply translation units (i.e. your changes) where the content hasn’t changed, but we just haven’t had time to do that yet.
2. Once a post is approved and pushed to your blog, then it’s no longer eligible for crowdsourcing. If you do have your own people, though, you might want to have them keep an eye out for new posts…the turn around time will be surely be faster if you have dedicated moderators.
Hope those answers help, and look forward to hearing any more feedback or answering any more questions for you.
Thanks again!
Steve
Hey Steve,
As always thanks for your help with this plugin – despite the hiccups I’m having it really is a great plugin. In fact I think the main problem I’m having may be a server issue. I’m outlining the process I used and maybe you can shed some light.
create a post in WP > go to GTS site > check out > approve> publish
(This is all good – from here the translated version is “locked” so to speak)
Needed to make change but once “published” it’s not available for check out again. What I did was the following:
GTS settings >Manage Posts > deleted the post in question from the list >went to GTS site and the post was once again available to check out and edit.
Now the question – the process I just described worked perfectly on my dev site, but not on the live site. Two different servers, two different hosts. Do you know what could be causing that? Is it a database thing? CHMOD settings?
Let me know if anything jumps out at you – also I can send you my logins if you need to take a look at the backend.
Thanks so much.
Also – the only other difference is I am the only editor on the dev site. Don’t know if that makes a difference.
thanks
Hi Mick.
Interesting… Before I look into it, though, I do want to point out something that might make your life easier. There’s a “Show Published Entries” checkbox on the page on the GTS site that you can use to toggle and display and check out the already published entries. Let me know if for some reason that feature isn’t available to you.
And now that I’ve had a look into our server logs, I see the following error coming up when we try to post the translated content to your live site:
ERROR 404 http://elmusico.luketan.com/wp-content/plugins/gts-translation/callbacks/gts-save-content.php
I see that your dev site was created with an preceding /cms in the plugin path and that your live site also responds to that URL. Did you move the wp-content directory after signing up? In any case, I’ll update the path in our database and you should start receiving the translated posts again.
Thanks!
Steve
