Support/Comments for Babel 2.2.3-rc1

This is an auto-generated topic for Babel 2.2.3-rc1 by mikrobi.

Brief Description:

Babel is an Extra for MODx Revolution that helps you managing your multilingual websites using differentc ontexts. Babel even supports managing several different multilingual websites within one MODx instance by using so called context groups.
Babel maintains links between translated resources. In the manager you can use the Babel Box to easily switch between the different language versions of your resource. Translations can be created automatically by Babel or defined manually.
Additionally Babel can be used to synchronize certain template variables (TVs) of translated resource which should be the same in every context (language).
Offical documentation is located at http://rtfm.modx.com/display/ADDON/Babel. You may have a look at our tutorial for setting up your multilingual website with MODx and Babel.
Feel free to suggest ideas/improvements/bugs on GitHub: https://github.com/mikrobi/babel/issues
New in 2.2.3-rc1

• Issue #18: Added 'id' placeholder for BabelLink chunk which is used by the BabelLinks snippet.
• Fixed issue #21: Manager redirect causes error in Google Chrome browser.

New in 2.2.2-rc2

• Fixed bug: Initial synchronization of TV values when setting a link manually didn't work.

New in 2.2.2-rc1

• Added feature #16: Values of synchronized TVs of the source resource(s) can be copied to the target resource when setting a translation link manually.
• Added showUnpublished parameter to BabelLinks and BabelTranslation snippets.

New in 2.2.1-rc1

• Added feature #11: User is redirect to new resource after creating a translation.
• Fixed issue #15: Babel TV of duplicated resources is being initiated.
• Alias is duplicated when creating an translation, too.

New in 2.2.0-pl

• Fixed bug which occured when creating new resources.
• Fixed bug in validation which is performed on setting a link manually.
• Improved performance of TV synchronization.
• Regarding issue #10: Added checks to handle invalid Babel settings (defined by the user).

Hi Jakob, great work on this package! I’m using your SEO friendly method with the rewrite rules and everything works great. One thing I noticed about the [[BabelLinks?]] snippet is that it displays the links to each translation on the page even if there is no translation for that particular page. So when I click the link on a page that does not have any translations yet I get a ’file not found’ error page.

How can I do a check to see if there is an existing Babel translation for the current resource to be able to disable the language links generated by BabelLinks?


Thanks again for creating this wonderful addon.

That’s strange behaviour. Babel works in that way that it displays the site_url (= start page) of a specific language when there is no translation available. Have you set the site_start setting for your contexts?

Where do the links which cause the 404 erros refer to?



Nevertheless you can use the [[+id]] placeholder in your own BabelLink chunk to hide links to languages for which no translation exists:

site_start was not specified in the context... setting the site_start to the id of the translated "home" page was all that was needed. I should have paid more attention to your instructions I just got so excited and left out the site start, error page, etc. for the extra context Muchas Gracias!

Hi,

does Babel 2.2.4-pl works with MODX 2.1?

Yes it works perfect with 2.1.0-rc4

Is it possible to have the default language without the language code (en) in the url?

I have two questions:

1) Where are the language names defined. Right now, I’m just getting babel.language_hu for languages that are not in the default plugin.

2) Also, is it possible to isolate babel to just a certain group of resources? I don’t want to translate the entire site.

Quick heads-up.

Tags generated by getResources and toLinks and tagLister stopped working after the upgrade in the English side of the site. The French side still works fine.

I have no idea if this is something to do with Babel yet, or something hidden within Contexts definition. I’m going to check my contexts now to ensure they are exactly as per the manual.




///Problem fixed. cached snippet called within formatting template within chunk. I think. Worked fine in 2.1.1. The fix to some problem in 2.1.2 revealed the error.