on page admin/settings/language/configure/language
there are 2 different menu_default_local_task-s when the l10n_client module is also enabled with i18n..

see attached picture..

Comments

jose reyero’s picture

Project: Internationalization » Localization client

I think this is l10n client's issue

I don't know what happens with that menu, but I see the two tabs causing trouble are l10n's. Maybe the issue happens when one more tab is added there (language icons) but I'm just adding a 'non default local task'...

Gabor?

gábor hojtsy’s picture

Project: Localization client » Language Icons

Localization client just adds the "Language negotiation" default tab and the "Localization sharing" non-default tab:

  // Direct copy of the Configure tab from locale module to                                                                
  // make space for the "Localization sharing" tab below.                                                                  
  $items['admin/settings/language/configure/language'] = array(                                                            
    'title' => 'Language negotiation',                                                                                     
    'page callback' => 'locale_inc_callback',                                                                              
    'page arguments' => array('drupal_get_form', 'locale_languages_configure_form'),                                       
    'access arguments' => array('administer languages'),                                                                   
    'weight' => -10,                                                                                                       
    'type' => MENU_DEFAULT_LOCAL_TASK,                                                                                     
  );                                                                                                                       
  $items['admin/settings/language/configure/l10n_client'] = array(                                                         
    'title' => 'Localization sharing',                                                                                     
    'page callback' => 'drupal_get_form',                                                                                  
    'page arguments' => array('l10n_client_settings_form'),                                                                
    'access arguments' => array('administer languages'),                                                                   
    'weight' => 5,                                                                                                         
    'type' => MENU_LOCAL_TASK,                                                                                             
  );                                                

Looks like i18n is also adding a defualt tab there. I have no idea ATM on how could we avoid multiple contribs putting in default tabs there. I also think that l10n_client is adding a more specific default tab title, which is better to use instead of just plain "Configure". I'd try using the same default tab code in Language icons, and see what happens.

hass’s picture

Same here. I'm with Garbor - we should use the 'Language negotiation' tab title.

hass’s picture

Priority: Minor » Normal
Status: Active » Needs review
StatusFileSize
new1.13 KB

Patch attached copies 1:1 the menu item from l10n_client. We might need a menu refresh in .install for people upgrading from older versions...

Freso’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev

Could somebody please test that the patch works as expected? Thank you.

jose reyero’s picture

I think this was caused by a bug in i18n module (menu_alter) already fixed so possibly no need for any patch here.

hass’s picture

Jose: No, this patch needs to go in...

jose reyero’s picture

Status: Needs review » Reviewed & tested by the community

@hass,

Yes, you're right, I had read the thread too quickly...

I've tried it and it works.

Freso’s picture

Thanks for testing, Jose!

I'll commit this once I get back to my private development machine. (And per #4, I'll add a menu_rebuild() to a hook_update_600N, just to play it safe.)

hass’s picture

The menu refresh is not really required... all people should run update.php... on every module update.

Freso’s picture

Status: Reviewed & tested by the community » Fixed

@ hass: Alright. Thank you. :)

I've committed the patch to 6.x-2.x and 6.x-1.x and once I've committed the flag icons waiting in the queue, I'll make a 6.x-1.1 release.

Thanks for the help and inputs everyone! :)

Status: Fixed » Closed (fixed)

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