Adding Translated Pages To WordPress

[Sebastian]

Hey Guys,

I'm having some big difficulties with this seemingly simple task.

I started off using 2 plugins, but the localized posts would never ping.....

So I gave up on plugins. Can any of you tell me if this strategy is sound ?

Say I have a page in Italian.

1. Can I create a category called /it/ in WordPress and make the post in that category ?
   
2. I'll deactivate mysitename/it/ indexing via the All in one SEO plugin, so that only /it/postname gets indexed.

What do you guys think ?

Seb

[Sebastian]

Figured this one out thanks to Nick M, thanks.

[pokeraussie]

I use a different wordpress install for the new language. Is that what you did? I guess if all you wanted to do was publish one translated page then it wouldn't be necessary.

[CasinoMack]

I've never done the separate wordpress installs for languages, but its a very cool way to do it. More work to manage and all that, but so much more control over things. All the plugins are annoying. Even the best translate plugin screws up your site if your theme isn't built for it.

When goto the translated page, it only shows your translated pages not the whole site.

[domainer]

I use a different wordpress install for the new language.

I've read this a few different places now and I'm not sure I really get it. So you actually do a new WP install into each folder for every new language? How about themes, plugins, etc....do those also get re-installed into each folder/language as well?

Is this the best/proper way to have multiple languages for a WP site (other than plugins, which I'd rather avoid)? Isn't it a bit tough having multiple logins, etc? Or am I missing something?

[Sebastian]

I use a different wordpress install for the new language.

Sorry, I don't get this. What are you installing, the WP software ?

What I did is create "parent page" like /es/

And then created the translated page and made it a subset of /es/

then I marked /es/ as private cause I had no content on it.

So I ended up with /es/translatedpost

I agree that the plugins suck

[pokeraussie]

I've read this a few different places now and I'm not sure I really get it. So you actually do a new WP install into each folder for every new language? How about themes, plugins, etc....do those also get re-installed into each folder/language as well?

Is this the best/proper way to have multiple languages for a WP site (other than plugins, which I'd rather avoid)? Isn't it a bit tough having multiple logins, etc? Or am I missing something?

IMO it's the best way to manage it, other people could have a different opinion. In terms of implementing it, just do a new WP install in each folder, so if you were translating the site to Russian, create a /ru/ folder and install WP in this location. Manage each WP installation as a new wordpress blog, so would install whatever plugins you needed for each blog.

[Charlie Brown]

Sorry, I don't get this. What are you installing, the WP software ?

What I did is create "parent page" like /es/

And then created the translated page and made it a subset of /es/

then I marked /es/ as private cause I had no content on it.

So I ended up with /es/translatedpost

I agree that the plugins suck

That's a nice way of doing it, but I'm curious, does that fix your ping issue? Am I wrong, but new pages don't ping, only posts?
EDIT: Ok, maybe pages ping after all based on this post: Sitemap pings for instant searchupdates — Blog — WordPress.com

Also, is there a reason why you didn't go through with your suggestion in your OP?

Really curious since the plugins I've tried for WP all had some kind of issues, and the new WP install has the disadvantage of increasing the maintenance, especially if the site is translated in many languages.

[Sebastian]

Yeah they still don't ping unfortunately.

You can ping manually, but it's not as good.

I never got a page to ping.

What you can do is create a post, ping it, and convert it to a page.

That works.

But you can't do that with a translated post because the permalink structure will change.

So you may ping sitename/translatedpage (post) but that won't help siteame/es/translatedpage (page) after conversion.