Magento’s admin panel uses the exact same design pattern as the frontend (layouts + blocks + templates). If you’ve ever done any modifications to the Magento admin panel, you’ve probably tried to turn on template/block hints for the admin panel. The only problem is, Magento doesn’t have built-in support for this. I did some digging around and found out how to enable block hints in Admin Panel.

Step 1 – Connect to database

Using your favorite database administration tool, connect to your Magento database. These are tools I’ve used and recommend: phpMyAdmin (free).

Step 2 – Enter values into ‘core_config_data’ table

// for first time

INSERT INTO core_config_data (scope, scope_id, path, value)
VALUES ('default', 0, 'dev/debug/template_hints', 1),
('default', 0, 'dev/debug/template_hints_blocks', 1);

// second time you just need to update the inserted records
// to enable 
UPDATE core_config_data set value = 1 where scope = 'default' and scope_id = 0 and path ='dev/debug/template_hints'

// to disable
UPDATE core_config_data set value = 0 where scope = 'default' and scope_id = 0 and path ='dev/debug/template_hints'

The post Enable Template or Block Hints in Admin Panel appeared first on Raise Review.

//If you need do it from frontend - add line Mage::registry('isSecureArea'); before this code.

//#add Website
    /** @var $website Mage_Core_Model_Website */
    $website = Mage::getModel('core/website');
    $website->setCode('<your_website_code_here>')
        ->setName('<your_website_name>')
        ->save();

//#add StoreGroup
    /** @var $storeGroup Mage_Core_Model_Store_Group */
    $storeGroup = Mage::getModel('core/store_group');
    $storeGroup->setWebsiteId($website->getId())
        ->setName('<your_store_name>')
        ->setRootCategoryId('<needed_root_category_id>')
        ->save();

//#add Store
    /** @var $store Mage_Core_Model_Store */
    $store = Mage::getModel('core/store');
    $store->setCode('<your_store_view_code_here>')
        ->setWebsiteId($storeGroup->getWebsiteId())
        ->setGroupId($storeGroup->getId())
        ->setName('<your_store_view_name>')
        ->setIsActive(1)
        ->save();

The post magento create store programmatically appeared first on Raise Review.

Magento collect all the config data from different modules and combine it all into a single file named system config.xml

To view this file simply paste this code in any controllers, run it and see the magic. A huge tree with lots of nodes.

It will show whole generated magento system config in xml format

<?php
echo $config = Mage::getConfig()
->loadModulesConfiguration('config.xml')
->getNode()
->asXML();
die;
?>

The post View all magento system config xml appeared first on Raise Review.

You sometimes need to retrieve Magento url / path like the website base URL or the media directory path on the server. Magento brings us 2 functions allowing to do that easily.

For web adresses you need to use Mage::getBaseUrl() with the link type in parameter. The types are described in the model Mage_Core_Model_Store

const URL_TYPE_LINK = 'link';
const URL_TYPE_DIRECT_LINK = 'direct_link';
const URL_TYPE_WEB = 'web';
const URL_TYPE_SKIN = 'skin';
const URL_TYPE_JS = 'js';
const URL_TYPE_MEDIA = 'media';

So we have

Mage::getBaseUrl(Mage_Core_Model_Store::URL_TYPE_LINK)

http://www.domain.com/index.php/

http://www.domain.com

http://www.domain.com/skin/

http://www.domain.com/js/

http://www.domain.com/media/

To get a directory path you need to use Mage:::getBaseDir() with the
directory code in parameter. The following table show all the available

The post Magento Urls & Paths appeared first on Raise Review.

I wanted to write this up for my own reference, but I hope this ends up helping you to. At the time of writing this, all of these methods have been tested on 1.4.0. This post assumes you to have familiarity with writing Magento modules. And remember, you only need to include functions in your file that you are modifying. Leave all untouched functions out of your file.

Also, the reason I haven’t included much for examples of the actual block/model code is that 90% of getting a rewrite to work correctly is just getting your config.xml correct. It matters way less of where you put your files in your module (though it’s good to keep it organized and clean).

Overriding Core Blocks

One of the more simple and straight-forward things to override in Magento. Let’s say that you want to override the following class: Mage_Catalog_Block_Product_View.

The first step is to copy the file into your own module’s Block folder. It can be anywhere you want within that folder, it really doesn’t matter. But, for organizational purposes, it’s always best, in my opinion, to keep a similar folder/file structure as Magento does. In this case, I would put this file in My/Module/Block/Catalog/Product/View.php. Of course, you’ll need to rename the class, and have it extend Mage_Catalog_Block_Product_View.

Here is how the ‘blocks’ tag in your config.xml should look:

<blocks>
    <my_module>
        <class>My_Module_Block</class>
    </my_module>
    <catalog>
        <rewrite>
            <product_view>My_Module_Block_Catalog_Product_View</product_view>
        </rewrite>
    </catalog>
</blocks>

As you can see, we’ve got the rewrite xml inside of the ‘catalog’ tag. This refers to app/code/core/Mage/Catalog/. Then the ‘rewrite’ tag tells Magento that we are going to override a block (since we are within the ‘blocks’ tag) under Mage/Catalog/. The ‘product_view’ tag points to Mage/Catalog/Block/Product/View.php, and within that tag is the name of the class that we are using to override the core block.

As another example, if you wanted to override Mage/Catalog/Block/Product/View/Type/Simple.php, the tag under ‘rewrite’ would be ‘product_view_type_simple’.

Overriding Core Models

Overriding models (but not resource models, which are anything declared in config.xml as ‘resourceModel’, which are typically files within a Mysql4 directory) is basically the same as blocks (above). So, I will give an example, but leave out much of the explanation.

Lets say that I want to modify the model for the items on an order invoice (Mage_Sales_Model_Order_Invoice_Item). I will copy that file to My/Module/Model/Sales/Order/Invoice/Item.php, rename the class, and extend Mage_Sales_Model_Order_Invoice_Item.

The config.xml ‘models’ will look something like this:

<models>
    <my_module>
        <class>My_Module_Model</class>
    </my_module>
    <sales>
        <rewrite>
            <order_invoice_item>My_Module_Block_Sales_Order_Invoice_Item</order_invoice_item>
        </rewrite>
    </sales>
</models>

Overriding Core Resource Models

I found out the hard way once, and wasted a couple hours, that resource models have a different way of overriding them. All of the concepts are the same, with the exception of the syntax in your config.xml file. A resource model is typically going to be models that reside within a ‘Mysql4′ folder. The resource model folder is typically defined in the config.xml file using the tag ‘resourceModel’.

I was putting together a dependent filter module, and I needed to override this class: Mage_Catalog_Model_Resource_Eav_Mysql4_Attribute. Just as the above examples, I created this file: My/Module/Model/Catalog/Resource/Eav/Mysql4/Attribute.php, renamed the class, and extended Mage_Catalog_Model_Resource_Eav_Mysql4_Attribute.

As I said above, the xml syntax changes for resource models. Instead of defining just the ‘catalog’ tag right before the ‘rewrite’, you actually have to define all the way down to the mysql4 folder. Here is an example for the above model:

<models>
    <my_module>
        <class>My_Module_Model</class>
    </my_module>
    <catalog_resource_eav_mysql4>
        <rewrite>
            <attribute>My_Module_Model_Catalog_Resource_Eav_Mysql4_Attribute</attribute>
        </rewrite>
    </catalog_resource_eav_mysql4>
</models>

Overriding Admin Core Controllers

I have seen numerous methods on how to do this, but the method I will describe seems to be the current ‘standard’.

Lets say that I need to override the adminhtml attribute controller: Mage_Adminhtml_Catalog_Product_AttributeController. First thing is to create the controller in your module. I would put mine in My/Module/controllers/Catalog/Product/AtttributeController.php. An important key to note here is that with controllers, Magento does not autoload them like it does with blocks and models. So, we’ll need to include the file of the controller that we want to override. Here is an example of how my controller would look:

<?php
include_once("Mage/Adminhtml/controllers/Catalog/Product/AttributeController.php");
class My_Module_Catalog_Product_AttributeController extends Mage_Adminhtml_Catalog_Product_AttributeController
{
...

The config.xml file is key now. Unlike models and blocks, you don’t need to define exactly which/where controller you are needing to override. You just need to define whether it is an ‘admin’ or ‘frontend’ controller, which module has the controller(s) you are overriding, and which module you are overriding it with (your own, obviously).

Here is the example for the above controller:

<config>
    <admin>
        <routers>
            <adminhtml>
                <args>
                    <modules>
                        <my_Module before="Mage_Adminhtml">My_Module</my_Module>
                    </modules>
                </args>
            </adminhtml>
        </routers>
    </admin>
</config>

Overriding Frontend Core Controllers

Lets override the Onepage Checkout controller: Mage_Checkout_OnepageController. First thing is to create the controller in your module. I would put mine in My/Module/controllers/Checkout/OnepageController.php. An important key to note here is that with controllers, Magento does not autoload them like it does with blocks and models. So, we’ll need to include the file of the controller that we want to override. Here is an example of how my controller would look:

<?php
include_once('Mage/Checkout/controllers/OnepageController.php');
class My_Module_Checkout_OnepageController extends Mage_Checkout_OnepageController
{
...

The config.xml file is key now. Unlike models and blocks, you don’t need to define exactly which/where controller you are needing to override. Unlink overriding an admin controller, here will will put our router info inside the ‘frontend’ tags.

Here is the example for the above controller:

<config>
    <frontend>
        <routers>
            <checkout>
                <args>
                    <modules>
                         <My_Module before="Mage_Checkout">My_Module_Checkout</My_Module>
                    </modules>
                </args>
            </checkout>
        </routers>
    </frontend>
</config>

Please feel free to ask questions or provide feedback on this post. If there are any errors or better ways to do any of this, please let me know.

The post Magento overriding core files (Blocks, Models, Resources, Controllers) appeared first on Raise Review.

customized tinymce magento

In magento admin we always need to remove some buttons from magento tinymce.

also while we add tinymce in our custom module at that time we can also customize the magento tinymce view. here is the way to magento customize tinymce. while adding magento field as magento tinymce..

add below code in /js/mage/adminhtml/wysiwyg/tiny_mce/setup.js at bottom of the file

tinyMceWysiwygSetup.prototype.oldGetSettings = tinyMceWysiwygSetup.prototype.getSettings;

tinyMceWysiwygSetup.addMethods({
    getSettings: function(mode) {
        var settings = this.oldGetSettings(mode);

        if (this.config.theme_advanced_buttons1 != undefined) {
            settings.theme_advanced_buttons1 = this.config.theme_advanced_buttons1;
        }

        if (this.config.theme_advanced_buttons2 != undefined) {
            settings.theme_advanced_buttons2 = this.config.theme_advanced_buttons2;
        }

        if (this.config.theme_advanced_buttons3 != undefined) {
            settings.theme_advanced_buttons3 = this.config.theme_advanced_buttons3;
        }

        if (this.config.theme_advanced_buttons4 != undefined) {
            settings.theme_advanced_buttons4 = this.config.theme_advanced_buttons4;
        }

        return settings;
    }
});

now its time to add your customized editor field with magento tinymce field type

$wysiwygConfig = Mage::getSingleton('cms/wysiwyg_config')->getConfig(
            array(
                    'add_widgets' => false,
                    'add_variables' => false,
                    'add_images' => false,

                    'files_browser_window_url'=> $this->getBaseUrl().'admin/cms_wysiwyg_images/index/',
                    'theme_advanced_buttons1' => 'bold,italic,underline,strikethrough,separator,justifyleft,justifycenter,justifyright,justifyfull,separator,bullist,numlist,separator,outdent,indent,separator,link,unlink,image,anchor,separator,cut,copy,paste,pastetext,pasteword',
                    'theme_advanced_buttons2' => '',
                    'theme_advanced_buttons3' => '',
                    'theme_advanced_buttons4' => '',
			)
        );

$contentField = $fieldset->addField('content', 'editor', array(
    'name'      => 'content',
    'style'     => 'height:36em;',
    'required'  => true,
    'config'    => $wysiwygConfig
));

Conclusion is to add some buttons by passing values in array. and also we can remove image upload and widget and vaiables insert..

The post Magento customize tinymce appeared first on Raise Review.

<?php
$string = "string containing # and @ and other non alpha characters";
$clean_string = preg_replace("/[^a-z0-9\s]/", "", $string);
?>

The post Remove non alphanumeric characters from string appeared first on Raise Review.

Below is full list of magento form validate class and its error message that I found in prototype lib.

* validate-select

Please select an option.

* required-entry

This is a required field.

* validate-number

Please enter a valid number in this field.

* validate-digits

Please use numbers only in this field. please avoid spaces or other characters such as dots or commas.

* validate-alpha

Please use letters only (a-z or A-Z) in this field.

* validate-code

Please use only letters (a-z), numbers (0-9) or underscore(_) in this field, first character should be a letter.

* validate-alphanum

Please use only letters (a-z or A-Z) or numbers (0-9) only in this field. No spaces or other characters are allowed.

* validate-street

Please use only letters (a-z or A-Z) or numbers (0-9) or spaces and # only in this field.

* validate-phoneStrict

Please enter a valid phone number. For example (123) 456-7890 or 123-456-7890.

* validate-phoneLax

Please enter a valid phone number. For example (123) 456-7890 or 123-456-7890.

* validate-fax

Please enter a valid fax number. For example (123) 456-7890 or 123-456-7890.

* validate-date

Please enter a valid date.

* validate-email

Please enter a valid email address. For example abc@example.com.

* validate-emailSender

Please use only letters (a-z or A-Z), numbers (0-9) , underscore(_) or spaces in this field.

* validate-password

Please enter 6 or more characters. Leading or trailing spaces will be ignored.

* validate-admin-password

Please enter 7 or more characters. Password should contain both numeric and alphabetic characters.

* validate-cpassword

lease make sure your passwords match.

* validate-url

Please enter a valid URL. http:// is required

* validate-clean-url

Please enter a valid URL. For example http://www.example.com or www.example.com

* validate-identifier

Please enter a valid Identifier. For example example-page, example-page.html or anotherlevel/example-page

* validate-xml-identifier

Please enter a valid XML-identifier. For example something_1, block5, id-4

* validate-ssn

Please enter a valid social security number. For example 123-45-6789.

* validate-zip

Please enter a valid zip code. For example 90602 or 90602-1234.

* validate-date-au

Please use this date format: dd/mm/yyyy. For example 17/03/2006 for the 17th of March, 2006.

* validate-currency-dollar

Please enter a valid $ amount. For example $100.00.

* validate-one-required

Please select one of the above options.

* validate-one-required-by-name

Please select one of the options.

* validate-not-negative-number

Please enter a valid number in this field.

* validate-state

Please select State/Province.

* validate-new-password

Please enter 6 or more characters. Leading or trailing spaces will be ignored.

* validate-greater-than-zero

Please enter a number greater than 0 in this field.

* validate-zero-or-greater

Please enter a number 0 or greater in this field.

* validate-cc-number

Please enter a valid credit card number.

* validate-cc-type

Credit card number doesn\’t match credit card type

* validate-cc-type-select

Card type doesn\’t match credit card number

* validate-cc-exp

Incorrect credit card expiration date

* validate-cc-cvn

Please enter a valid credit card verification number.

* validate-data

Please use only letters (a-z or A-Z), numbers (0-9) or underscore(_) in this field, first character should be a letter.

* validate-css-length

Please input a valid CSS-length. For example 94px or 57pt or 14em or .5ex or 50%

* validate-length

Maximum length exceeded.

The post Magento form validation with css class appeared first on Raise Review.

We can use these events for our requirement.

I am describing here a way to use it. An example would be the event ‘checkout_onepage_controller_success_action’ (this has been use by me at many instances) which will be raised by Magento immediately after an order is placed succesfully. There are many events used in Magento, you can use them as per your requirement.

Event An Event is something that occurs in a certain place during a particular sequence flow.

Observer An Observer is an event handler. It listens to any event it is attached to and accordingly reacts to the event.

I am assuming you are familiar with devloping an module.

Lets begin.
1) I am using the event found in ‘/app/code/core/Mage/Checkout/controllers/OnepageController.php’ in function ‘successAction()’ line no 243. below is a syntax which which dispatch event.

Mage::dispatchEvent('checkout_onepage_controller_success_action', array('order_ids' => array($lastOrderId)));

You can also create a custom event, only thing is you need to maintain the namespace.

2) Register the event with its Observer.
In the config file of your module (mine module path app/code/local/DW/Ordercustomer/etc/config.xml), please copy the following code
Suppose my module is ‘XYZmodule’, and ‘saveCustomerInfo’ this is the method to be called on order success

<?xml version="1.0"?>
<config>
<global>
    <!-- for observer-->
    <!--start-->
    <events>           
        <checkout_onepage_controller_success_action>
            <observers>
                <xyzmodule>
                    <class>dw/observer</class>
                    <method>saveCustomerInfo</method>
                </xyzmodule>
            </observers>
        </checkout_onepage_controller_success_action>                 
    </events>      
    <!--end-->
</global>
</config>

3) Create an observer.
My directory structure – app/code/local/DW/Ordercustomer/Model/. Create a file Observer.php here.

Paste the below mentioned code.

<?php

class ABCnamespace_XYZmodule_Model_Observer 
{    
    public function saveCustomerInfo($observer) 
    {       
        $order_ids = $observer->getEvent()->getOrderIds(); //$order_ids is the array containg the od of the order placed
        //your code goes here       
        return $this; 
    }
}

That’s it…

below i have defined a whole magento event and observer cheat sheet table.

The post Magento event and observer cheat sheet appeared first on Raise Review.

What’s the use of store emulator?

When a process run on backend for example cron jobs or email notifications, these processes work under admin store. No problem, but what if these codes need different store themes. For example product alert emails need to send store wise.

So each time a mail is sent it grabs the template from store view of the Emulated Store.

app/design/frontend/default/store1_theme/template/email/custom-email-block.phtml, for first store

app/design/frontend/default/store2_theme/template/email/custom-email-block.phtml for second store and so on.

So in that case store emulator play a very crucial role and help to create the store environment on the fly.

To emulate any store just copy the given code in any controller with specific store id. below is the way to emulate magento store programmatically.

<?php
$appEmulation = Mage::getSingleton('core/app_emulation');
//Start environment emulation of the specified store
$initialEnvironmentInfo = $appEmulation->startEnvironmentEmulation($storeId);

//Emulation Started
//Run any code here and it will use the emulated store
//Stop environment emulation and restore original store
$appEmulation->stopEnvironmentEmulation($initialEnvironmentInfo);
?>

The post Emulate Magento store programmatically appeared first on Raise Review.