Closed (works as designed)
Project:
Panels
Version:
7.x-3.0-alpha1
Component:
Panel pages
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Mar 2009 at 20:10 UTC
Updated:
18 Oct 2011 at 15:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
stella commentedComment #2
ifrikIf you use the contributed modules "panels" and "i18n module" for menu translation, then you got the problem that they don't work well together.
If you add a menu item in the process of adding a new page with panels, then no string is added for translation, so it can't be translated. However is you add a new page without a menu item, and then add the menu item in the menu module, then the string is added and can be translated.
Comment #3
merlinofchaos commentedWith the release of Drupal 7, Drupal 5 is no longer supported.
Comment #4
brycesenz commentedReopening, as I believe that this is still an issue in the D7 version of both i18n and Panels -
I am running Drupal 7.8, the latest version of i18n (Internationalization), and the latest -dev version of Panels (plus all required modules).
If a use the panel interface to add a new menu item, that menu item cannot be translated. More accurately, you can go through the UI motions of translating the item, but no translated string is ever actually saved. If you add a menu item through the menu interface which points to the Panel path, then the menu item can be translated correctly.
Browsing the i18n issue queue, it sounds like the description in post #2 is accurate, and is a bug in this module and not in i18n.
Comment #5
brycesenz commentedActually, ignore the above post -
When you add a panel as a menu item through Panels, it is added as "Language Neutral". As long as a menu item has this setting, it will let you go through the motions of translating it, but no translation will ever be saved. Simply changing the menu item to "English" and then translating it solves the issue.