stevevls

Hi again. I’ve looked a little further into what’s happening with your blog. I see that we had a problem pulling in the data for the initial translation of your website…somehow the data got corrupted. Fortunately, I see that you have translated content now for new posts. From now on, as you edit or write new posts and pages, they’ll be translated according to plan. Sorry for the inconvenience!

By any chance, did you untick the “Display machine-translated content” checkbox on the GTS Settings panel in your WP admin?

Hello…

I can tell you for sure that it does’t work with WP MU. We decided to keep the plugin simple at first and add MU support later if we found a demand for it.

As for Buddy Press, I don’t see any reason it shouldn’t be compatible if you’re using single user WP. We haven’t tested it, though, so I can’t say for sure that it’s conflict-free.

Hope that helps!

Cool man…I’ll put it on the request list. An initial looks tells me that it could take some effort, so I won’t be able to get to it right away.

Just wanted to let you know that I just packaged up a new version (1.1.7) for release that should fix your problem with menus displaying in English.

Thanks!

I’ve thought about rewriting links on the main domain, but the problem there is that it’s possible that a user may want the link to point back to the original text or a specific translation. That’s why I was thinking about the shortcode…so the intention is clear. I really wish that WP had a good mechanism for inter-blog linking that we could extend from…the use of plain old URLs seems short sighted to me!

And…if you modify a page, we’ll run it through the translator again.

Cheers…

Great! I’m glad that worked.

The absolute URLs is a tricky one to solve. Most of our users thus far are using WP as a blog rather than a CMS, so they haven’t found it to be too much of an issue…more of a nice to have if anything.

One idea I had was to provide a shortcode tag for links, so you could add a snippet like [gts-permalink 'permalink-name'] and it would rewrite itself to whichever language is currently selected. Something to mull over with future versions of the plugin…

Actually, I just thought of something… Do you have a permalink structure set as just the post name? If that’s the case and you don’t have any posts in your database, then you’ll get a 404. That happens because ambiguity is introduced into the rewrite rules. If you see that your permalink is just the post name, change it to anything else, and the pages will start working.

Hi again.

I’ve been digging into why the page titles aren’t translating, and I was able to find why the English text is showing up for your menu pages. The menu functionality does some slightly non-standard stuff, but I found a workaround. We’ll be releasing a new plugin (version 1.1.7) soon, so keep an eye out for that.

As for the Recently Popular plugin, it’s not going to be possible to translate the list that it’s spitting out. Unfortunately, instead of using WP code to get at the posts, they’re doing a direct select against the database, and they’re not calling out to any hooks or filters afterwards. They should be at the very least invoking the filter for ‘the_posts’ if they want their plugin to play well with others.

Finally, I’m still unsure why you’re getting 404s… It’s difficult to debug from here. My guess is that something about the way we’re modifying the select statement for pages isn’t working in your environment. Would you mind trying deactivating all of your plugins (including GTS) and then re-enabling only GTS? If it works, then we can start looking for conflicts. If it doesn’t, then it’s something internal. Also, can you check for any PHP errors in your server logs? We’ll see what that turns up…

Thanks!

Hi again.

I notice something interesting, which is that all of the permalinks are localized. If you hover over the links in the left sidebar after changing the blog language to Spanish for example, you can see that the URLs are translated.

So I guess that means we have two questions… The first is why the text for the links is in English. How are you generating the links in the sidebar? The second is, why aren’t the localized URLs working? A very common reason is that there’s a plugin that’s conflicting with ours…can you tell me which other plugins you have installed?

As for the virtual hosts, a number of people have asked the same thing lately, so I’ll be putting together a guide very soon. I’ll let you know when I’ve got it put together.

Thanks!

Hi there. Thanks for taking the plugin for a spin. I’m the developer that maintains the plugin. Let’s see what we can do for you…

First off, it should be no problem that you have pages and not posts. As you publish pages, they’ll be translated. Can you send me a link to your blog so that I can poke around and see about the pages that don’t have translated content yet?

As for the links, that can be tricky business. If the link is generated by WordPress, then it should go to a translated page. However, when the links are in the post or page body itself, it’s difficult to infer whether it should link to a translated post or to the original and we just leave it be. Unfortunately, the new feature in WP 3.1 inserts the link as HTML…it doesn’t use a nifty internal function call that we can hook into.

Shortcodes in the post are another troublesome area. We remove short codes before sending the post off for translation, but many plugins don’t register their shortcodes for admin screens…and if they’re not registered at the time you publish your post, we can’t tell the difference between a shortcode and bracketed text. The only fix there is to modify the problem plugin.

So, if you can send me a link to your blog, I’ll see if I can turn up anything else.

Thanks!

Hi again. Well, the plugin should work within those parameters. Do you have access to the error logs for your web server? My guess is that our plugin is looking for a PHP library that you don’t have installed, and looking at the error log could confirm or deny that. Thanks!

Hi there.

I’m the developer who wrote the plugin, and I’ll see if I can help out. I haven’t seen this error before, but it’s going to be something specific to your environment. Can you tell me the version of PHP and WordPress that you’re using plus which webserver and its version? That will help in trying to get to the bottom of this.

Thanks!

Steve

Excellent…glad to hear it!

Hi there, and thanks for taking the plugin for a spin. Can you confirm that you’ve got PHP version 5.1.3 or above? Unfortunately, our plugin doesn’t work with PHP versions earlier than that. Thanks!

Hello again… We were able to reproduce your issue and get it fixed in the latest 1.1.1 release. You can upgrade automatically from your WP admin. Thanks for reporting the issue!