Hi,
I have tested this great module and it works very well.
Perhaps it missing the integration with i18n module (in particular with the taxonomy translation module) so this is unfortunately unusable on multilingual sites.
Do you think this kind of integration is possible in future releases? I suppose the modifications shouldn't be very complicated because i18n modules do all the work (or quite all).
Best regards,
Saxx

Comments

PixelClever’s picture

PixelClever commented

It is probably doable, however it may require rewriting major sections of code. i8n wouldn't do anything for it automatically since the information is gathered by sql select statements. I will look over the database structure and see how hard it would be.

Anyone is welcome to post a patch also.

SaxxIng’s picture

SaxxIng commented

Ok, I don't know very well i18n code, but I think it offers APIs to obtain the correct translated version of strings/taxonomies&co on the basis of the current language and configured language setting. I hope that none should write complex sql statements to work with translated versions (i18n should do it for us).
I'll take a look on this on next weeks (hopefully).
Regards,
Saxx

PixelClever’s picture

PixelClever commented
Status: Active » Closed (duplicate)

I know this issue came first, but there is a solution to this on http://drupal.org/node/364909, if we put it in it will probably related to this.