The 'page specific visibility' is not working properly for localized pages (different language pages). With previous versions to 4.6.3 (at least with 4.5.5, not sure about 4.6.x), you could use this filter to show specific blocks to specific languages. This was a workaround which next versions of i18n module is supose to fix (http://drupal.org/node/14347).

However, drupal 4.6.6 doesn't allow you to use this workaround.

The patch included, to apply to block.module, solves this problem.

Robert Garrigos

CommentFileSizeAuthor
i18n_block.patch644 bytesrobertgarrigos

Comments

robertgarrigos’s picture

robertgarrigos commented
Status: Needs review » Reviewed & tested by the community
jose reyero’s picture

jose reyero commented
Status: Reviewed & tested by the community » Needs review

Hi Robert.

Sure it works -looks ok- but it doesnt allow for generic -language independent- paths, which is what I'll be aiming at when thinking of blocks visibility. In addition, it's a patch for block.module -core-, plays with server variables, and not sure whether it could introduce some problem, maybe with IIS.. (?)

It also may change somehow the standard behaviour with paths/aliases/blocks, which is also a problem.

So, for now, it will be around in case someone needs it. Maybe we could compile a list of useful patches to add to i18n documentation -but not to the module, as the goal for next version is to provide a patch free module- ?

dopry’s picture

dopry commented

anyone using i18n that can test this against 4.6.5 and see if the bug still exists? I'm not quite sure how to test it.

moshe weitzman’s picture

moshe weitzman commented
Status: Needs review » Needs work
robertgarrigos’s picture

robertgarrigos commented
Status: Needs work » Closed (fixed)

I'm closing this as with the latest version of this module for 4.6.x this problem gets fixed.