#1067: Build templates for ProjectBaseView and output_types.xml use different
name
for slot layout
--------------------+-------------------------------------------------------
Reporter: felix | Owner: impl
Type: defect | Status: new
Priority: normal | Milestone: 1.0.1
Component: build | Version: 1.0.0
Severity: normal | Keywords:
Has_patch: 0 |
--------------------+-------------------------------------------------------
The build template for the ProjectBaseView contains a guard that loads a
specialized layout for all slots:
{{{
if($layoutName === null &&
$this->getContainer()->getParameter('is_slot', false)) {
// it is a slot, so we do not load the default layout, but a
different one
// otherwise, we could end up with an infinite loop
$layoutName = self::SLOT_LAYOUT_NAME;
}
}}}
ProjectBaseView::SLOT_LAYOUT_NAME evaluates to 'slot'. However, the
output_types.xml defines this layout with a different name:
{{{
<!-- special layout for slots that only has a content layer to prevent
the obvious
infinite loop that would otherwise occur if the decorator layer has
slots
assigned in the layout; this is loaded automatically by
ProjectBaseView::setupHtml()
in case the current container is run as a slot -->
<layout name="simple">
<layer name="content" />
</layout>
}}}
A freshly generated application will throw an exeception on all registered
slots as it tries to load an undefined layout.
--
Ticket URL: <http://trac.agavi.org/ticket/1067>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
