joomla: ja-university where to locate header layout - joomla

I want to add a module position inside header in Joomla ja-university template. I tried to find header template to add a new module position. But, I could not locate the header template. How can I add a module position inside header.

Related

How to use Moo Cloud Extension block media use another template in magento?

I am adding My Cloud Zoom Extension Block use In My Vs_Ajax Extension in Magento. Can You please suggest me how to use Cloud Zoom block in another template. I want to use in product list page. I can open product in popup using vs_ajax Extension.
Check that ajax module layout file.
Check that product.info.media template file. Replace with your moo cloud zoom template file.
And necessary js into that ajax module head tag.

Joomla 3: Advanced Options for modules not working

In Module Manager, when I go to the module settings, in the second tab called "Options" there is "Advanced Options" section. Inside Advanced Options, there are some fields such as Module Tag, Header Tag and Header Class. When I update these fields, I cannot see any update in the module's html. Do I need to call these functions in the module template using code something like this $params->get('header_class')? I thought this would work without having to make changes to the template code. Just wanted to clarify.
I believe you should reference those items via $params such as $params->get('header_tag', 'h2') in the module chrome. If the module chrome does not make use of that parameter(s), then you won't see any change. You can create an override in your template /html/modules.php to use them.

Properly override a admin template file in Magento

I want to properly override this admin template file app/design/adminhtml/default/default/template/sales/order/create/form/address.phtml
From what I have found, the proper way is to create a layout file in a new module, set template path inside my module directory and reference that template file using reference node. But I have no clue how to do that.
I don't understand how the layout is controlled using xml as of now. Can someone show how to actually do that?
You should really create your own module, which you can then create a new template.
If you want to force is you need setTemplate() which takes your phtml path as a param. $this->getLayout()->createBlock('my_module/blockname')->setTemplate('my_module/template.phtml');
Bear in mind that the two slash notations here are different.
createBlock() is for a block, so will be in /app/code/<codePool>/My/Module/Blocks/<blockname.php>
setTemplate() is for the template, so will be in /app/design/<area>/default/default/template/template.phtml
Your <area> will be /adminhtml as you're in the admin backend.
In order to get the template working you'll need to create a new module and extend the adminhtml block file which uses this template. You'll have to find the block from the layout.xml and then you can extend the Block and specify a new template.
That's how I'd go about it, but I'm also really finding it hard to override things in the Adminhtml module.

Joomla in component does not include mootools in jdoc: type=head

I have problem with joomla's search component. When I display the component, there are no mootools included in the head, like on standard pages..
Please in which file is defined what is rendered in jhead?
In Joomla 1.5 you can use this line of code to include the mootools library:
JHTML::_('behavior.mootools');
You can use this line in your template's index.php file (mootools will be loaded on every page), or in the search component view.

Does Magento loads every xml file from the layout folder?

When calling $this->loadLayout() in your controller, does Magento fetches all of the xml files from the layout folders in the current design package?
I am trying to figure out how the customer login form pulls out the template from:
persistent/customer/form/login.phtml, is it because there is only a layout file: persistent.xml present?
EDIT:
I figured it out I didn't see there is a new module in 1.6.1.0 and also there are changes in model resource names
The customer login form pulls in because of the template or code block type referenced in that block's XML tag (in persistent.xml).

Resources