Hello Mint team and users,
I had a trouble with Cobalt from my first use, about the Menu Item ID fixed and required in the type declaration.
Each time, on my projects, I like to define some common type used in more than one section of content. For exemple, a type 'Common Article', that allow my customer to format some elements with some prepared fields.
Unfortunately, the Type Menu ID have to be declared (instead of what it was in Resources), and override the Section Item ID of the article in record view.
It's mean that I always have to declare a common Item ID for all types, witch will be use everywhere, loosing url menu and breadcrumbs organisation all over the site.
And it's really become more boring when you try to made a multi-languages site, then you have to declare lots of types for all the supported languages and all the proposed sections... :O
I just find a way to fix this for my projects, without having to hack this precious component.
I just override the default.php view of records, to add the section Itemid on all currents items...
Here the code to put :
...
defined('_JEXEC') or die('Restricted access');
global $app, $option, $Itemid;
$item_link = '&Itemid='.$this->section->params->get('general.category_itemid', JRequest::getInt('Itemid'));
foreach ($this->items AS $item){
$item->url .= $item_link;
}
?>
...
My Idea is simple, It could be really great if the Item ID fixed in section and type declaration were not [u]required[/u], and could be fixed by the one used in the current menu (on section or category view).
Hello Mint team and users,
I had a trouble with Cobalt from my first use, about the Menu Item ID fixed and required in the type declaration.
Each time, on my projects, I like to define some common type used in more than one section of content. For exemple, a type 'Common Article', that allow my customer to format some elements with some prepared fields.
Unfortunately, the Type Menu ID have to be declared (instead of what it was in Resources), and override the Section Item ID of the article in record view.
It's mean that I always have to declare a common Item ID for all types, witch will be use everywhere, loosing url menu and breadcrumbs organisation all over the site.
And it's really become more boring when you try to made a multi-languages site, then you have to declare lots of types for all the supported languages and all the proposed sections... :O
I just find a way to fix this for my projects, without having to hack this precious component.
I just override the default.php view of records, to add the section Itemid on all currents items...
Here the code to put :
My Idea is simple, It could be really great if the Item ID fixed in section and type declaration were not [u]required[/u], and could be fixed by the one used in the current menu (on section or category view).