hide 'all' tab in detail view.

[spg82]

Hello,

I want to remove the 'all' tabs from detail views of all my modules. I have used Admin->Configure Group Tabs to group my subpanels into different tabs and this works fine except that I still have everywhere 'All' tab containing all my subpanels. Is there a way to get rid of it?

I'm using Sugar 5.1

Thanks and regards,
Steliyan

[r.douglas@uq.edu.au]

Hello,

I want to remove the 'all' tabs from detail views of all my modules. I have used Admin->Configure Group Tabs to group my subpanels into different tabs and this works fine except that I still have everywhere 'All' tab containing all my subpanels. Is there a way to get rid of it?

I'm using Sugar 5.1

Thanks and regards,
Steliyan

Any updates on this? How about changing the order of these tabs to put the All tab last? I'm using Version 6.2, Corporate edition

[kuske]

You can change the module include/SubPanel/SubPanelTilesTabs.php as follows:

1st patch (line ~167):

         /* Add the 'All' group.
         * Note that if a tab group already exists with the name 'All',
         * it will be overwritten in this union operation.
         */
        if(count($groups) <= 1)
         $groups = array(translate('LBL_TABGROUP_ALL') => array('label' => translate('LBL_TABGROUP_ALL'), 'modules' => $tabs));
        else
//KUSKE begin patch
//          $groups = array(translate('LBL_TABGROUP_ALL') => array('label' => translate('LBL_TABGROUP_ALL'), 'modules' => $tabs)) + $groups;
//KUSKE end patch
        /* Note - all $display checking and array_intersects with $tabs
         * are now redundant (thanks to GroupedTabStructure), and could
         * be removed for performance, but for now can stay to help ensure
         * that the tabs get renedered correctly.
         */ 
  

2nd patch (line ~237):

             if(empty($displayTabs) && !empty($otherTabs))
            {
                //WDong Bug: 12258 "All" tab in the middle of a record's detail view is not localized.
//KUSKE begin patch
//              $selectedGroup = translate('LBL_TABGROUP_ALL');
                $otherKeys = array_keys($otherTabs);
                $selectedGroup = $otherKeys['0'];
//KUSKE end patch
                $displayTabs = $otherTabs[$selectedGroup]['tabs'];
                $sugarTabs[$selectedGroup]['type'] = 'current';
                $retTabs = array_intersect($tabs, array_map('strtolower', $groups[$selectedGroup]['modules']));
            } 
  

[r.douglas@uq.edu.au]

You can change the module include/SubPanel/SubPanelTilesTabs.php as follows:

1st patch (line ~167):

         /* Add the 'All' group.
         * Note that if a tab group already exists with the name 'All',
         * it will be overwritten in this union operation.
         */
        if(count($groups) <= 1)
         $groups = array(translate('LBL_TABGROUP_ALL') => array('label' => translate('LBL_TABGROUP_ALL'), 'modules' => $tabs));
        else
//KUSKE begin patch
//          $groups = array(translate('LBL_TABGROUP_ALL') => array('label' => translate('LBL_TABGROUP_ALL'), 'modules' => $tabs)) + $groups;
//KUSKE end patch
        /* Note - all $display checking and array_intersects with $tabs
         * are now redundant (thanks to GroupedTabStructure), and could
         * be removed for performance, but for now can stay to help ensure
         * that the tabs get renedered correctly.
         */ 
  

2nd patch (line ~237):

             if(empty($displayTabs) && !empty($otherTabs))
            {
                //WDong Bug: 12258 "All" tab in the middle of a record's detail view is not localized.
//KUSKE begin patch
//              $selectedGroup = translate('LBL_TABGROUP_ALL');
                $otherKeys = array_keys($otherTabs);
                $selectedGroup = $otherKeys['0'];
//KUSKE end patch
                $displayTabs = $otherTabs[$selectedGroup]['tabs'];
                $sugarTabs[$selectedGroup]['type'] = 'current';
                $retTabs = array_intersect($tabs, array_map('strtolower', $groups[$selectedGroup]['modules']));
            } 
  

Hey Kuske, thanks for the direction. Is this method upgrade safe or should the file be copied into a folder somewhere in the custom directory? thanks again for the heads up

[kuske]

This is a core patch, which is NOT upgrade safe.
There is no possibility at the moment to implement it upgrade safe.