You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 31, 2020. It is now read-only.
return $partialHelper($partial, $model); // 'partial/menu.phtml' and $model
Why is this a problem? If you have modules with two different menu templates saved under the same name (partial/menu.phtml), then the modules loading order will decide which template is used.
The text was updated successfully, but these errors were encountered:
Setting the module when calling setPartial has absolutely no effect.
Right, because the module option is an obsolete option parameter.
If you have modules with two different menu templates saved under the same name (partial/menu.phtml), then the modules loading order will decide which template is used.
You can specify the module name with the partial parameter:
Setting the module when calling setPartial has absolutely no effect.
Consider the following code:
renderPartialModel function (https://github.com/zendframework/zend-view/blob/master/src/Helper/Navigation/Menu.php#L751) will return the $partialHelper with the following parameters:
return $partialHelper($partial[0], $model); // 'partial/menu.phtml' and $model
If we call the setPartial function with a string
the same happens:
return $partialHelper($partial, $model); // 'partial/menu.phtml' and $model
Why is this a problem? If you have modules with two different menu templates saved under the same name (partial/menu.phtml), then the modules loading order will decide which template is used.
The text was updated successfully, but these errors were encountered: