After a month of development, we are ready to show it :)
It is my first website using multilanguage. The client requirement was to create website in 4 languages (2 languages currently) I've started by trying i18n, good mod but I didn't like :
- The menu can be translated only using locale, and the menu translating module for i18n has some problems with menu cacheing. Pretend that you need to translate big menu in 3 languages, by locale.module - you'll spend a lot of time :)
- When you are in a node, and you are trying to switch language - it doesn't work. It was very confusing for me. I've found the fix for that in i18n issues (the patch in 1 string) - this fix is very old and it is still not in the HEAD. I understand that there may be some reasons to not apply this patch to the official release, but... my opinion is that the module should work correctly out-of-the-box.
- Multilanguaged blocks don't work in the way how I need it, you need to create new block for every language instead of editing one block in several languages - so, if you have many languages, your block configuration page will be a mess.
I decided to try localizer.module. And it turned out to be a wonderful module! Is is still in early stages of development, so it lacks some features of i18n (Lacked :) But it works without bugs for node translations and menus, that was important for me. It is much faster to translate menu items in localizer (each menu item has collapsible form and you can create translation of the item for all languages on one page), and these translations are saved in localizer table, it is the 'correct' way to translate user input (comparing to i18nmenu.module, that saves data in locale table). The localizer had two big problems (for me):
- No multilanguage variables support
- No i18nprofile analog
But the Localizer has very active developer, Roberto Gerola, who is open for suggestions and who improves Localizer every day, and who answered all my stupid questions on Localizer :). So it was a pleasure to create 1 module for Localizer and rewrite 2 modules, which helped me to finish my project:
- Localizervars (which was already rewritten by Roberto, named localizersiteinformation and is available in localizer installation now)
- Port of i18nprofile - Locaprofile
- Rewritten localizerblock to have multilanguage title and body in one box - http://drupal.org/node/113234 (in alpha)
Thank you, Roberto, for your great module and for your support!
I've also created a custom module for my project - serial.module. Admin can insert/delete product serials in the db, and when a user registers on the website, the module checks if there is such serial in the db and activates/deactivates user and sends email notification to admin.
http://russianwebstudio.com/other/serial.jpg
Porting site_map module to Drupal5 and modifying profile.module was an easy job after that :)
Comments
Moved the website to
Moved the website to http://implant-assistant.ru/test/ for testing
That's Great job indeed!
Hi Troy,
Your experience making me to think about Localizer.
Can you give some more directions on porting site_map issue?
Regards,
d.