i18n / i18nviews support [#849174]

Since the redesign i18nviews title translation support doesn't work anymore.

Note that i18n changed also views support (own project, ...).
Please add i18n support natively to the titles.
Bug report because it previously worked.

Comment	File	Size	Author
#2	i18nviews_849174_2.patch	929 bytes	khaled.zaidan

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

khaled.zaidan CreditAttribution: khaled.zaidan commented 12 July 2010 at 09:39

Project:	Views Showcase	» Internationalization Views
Assigned:	Unassigned	» khaled.zaidan

Hmm, the same problem is there in both versions.

The problem is actually that i18nviews doesn't translate the title for a none-default display that is using a default title. It looks like i18nviews uses incorrect context in this particular case.

Comment #2

khaled.zaidan CreditAttribution: khaled.zaidan commented 15 July 2010 at 11:37

Status:

Active

» Needs review

File	Size
i18nviews_849174_2.patch	929 bytes

Changed the way the context is built before being passed in i18nstrings().

Previously, changing the default title while viewing a non-default display caused the new title to be saved with context 'views:view_name:page_1:title' instead of 'views:view_name:default:title'.

Now the default title is saved under context 'views:view_name:default:title: even if modified while viewing a non-default display. Issue seems fixed.