I have a custom magento template which im trying to tweak and just have a question regarding templates.
Currently the customer login uses the base .phtml file.
So I have created the customer/form/login.phtml file and placed it in my CUSTOM theme folder.
Then in my custom theme folder I went into layouts and and customer.xml. This is where in not sure what I need to do.
I found the following XML code:
<customer_account_login translate="label">
<label>Customer Account Login Form</label>
<!-- Mage_Customer -->
<remove name="right"/>
<remove name="left"/>
<reference name="root">
<action method="setTemplate"><template>page/1column.phtml</template></action>
</reference>
<reference name="content">
<block type="customer/form_login" name="customer_form_login" template="customer/form/login.phtml"/>
</reference>
</customer_account_login>
Im not sure what I need to change with this to make it use my custom login form instead of using the base login form.
At first I thought the system would automatically check to see if the file exists in custom and just apply and if it doesnt exist fall back on base template but that didnt seen to work.
Any help would be appreciated. A noob explanation would also be great!
Thanks for reading
Magento seems to use a login file from:
template/persistent/checkout/onepage/login.phtml
In version 1.6 of Magento.
Edited that and the changes appeared as expected. Sorry but i also just found this post
In Magento 1.6, changes to login.phtml don’t reflect
Mine seems to be a dupe (sorry I didnt come across it when searching before) so feel free to close this one :)
Related
I am a newcomer to magento. During the learning process, I want to know how to add a block to the bundled product page. The piece of information I found through google doesn't know what to do with it.
It depends on where you want to put it, and I am assuming that you have a theme setup with a local.xml file, but you could also add that part in the product's edit page in Admin->Manage Products->Edit Product->Design->Custom Layout Update.
The xml, added in app/design/frontend/[your-theme]/[your-subtheme]/layout/local.xml
<PRODUCT_TYPE_bundle>
<reference name="content">
<block name="yourtheme_yoursubtheme_nameofblock" type="core/text" template="path/to/your/template.phtml" />
</reference>
</PRODUCT_TYPE_bundle>
This will add the output of app/design/frontend/[your-theme]/[your-subtheme]/template/path/to/your/template.phtml at the bottom of every bundle-type product page. You may want to read up on Magento Layout XML
I am using magento 1.8.1. i want left side column on customer account page, but when i enable it, all the content of left column is shown here. i want only account related content on this page, but when i disable other content it is disable from other pages also.
so please tell me how to disable unnecessary content left side column for account page only.
This section is created from yourtheme/layout files..
So, go to xml files and comment or remove code..
That should help.
for shop by brand go to app/design/frontend/yourpackage/yourtheme/layout/manufacturer.xml file and comment below code bydefault this file in app/design/frontend/base/default/layout/manufacturer.xml
so if you find this file in your base directory pls copy this into your theme so dont face any problem at the time of magento up-gradation
<block type="manufacturer/navigation" name="manufacturer.navigation.left" after="sidenav">
<action method="setTemplate" ifconfig="manufacturer/sidebar/enabledleft">
<template>manufacturer/navigation/brands_nav.phtml</template>
</action>
</block>
for remove from account page go to customer.xml file and add this code
<reference name="left"> <remove name="manufacturer.navigation.left"/> </reference>
Ok I've checked everywhere including here and everyone's answers is exactly what I have written down so I have no idea why it's not working.
I cleared Magento's cache besides the configuration..
This is what I have in my local.xml file:
<layout>
<default>
<!-- Remove callouts and rarely used stuff -->
<remove name="right.poll" />
<remove name="right.permanent.callout" />
<remove name="left.permanent.callout" />
<!-- Add the local stylesheet -->
<reference name="root">
<action method="setTemplate"><template>page/1column.phtml</template></action>
</reference>
</default>
</layout>
I deleted the other css stuff I had written since my only concern is the root reference.
My directories look like:
simplistic
layout
local.xml
template
page
html
footer.phtml
header.phtml
etc (all other layout subthings)
1column.phtml
What exactly am I doing wrong? It's still using the 2 column layout when I'm trying to make it use the 1 column..
EDIT:
For anyone curious on the page, here is the page:
http://magento.neofill.com/magento/
You would think after editing local.xml in the default, that would affect all pages right? I don't get what I'm doing wrong. I keep searching and everything is exactly the way I have it. It should be working but if you view the source code, you'll see that it's using the 2 column layout here:
<div class="main-container col2-right-layout">
I'm making some changes to /customer/form/register.phml but they are not showing up in the frontend. Changes that I made to login.phtml and forgotpassword.phtml do show up.
I checked if magento was using a fallback from the base/default theme but it's not. I deleted register.phtml in both my theme and in the base/default theme to check what would happen: the page showed up just fine (without the changes of course).
I looks like magento gets the file from somewhere else (maybe the core). I've got no idea on how to solve this.
Thanks in advance for your help.
My Customer.xml file looks like this, I'm using magento 1.5.1
<customer_account_create translate="label">
<label>Customer Account Registration Form</label>
<remove name="right"/>
<remove name="left"/>
<reference name="root">
<action method="setTemplate"><template>page/1column.phtml</template></action>
</reference>
<reference name="content">
<block type="customer/form_register" name="customer_form_register" template="customer/form/register.phtml">
<block type="page/html_wrapper" name="customer.form.register.fields.before" as="form_fields_before" translate="label">
<label>Form Fields Before</label>
</block>
</block>
</reference>
</customer_account_create>
The best way to debug this - is to turn on template path hints.
You probably need to edit template/persistent/customer/form/register.phtml.
Yes i agree with WebFlake turn on template hints that will let you know which template file the form is being pulled from, most likely you are modifying the wrong template.
Here is a link which explains how to turn on template hints: http://vimeo.com/1067069
Use the template hints. Also, with any phtml changes you make, make sure that you have caching disabled, and flush all caches (System -> Cache Management).
I used template hints and discovered a plugin replaced the file. Enabling template hints: http://vimeo.com/1067069 helped a lot
I have edited the customer.xml file to add a new link to the dashboard page. I added the following line
<action method="addLink" translate="label" module="customer"><name>newpage</name><path>customer/newpage/</path><label>My New Page</label></action>
I've also added the following block to customer.xml
<customer_newpage_index translate="label">
<label>Customer My newpage</label>
<!-- Mage_Customer -->
<update handle="newpage"/>
<reference name="my.account.wrapper">
<block type="customer/newpage" name="newpage" before="-" template="customer/newpage.phtml"/>
</reference>
</customer_newpage_index>
And added a template file at template/customer/newpage.phtml
The link displays, but I get a 404 page when I view /customer/newpage/
What am I missing here?
Thanks
You need to add a controller called NewpageController.php and in it have an action called indexAction. It is probably not a good idea to add this controller inside of the Customer module, because that is in core, and we never touch core. Instead, what you probably want to do is create your own module and put the controller inside of that. It can still be added as one of the links to the sidebar like you have done, but from the outside so that when you upgrade Magento you won't lose your controller.