Hi,

First thank you for your work, it is really impressive.

I would like to report you an issue I noticed (maybe it is from my drupal setup)

I have my drupal website installed with i18n from Drupal 6.2, and recently I updated to 6.4.
Now when I try to create a block with multilingual option, I have no problem (see 2nd screen)

As you see on this screen, he created me a block:14:title and a block:14:content field in a database table.

but the problem is : my block in core drupal has the oid = 6 ! so I never have any translations displayed.
I think the issue is only a synchronisation ... but I do not really know how to do that.

Regards,

Bhaal22.

CommentFileSizeAuthor
block_created.png144.32 KBbhaal22
block_creation.png143.68 KBbhaal22

Comments

bhaal22’s picture

Resolved by uncommenting in i18nblocs.module le call to i18nblocks_block.

Tks.

Bhaal22.

AaronCollier’s picture

Status: Active » Fixed
pasqualle’s picture

Category: support » bug
Status: Fixed » Needs review

hacking the module does not qualify as a fix

the function i18nblocks_block is still commented out in the latest dev release.

bhaal22’s picture

Yep,

I did not tell it was a fix, I only said I resolved partially the problem.
Why is this function commented, I do not know, I suppose there is a reason, but whithout this I do not have the translation feature available in block.

If you have another idea ;)

And to have the transalation, I have to display the bloc generated : BLOCKNAME[Translatable]

Regards,

Bhaal22

thomas23@drupal.org’s picture

As reported in #297464: Multilingual menu broken by 6.4 core update? #15 I have noticed a problem after 6.4 upgrade with my multilang menu block not showing for the non-default language. Could this be related? Any fix or help apprechiated.

Cheers.

jose reyero’s picture

Component: Module i18nblocks » Code
Status: Needs review » Fixed

Right, there was a mess with block delta and i18n's block id, which is a different number. Should be fixed in beta5

Thanks

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.