The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I am trying to activate translation for panels on a bilingual website and I realized it was not possible to do so. The only information really relevant is from the following issue in the Panels module but it basically asks i18n developers to decide what to do wrt that issue.
I have tried what is suggested in this comment for translating views, but somehow it doesn't seem to be working. I got mypanel_en and mypanel_fr, each with an alias (en/mypanel => mypanel_en, fr/mypanel => mypanel_fr), but when I switch it still displays the same panel e.g. if I'm in en/mypanel and swith to french, the browser will end up displaying fr/mypanel_en instead of the french version.
Any suggestions, ideas, etc? (Note that if necessary I'd be ready to code a module (i18n_panels???) but in that case I would need strong support from the i18n team as I have never developed for i18n)
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | i18npanels.diff | 5.28 KB | JacobSingh |
| #1 | i18npanels.diff | 5.28 KB | JacobSingh |
Comments
Comment #1
JacobSingh commentedI've developed something which supports i18n for custom areas. There are other patches out there for panels to support node based i18n, but this is a good start. I've used it on sites where I need a view header, and I can't use views (obviously).
Here it is (added as a new i18n contrib mod).
Comment #2
JacobSingh commentedHere's another one with a simple settings page to convert existing custom panel areas to the i18n format. If someone wants to write a readme or something, would be cool. But I think the code is RTBC
Comment #3
jose reyero commentedHi Jacob, this looks good and contrib modules are welcomed.
Thanks.
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #5
eidoscomcommitted #2 to dev or elsewhere??
Comment #6
eidoscomsorry...... I'm searching for this on drupal 7 :(