Magento Resource | E-Commerce Generation Explorer

TAG | design

If you need to change the footer copyright notification use the next instruction:

1. Open the Magento admin panel
2. Select the “System” tab
3. Click the “Configuration” menu item
4. Select the “Design” menu item
5. Click the “Footer” tab. Here you can change the copyright notification
6. With that done, click the “Save Configure” button.

· ·

Adding and removing javascript / css when and where you need it

Adding and removing Javascript and CSS is handled separately within Magento.

CSS is added in the usual like . But any included javascript (unless linked to “by hand” from a theme’s skin) is pulled via a php files which reads through the “js” folder in the root directory (root/js/index.php is responsible for this).

That is all well and good for Magento. The real question is how we, as developers, add these items when we need them.
In this post, we will show how to add and remove Javascript and CSS to a CMS page (and anywhere else) that you may need.
(more…)

· · ·

Jul/09

26

Magento Showcase

Here are some sites developed by MAGENTO.

www.londonoflinks.co.uk/

www.inspiredoffice.co.uk

www.whiteboardstore.co.uk

www.grasscity.com/

www.gap.com/

www.kapitolreef.com

www.Gutes-Guenstiger.com

www.billetgrillpro.com/
(more…)

· ·

Here is a tutorial for how to add login form on the Home page.

Open customer.xml from layout folder, and find (around line 91)

1
2
3
<reference name=”content”>
<block type=”customer/form_login” name=”customer_form_login” template=”customer/form/login.phtml”></block>
</reference>

Then open cms.xml and find (around line 46)

1
2
3
<reference name=”content”>
<block type=”cms/page” name=”cms_page”></block>
</reference>

(more…)

· · ·

Jun/09

25

What’s in a block?

Many developers are familiar with the MVC (Model View Controller) design pattern that is seemingly ubiquitous throughout web frameworks. Looking through the code in Magento, however, we see many other components besides the M’s the V’s and the C’s.

Each module  (a “module” meaning the separate directories within the “app/code/core/Mage” directory that comprise of Magento’s different functional areas) contains the usual Controller and Model. You’ll see that within each module, there are no Views (more on this later). You’ll also see extra tidbits, such as “helper” , “etc” and “sql”. These are (and are not) standard within the Zend Framework context and will not be discussed in this article. In these modules are also the sort of files which we work with very often. The all powerful block! This article will attempt to (hopefully accurately) describe just what a Block is and how it’s used.

A top priority of (good) Object Oriented Programming is the decoupling of code. In a nut shell, this means that code should have the least amount of dependency on other code as possible. (Slightly more accurately, objects should not rely too heavily on other objects to exist and function). Blocks are part of Magento’s solution to keep their application loosely coupled.

(more…)

·

For Footer Area, we need edit two different locations.
One part is a static block which created within the magento admin area (CMS > Static Block).

The other part is held as .phtml / .php / .xml files within the design files.

XML files location:
app/design/frontend/*/*/layout/page.xml

Here you will find some footer reference:

1
2
3
4
<block type="page/html_footer" name="footer" as="footer" template="page/html/footer.phtml">
<block type="page/switch" name="store_switcher" as="store_switcher" template="page/switch/stores.phtml"></block>
<block type="page/template_links" name="footer_links" as="footer_links" template="page/template/links.phtml"></block>
</block>

Another XML files location:
app/design/frontend/*/*/layout/cms.xml

(more…)

· ·

Theme Design by devolux.nh2.me