Simple Translator (formerly known as Another Language Switcher)

Has anyone resolved the issue where you can only have one title field translated?

Ludwig, I am not sure I understand, but making additional custom fields with a language extension will work with titles just as with any custom field.

title title_de title_sk

body body_de body_sk

In this case the default language is english, but has no extension (as instructed Mark). The title for english is THE entry title and the translated are custom fields. For other fields like body, you create the default and thyen the lang variations.

Well I mean that, every weblog has a title field and custom fields must be unique which means that if I have weblog_a and weblog_b and they both have title fields, how will EE distinguish between title_fr for weblog_a and title_fr for weblog_b?

I see. Well 2 options come in mind:

1. If you can use the same field-set for weblog_b. I usually have some universal field-set that can be reused for other weblogs.
2. Ignore the title and make a custom title that has the weblog name in it. For example

weblog_b-title weblog_b-title_de weblog_b-title_sk

weblog_b-body weblog_b-body_de weblog_b-body_sk

Mind you you will still put something into the title field but will not use in the template.

Thanks elemental,

I’m assuming then that this extension is no longer being developed and their is no “proper” solution?

Hello,

thanks

scratch that, I had enabled template caching, a big no-no with simple translator.

Hi, I’ve inherited a site that uses this extension. Currently it uses per language weblogs etc to enable translated content to be displayed when the language switcher is switched.

The client now needs me to enable the site to have per language URLs that can be used in links, for search engines to consider as separate pages and to allow each language site to effectively have its own structure, e.g.

www.site.com/de/nachrichten/etc

rather than

www.site.com/news/etc

which is how things appear at the moment (with the same url displaying different language content dependant on which language has been chosen).

Can anyone point me to how to achieve this, or tell me whether it is even possible using this extension. I note that there are a couple of posts in this thread that raise similar issues, but that they’ve not really been answered.

All suggestions welcome. Thanks.

Hi Mark,

Thinking of installing your extension. A couple of questions:

1. I have several sites operating under MSM. Only one of them needs translations. I just want to make sure that I can install your extension, and it will only affect the site where I enable it. Is that correct?

2. I have different domain names as entry points to the site, depending on the language (I couldn’t get a good domain name that works in all languages). So, for example, I would like a user that goes to www.myenglishdomainname.com to end up on the English pages, and www.myswedishdomainname.com to end up on the Swedish pages of www.mydomain.com. Preferably I would also like the domain shown in the browser to be the original one, if possible. Any ideas for how to make this work?

Thanks,

/Bo

I used this extension on a site with great pleasure. Now I installed it a for a new site and discovered that the extension is not working with a custom_field using WYGWAM…. It always shows the default language… That’s a pity.

Someone know about this and found a workaround? Otherwise I go back to tiny_mc, but that’s not my favorite.

Is it correct that this extention does not work anymore with the latest build, 1.6.8 - Build: 20100121? It used to work with previous ones. Pity.

.

What is to stop it from working in 1.6? I just ported it to 2.0 and it works fine.

EE fixed a bug in 1,6,8 that existed for a long time and allowed incorrect use of quotations in a PHP string. http://ellislab.com/forums/viewthread/142560/ ( a numeric {if} statement in an {exp:query} tag will not work (and even fouls up following conditionals) if quotes are not used around the number.) EE 1.6.7 accepted the conditional even if there were no quotes, and this was a bug. 1.6.8 does not accept this anymore, and returns a PHP error message.

I noticed that the use of Simple Translator in 1.6.8 gives exactly that PHP error. My conclusion, does not work anymore because of the bug fix. This was on a project some time ago, wich I left alone because of this. So, you say it still works? Hmm might give it a try again…:-)

It sounds like you’re pointing out a very very specific usage of a tag, the query tag of all tags, which I avoid like the plague. Please provide a code sample of where it messes up. I ported it to 2.0, and it’s switching {body} to {body_es} and {body_it} just fine within a normal entries tag.

http://screenr.com/w7A

Well, it’s very simple. As soon as I ‘switch on’ the extention, I get a zillion PHP errors.

like:

Warning: Missing argument 1 for switch_field_names() in /home/path-to-directory/extensions/ext.simple_translator.php on line 383

Warning: Missing argument 2 for switch_field_names() in /home/path-to-directory/extensions/extensions/ext.simple_translator.php on line 383

Any Clue?

I have version Simple Translator (v.1.0.9) installed. And running EE 1.6.8 Before my upgrade from 1.6.7 I had no problem at all with this extention.