In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories
  

View Revisions: Issue #776 [ All Revisions ] [ Back to Issue ]
Summary 0000776: Change usage of "lu_rootcategory_name" Language label
Revision 2010-06-14 15:11:24 by Dmitry
Description Currently we are using "lu_rootcategory_name" label in Admin to list in navigation bar in Catalog.

TODO:


1. For the FRONT

We need to change the following method to use "lu_home" (label in Advanced theme) instead of the one defined in ConfigValue('Root_Name') configuration variable.

function RootCategoryName($params)
{
    $phrase_name = $this->Application->ConfigValue('Root_Name');
    $no_editing = array_key_exists('no_editing', $params) && $params['no_editing'];

    return $this->Application->Phrase($phrase_name, !$no_editing);
}


Also, add "lu_home" to all Front end language packs of ALL themes (advanced already has it)



2. For ADMIN

Change lu_rootcategory_name to la_rootcategory_name and move to Admin Language pack and get rid of the deprecated variable "Root_Name".
Revision 2010-06-13 23:24:37 by Dmitry
Description Currently we are using "lu_rootcategory_name" label in Admin to list in navigation bar in Catalog.

TODO:


1. For the FRONT

We need to change the following method to use "lu_home" (label in Advanced theme) instead of the one defined in ConfigValue('Root_Name') configuration variable.

function RootCategoryName($params)
{
    $phrase_name = $this->Application->ConfigValue('Root_Name');
    $no_editing = array_key_exists('no_editing', $params) && $params['no_editing'];

    return $this->Application->Phrase($phrase_name, !$no_editing);
}


Also, add "lu_home" to all Front end language packs of ALL themes (advanced already has it)



2. For ADMIN

Navigation bar should start with the Section called Home by default, but can be translated when new languages installed and translated version will be automatically used in Navigation bar resulting with NO need of separate Language Label for the Admin.

Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories
  

Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker