Search Results

either move your store views onto store group level to free up one level of the fallback or observe some event that triggers early enough but after config has already been loaded and replace the design/theme …

You shall move the templates of those extensions to either base/default theme or the theme you purchased. … I recommend the base/default theme because it will will work in case you will change theme again. …

The quick search brought up a usage in /app/design/frontend/base/default/template/page/html/notices.phtml

UPDATE To remove the wrapper "correct" way within local.xml file of your custom theme you have to move cms_page block directly to content block using unsetChild/remove routine and then removecms.wrapper …

Either put your slider into the template/page/html/header.phtml of your theme and then wrap it into the "if" clause which will check if the current page is home or not. … Modify template/page/2columns-left.phtml of your theme calling a new block between header and main content area. …

You have to put the following code as a layout update: <reference name="left"> <block type="catalog/layer_view" name="catalog.leftnav" before="-" template="catalog/layer/view.phtml"/> </reference …

4 x 4 = 16 {{block type="catalog/product_list" column_count="4" category_id="4" limit="16" template="catalog/product/featured.phtml"}}

Also it will make sense to execute your custom code on page load. For prototype: Event.observe(document, 'dom:loaded', function() { ... }); For jQuery: jQuery(document).ready(function() { …

Block can always be referenced by name. Alias (as) is used to simplify the long name of a block and the only differs with the scope. Name has to be unique within the page and alias within a parent blo …

So now you can set a custom theme for any customer group through xml: <?xml version="1.0" encoding="UTF-8"? … > <layout> <customer_group_wholesale> <reference name=”root”> <action method=”setTheme”><theme>modern</theme></action> </reference> </customer_group_wholesale> </layout …

SASS and Compass are not intended to make your website responsive. There are some other frameworks which are doing so (Twitter Bootstrap, Zurb Foundation, Skeleton etc). However I personally don't re …

If the translations are not module specific put it plain "text":"text" into the translate.csv of your theme. … It will exclude module dependencies and will also make your theme re-distributable with translations. …

Phil is absolutely right but theoretically there is a workaround (not that pretty though). You can create a custom module which will introduce the layout update. Then in the module you can check if t …

This can be done either within your theme or layout updates in admin panel like this: <reference name="head"> <action method="addItem"><type>skin_css</type><name>below_ie7.css</name></action> </reference …