I was having trouble when i was developing my magento2 blog extension because i get stuck at the point when i need to use wysiwyg editor for magento2. It is little bit different then magento1 i guess.

Before we start i hope you all knows how to do magento2 grid with form. If you are not sure read this blog How to create a Magento2 Admin Grid

To make it work what i did is:-

Step1:-

Open your layout file. In my case it is located here:

Kdecom/Blog/view/adminhtml/layout.xml

<adminhtml_blog_blog_edit>
        <update handle="editor"/>
        <reference name="content">
            <block type="Kdecom_Blog_Block_Adminhtml_Blog_Edit"  name="blog.post.edit" />
        </reference>
</adminhtml_blog_blog_edit>

<update handle=”editor”/> tag included all necessary Java Script file related to Wysiwyg editor.

Only for reference. Do not add the below line in your xml.

If you want to know which file gets included in magneto admin. Here is the list ()

<editor>
        <reference name="head">
            <action method="setCanLoadExtJs"><flag>1</flag></action>
            <action method="addJs"><file>Mage_Adminhtml::variables.js</file></action>
            <action method="addJs"><file>mage/adminhtml/wysiwyg/widget.js</file></action>
            <action method="addJs"><file>lib/flex.js</file></action>
            <action method="addJs"><file>lib/FABridge.js</file></action>
            <action method="addJs"><file>mage/adminhtml/flexuploader.js</file></action>
            <action method="addJs"><file>mage/adminhtml/browser.js</file></action>
            <action method="addJs"><file>prototype/window.js</file></action>
            <action method="addCss"><file>prototype/windows/themes/default.css</file></action>
            <action method="addCss"><file>Mage_Core::prototype/magento.css</file></action>
        </reference>
    </editor>

Open your form.php file . In my case location of the file was:-

Kdecom/Blog/Block/Adminhtml/Blog/Edit/Form.php

Add this method.

protected function _prepareLayout() {
        parent::_prepareLayout();
        if (Mage::getSingleton('Mage_Cms_Model_Wysiwyg_Config')->isEnabled()) {
            $this->getLayout()->getBlock('head')->setCanLoadTinyMce(true);
        }
    }

Here is the code to add the element

$fieldset->addField(
                'post_content', 'editor', array(
            'label' => $this->__('Post Content'),
            'class' => 'required-entry',
            'style' => 'width:725px;height:460px',
            'required' => true,
            'force_load' => true,
            'config' => Mage::getSingleton('Mage_Cms_Model_Wysiwyg_Config')->getConfig($config)
                )
        );

As a Zend Framework developer i was thinking it why magento using Editor as an element but not the TextArea so just in that case i would like to say magento has list of the Element that you can use in your form.

Here is the list of the magento element that you can use in your magento form.

• Button
• Checkbox
• Checkbboxes
• Collection
• Column
• Date
• EditableMultiSelect
• Editor
• Fieldset
• File
• Gallery
• Hidden
• Image
• ImageFile
• Label
• Link
• Multiline
• MultiSelect
• Note
• Obscure (not sure what is it)?
• Password
• Radio
• Radios
• Reset
• Select
• Submit
• Text
• Textarea
• Time

I hope that helps.

The post How to use Wysiwyg editor in magento2 appeared first on Kdecom.

Some tips and tricks for the magento Developer:-

$this->getSkinUrl()

Replace with in magento2

$this->getViewFileUrl()

The post Magento2 Developer Tips and trick appeared first on Kdecom.

When i was developing magento2 extension it is always good to turn off url rewrite in magento.

What is the difference between turn on url rewrite and turn off url rewrite?

Turn On URL Rewrite PRODUCT PAGE:-

http://www.kdecom.com/mage2/index.php/living-room-furniture.html

Turn off URL Rewrite PRODUCT PAGE:-

http://www.kdecom.com/mage2/index.php/catalog/product/view/id/3/s/my-shoes-1/category/5/

If you have turn off magento2 url rewrite then you will know exactly which module and which controller and which action magento execute from above url you will know it will execute Mage_Catalog module, ProductController.php and viewAction from that file.

In magento2 admin panel:

store-> setting -configuation -> catalog -> catalog ->search engine optimization

And turn off the url rewrite.

Next i did went on front end and check it that is it working for me? But unfortunately answer was no.

So finally i have to open up PhpMyAdmin and check the magento2 core_url_rewrite table and all the data was inside the table.

then i did execute

TRUNCATE core_url_rewrite;

Now i went on frontend and it starts working.

Finally..

Simply if you want to turn off magento2 First thing you will do is:- turn off url rewrite in admin panel. Then you have to truncate the core_url_rewrite table from magento2 database.

The post How to turn off URL Rewrite in Mangeto2 appeared first on Kdecom.

Here is what i was doing it for my magento2 product question answer extension.

i need the list of the question for that particular product to displaying on the product page.

What we used to do in old magento version

$this->getCollection()
->addAttributeToFilter(‘product_id’, $id)
->addAttributeToFilter(‘status’, ‘published’)
;

but it didnt worked in magento2.

After doing some research of magento code i figure out instead of using addAttributeToFilter you should be using addFieldToFilter so i did replace it with

$this->getCollection()
->addFieldToFilter(‘product_id’, $id)
->addFieldToFilter(‘status’, ‘published’)
;

WORKED

I will come up with more as i will know more ..

The post How to use Magento2 Collection appeared first on Kdecom.

What i learn from this extension is…

• How admin Grid works
• Admin Layouts.
• how to add Menu in magento2 admin
• How to create a magento2 admin grid

Step1:- create a config file

app/code/Kdecom/Blog/eetc/config.xml with the code provided below.

<?xml version="1.0"?>
<config>
    <modules>
        <Kdecom_Blog>
            <version>1.0.0.0</version>
            <active>true</active>
        </Kdecom_Blog>
    </modules>
    <global>
        <resources>
            <blog_setup>
                <setup>
                    <module>Kdecom_Blog</module>
                </setup>
            </blog_setup>
        </resources>
    </global>
    <admin>
        <routers>
            <adminhtml>
                <args>
                    <modules>
                        <blog before="Mage_Adminhtml">Kdecom_Blog_Adminhtml</blog>
                    </modules>
                </args>
            </adminhtml>
        </routers>
    </admin>

    <frontend>
        <routers>
            <blog>
                <use>standard</use>
                <args>
                    <module>Kdecom_Blog</module>
                    <frontName>blog</frontName>
                </args>
            </blog>
        </routers>
        <layout>
            <updates>
                <blog module="Kdecom_Blog">
                    <file>layout.xml</file>
                </blog>
            </updates>
        </layout>
    </frontend>
    <adminhtml>
        <layout>
            <updates>
                <blog module="Kdecom_Blog">
                    <file>layout.xml</file>
                </blog>
            </updates>
        </layout>
    </adminhtml>
</config>

<Kdecom_Blog> <version>1.0.0.0</version> <active>true</active> </Kdecom_Blog>

The above code is just saying your module is enabled. If you set as false it will disable the blog module.

Step2:-

create your sql file:-

/app/code/Kdecom/Blog/sql/blog_setup/install-1.0.0.0.php with this code

<?php

$installer = $this;
/* @var $installer Mage_Core_Model_Resource_Setup */

$installer->startSetup();

$blogtable = $installer->getConnection()
    ->newTable($installer->getTable('kd_blog'))
    ->addColumn('post_id', Varien_Db_Ddl_Table::TYPE_INTEGER, null, array(
        'identity'  => true,
        'unsigned'  => true,
        'nullable'  => false,
        'primary'   => true,
        ), 'Post Id')
    ->addColumn('post_title', Varien_Db_Ddl_Table::TYPE_TEXT, 255, array(
        ), 'Post Title')
    ->addColumn('post_content', Varien_Db_Ddl_Table::TYPE_TEXT, '64k', array(
        ), 'Post Content')
    ->addColumn('post_status', Varien_Db_Ddl_Table::TYPE_TEXT, 25, array(
        ), 'Post Status')
    ->addColumn('created_datetime', Varien_Db_Ddl_Table::TYPE_DATETIME, null, array(
        ), 'Created Time')
    ->addColumn('update_datetime', Varien_Db_Ddl_Table::TYPE_DATETIME, null, array(
        ), 'Updated Time')
    ->addColumn('meta_keywords', Varien_Db_Ddl_Table::TYPE_TEXT, 512, array(
        ), 'Meta Keywords')
    ->addColumn('meta_description', Varien_Db_Ddl_Table::TYPE_TEXT, 512, array(
        ), 'Meta Keywords')
    ->addColumn('meta_title', Varien_Db_Ddl_Table::TYPE_TEXT, 512, array(
        ), 'Meta Keywords');
$installer->getConnection()->createTable($blogtable);

$commenttable = $installer->getConnection()
    ->newTable($installer->getTable('kd_blog_comment'))
    ->addColumn('comment_id', Varien_Db_Ddl_Table::TYPE_INTEGER, null, array(
        'identity'  => true,
        'unsigned'  => true,
        'nullable'  => false,
        'primary'   => true,
        ), 'Comment Id')
    ->addColumn('post_id', Varien_Db_Ddl_Table::TYPE_INTEGER, null, array(
        ), 'Post Id')
    ->addColumn('comment_content', Varien_Db_Ddl_Table::TYPE_TEXT, '64k', array(
        ), 'Comment Content')
    ->addColumn('comment_status', Varien_Db_Ddl_Table::TYPE_TEXT, 25, array(
        ), 'Comment Status')
    ->addColumn('user_name', Varien_Db_Ddl_Table::TYPE_DATETIME, null, array(
        ), 'User Name')
    ->addColumn('user_email', Varien_Db_Ddl_Table::TYPE_DATETIME, null, array(
        ), 'User Email');

$installer->getConnection()->createTable($commenttable);

$installer->endSetup();

Step3:- Now we are going to add a menu in magneto2 admin panel.

Add a file inside the /app/code/Kdecom/Blog/etc/adminhtml/menu.xml

<?xml version="1.0" encoding="UTF-8"?>
<config>
    <menu>
        <add id="Kdecom_Blog::marketing_adminuser_blog" title="Blog" 
             module="Kdecom_Blog" sortOrder="60" parent="Mage_Adminhtml::marketing"  
             resource="Kdecom_Blog::marketing_adminuser_blog"/>
        <add id="Kdecom_Blog::blog_post_list" title="Blogs Grid" module="Kdecom_Blog" sortOrder="40" 
             parent="Kdecom_Blog::marketing_adminuser_blog"
             action="adminhtml/blog_blog/index" resource="Kdecom_Blog::blog_post_list"/>       
    </menu>
</config>

Step4:- Add a controller file inside the

app/code/Kdecom/Blog/controllers/Adminhtml/Blog/BlogController.php

<?php

/**
 *
 * @category   Kdecom
 * @package    KD Manufacturer <www.kdecom.com>
 */
class Kdecom_Blog_Adminhtml_Blog_BlogController extends Mage_Adminhtml_Controller_Action {

    public function indexAction() {
        $this->_title($this->__('Blog Post List'))
                ->_title($this->__('Manage Post'));
        $this->loadLayout();
        $this->renderLayout();
    }
     public function newAction()
    {
        Mage::register('blog_action', 'new');
        $this->_forward('edit');
    }

    public function editAction() {

        $model = Mage::getModel('Kdecom_Blog_Model_Blog');
        $postId = (int) $this->getRequest()->getParam('post_id');
        if ($postId) {
            $model->load($postId);
        }
        $model->setData('update_datetime', date('Y-m-d H:m:s'));

        if ($model->getId()) {
            $data = Mage::getSingleton('Mage_Backend_Model_Session')->getFormData(true);
            if (!empty($data)) {
                $model->setData($data);
            }
        }
        Mage::register('current_blog', $model);

        $this->loadLayout()
                //->_setActiveMenu('system/api')
                ->_title(Mage::helper('Kdecom_Blog_Helper_Data')->__('Post'));

        if (Mage::registry('blog_action') == 'new') {
            $this->_title(Mage::helper('Kdecom_Blog_Helper_Data')->__('Add Post'));
        } else {
            $this->_title(Mage::helper('Kdecom_Blog_Helper_Data')->__('Edit Post'));
        }

        $this->renderLayout();
    }

    public function saveAction() {
        $data = $this->getRequest()->getPost();

        $model = Mage::getModel('Kdecom_Blog_Model_Blog');
        $postId = (int) $this->getRequest()->getParam('post_id');

        if ($postId) {
            $model = $model->load($postId);
        } 
        $model->setUpdateDatetime(date('Y-m-d H:m:s'));
        Mage::register('current_blog', $model);
        if ($data) {
            $model->setData($data);
            if($postId) {
                $model->setId($postId);
            } else {
                $model->setData('created_datetime', date('Y-m-d H:m:s'));
            }
            $model->setData('update_datetime', date('Y-m-d H:m:s'));

            try {
                $model->save();
                $this->_getSession()->addSuccess($this->__("The Post '%s' has been saved.", $model->getPostTitle()));
            } catch (Exception $e) {
                Mage::logException($e);
                $this->_getSession()->addError($e->getMessage());
            }
        } else {
            $this->_getSession()->addError($this->__("The Post '%s' has not been saved.", $model->getPostTitle()));
        }
        $this->_redirect('*/*/');
    }

    public function deleteAction() {
        $model = Mage::getModel('Kdecom_Blog_Model_Blog');

        $postId = (int) $this->getRequest()->getParam('id');
        if ($postId) {
            $model = $model->load($postId);
        }
        if ($model && !$model->getId()) {
            try {
                $model->delete();
                $this->_getSession()->addSuccess($this->__("The Post '%s' has been removed.", $model->getName()));
            }
            catch (Exception $e) {
                Mage::logException($e);
                $this->_getSession()->addError($e->getMessage());
            }
        }
        else {
            $this->_getSession()->addError($this->__("The Post '%s' can not be removed.", $model->getName()));
        }
        $this->_redirect('*/*/');
    }

}

Step5:- Add a Model file at /app/code/Kdecom/Blog/Model/Blog.php with the below code

<?php

class Kdecom_Blog_Model_Blog extends Mage_Core_Model_Abstract {

    public function _construct() {
        parent::_construct();
        $this->_init('Kdecom_Blog_Model_Resource_Blog');
    }
    public function getPostStatusOptions() {
        $status[] = array('label' => 'Please Select','value' => '');
        $status[] = array('label' => 'Draft','value' => 'draft');
        $status[] = array('label' => 'Published','value' => 'published');
        return $status;
    }

}

Next another Model file at  /app/code/Kdecom/Blog/Model/Resource/Blog.php

<?php

class Kdecom_Blog_Model_Resource_Blog extends Mage_Core_Model_Resource_Db_Abstract {

    public function _construct() {
        $this->_init('kd_blog', 'post_id');
    }

}

We need one more model file at :- app/code/Kdecom/Blog/Model/Resource/Blog/Collection.php

<?php

class Kdecom_Blog_Model_Resource_Blog_Collection extends Mage_Core_Model_Resource_Db_Collection_Abstract {

    public function _construct() {
        parent::_construct();
        $this->_init('Kdecom_Blog_Model_Blog', 'Kdecom_Blog_Model_Resource_Blog');
    }
}

Now we have to create some admin layout files:- app/code/Kdecom/Blog/view/adminhtml/layout.xml

<?xml version="1.0"?>

<layout>
    <adminhtml_blog_blog_index>
        <reference name="content">
            <block type="Kdecom_Blog_Block_Adminhtml_Blog" name="blog.post.list" />
        </reference>
    </adminhtml_blog_blog_index>

    <adminhtml_blog_blog_edit>
        <update handle="editor"/>
        <reference name="content">
            <block type="Kdecom_Blog_Block_Adminhtml_Blog_Edit"  name="blog.post.edit" />
        </reference>
    </adminhtml_blog_blog_edit>

</layout>

We have to create an empty helper file:-  /app/code/Kdecom/Blog/Helper/Data.php

<?php

class Kdecom_Blog_Helper_Data extends Mage_Catalog_Helper_Data {

}

So at last now we have to create 4 another Block files for grid to work…

Create first block file:- /app/code/Kdecom/Blog/Block/Adminhtml/Blog.php

<?php
class Kdecom_Blog_Block_Adminhtml_Blog extends Mage_Backend_Block_Widget_Grid_Container
{
    /**
     * @var string
     */
    protected $_blockGroup = 'Kdecom_Blog';

    /**
     * @var string
     */
    protected $_controller = 'adminhtml_blog';

    /**
     * Internal constructor.
     */
    protected function _construct()
    {
        parent::_construct();

        $this->_headerText      = $this->__('Blog Post');
    }
}

/app/code/Kdecom/Blog/Block/Adminhtml/Blog/Grid.php

<?php

class Kdecom_Blog_Block_Adminhtml_Blog_Grid extends Mage_Backend_Block_Widget_Grid_Extended {

    public function _construct() {
        parent::_construct();
        $this->setId('blogGrid');
        $this->setDefaultSort('id');
        $this->setDefaultDir('ASC');
        $this->setSaveParametersInSession(true);
    }

    protected function _prepareCollection() {
        $collection = Mage::getModel('Kdecom_Blog_Model_Blog')->getCollection();
        $this->setCollection($collection);
        return parent::_prepareCollection();
    }

    protected function _prepareColumns() {
        $this->addColumn('post_id', array(
            'header' => $this->__('Post Id'),
            'align' => 'right',
            'width' => '50px',
            'index' => 'post_id',
        ));

        $this->addColumn('post_title', array(
            'header' => $this->__('Title'),
            'align' => 'left',
            'index' => 'post_title',
        ));
        $this->addColumn('update_datetime', array(
            'header' => $this->__('Post Last Updated DateTime'),
            'align' => 'left',
            'index' => 'update_datetime',
        ));

        $this->addColumn('meta_title', array(
            'header' => $this->__('Meta Title'),
            'align' => 'left',
            'index' => 'meta_title',
        ));

        $this->addColumn('action', array(
            'header' => Mage::helper('Kdecom_Blog_Helper_Data')->__('Action'),
            'width' => '100',
            'type' => 'action',
            'getter' => 'getId',
            'actions' => array(
                array(
                    'caption' => Mage::helper('Kdecom_Blog_Helper_Data')->__('Edit'),
                    'url' => array('base' => '*/*/edit'),
                    'field' => 'post_id'
                )
            ),
            'filter' => false,
            'sortable' => false,
            'index' => 'stores',
            'is_system' => true,
        ));

        return parent::_prepareColumns();
    }

    public function getGridUrl() {
        return $this->getUrl('*/*/grid', array('_current' => true));
    }

    public function getRowUrl($row) {
        return $this->getUrl('*/*/edit', array('id' => $row->getId()));
    }

}

Next file app/code/Kdecom/Blog/BlockAdminhtml/Blog/Edit.php

<?php

class Kdecom_Blog_Block_Adminhtml_Blog_Edit extends Mage_Adminhtml_Block_Widget_Form_Container {

    protected function _construct() {
        $this->_objectId = 'id';
        $this->_blockGroup = 'Kdecom_Blog';
        $this->_controller = 'adminhtml_blog';

        parent::_construct();

        $this->getCanLoadTinyMce();
        $this->_updateButton('save', 'label', Mage::helper('Mage_Customer_Helper_Data')->__('Save Post'));
        $this->_updateButton('delete', 'label', Mage::helper('Mage_Customer_Helper_Data')->__('Delete Post'));
    }

}

Last file /app/code/Kdecom/Blog/Block/Adminhtml/Blog/Edit/Form.php

<?php

class Kdecom_Blog_Block_Adminhtml_Blog_Edit_Form extends Mage_Backend_Block_Widget_Form {

    protected function _prepareLayout() {
        parent::_prepareLayout();
        if (Mage::getSingleton('Mage_Cms_Model_Wysiwyg_Config')->isEnabled()) {
            $this->getLayout()->getBlock('head')->setCanLoadTinyMce(true);
        }
    }

    protected function _prepareForm() {

        $blogPost = Mage::registry('current_blog');
        $form = new Varien_Data_Form(
                        array(
                            'id' => 'edit_form',
                            'action' => $this->getUrl(
                                    '*/*/save', array('post_id' => $blogPost->getId())
                            ),
                            'method' => 'post'
                        )
        );

        $fieldset = $form->addFieldset('blog_fieldset', array('legend' => $this->__('Blog Post')));

        $fieldset->addField(
            'post_title', 'text', array(
            'label' => $this->__('Post Title'),
            'class' => 'required-entry',
            'required' => true,
            'name' => 'post_title',
                )
        );

        $fieldset->addField(
                'post_content', 'editor', array(
            'label' => $this->__('Post Content'),
            'class' => 'required-entry',
            'style' => 'width:725px;height:460px',
            'required' => true,
            'force_load' => true,
            'name' => 'post_content',
            'config' => Mage::getSingleton('Mage_Cms_Model_Wysiwyg_Config')->getConfig($config)
                )
        );

        $postStatus = array();
        $postStatus = Mage::getModel('Kdecom_Blog_Model_Blog')->getPostStatusOptions();
        $fieldset->addField('post_status', 'select', array(
            'label' => $this->__('Post Status'),
            'required' => true,
            'values' => $postStatus,
            'name' => 'post_status',
        ));

        $fieldset->addField('meta_title', 'text', array(
            'label' => $this->__('Meta Title'),
            'required' => false,
            'name' => 'meta_title'
        ));
        $fieldset->addField('meta_keywords', 'textarea', array(
            'label' => $this->__('Meta Keywords'),
            'required' => false,
            'style' => 'width:725px;height:200px',
            'name' => 'meta_keywords',
            'values' => $postStatus,
        ));
        $fieldset->addField('meta_description', 'textarea', array(
            'label' => $this->__('Meta Description'),
            'style' => 'width:725px;height:200px',
            'name' => 'meta_description',
            'required' => false
        ));

        $values = $blogPost->getData();
        $form->setUseContainer(true);
        $form->setValues($values);
        $this->setForm($form);
        return parent::_prepareForm();
    }

}

Now you can try to login into the admin panel and you will be able to see the menu under marketing with Blog. Click on Grid
You will be able to see the Post Grid.

The post How to create a Magento2 Admin Grid appeared first on Kdecom.

Why do i learn from this extension?

Light box extension helps magento2 developer to get more knowledge about how to use magento system data and layout. and important how to over ride a magento layout with your own template.

Now we start Developing Extension

Before we start i will show you the folder and files to make this extesion.

Lets Start now….

Step1:-  First create a config.xml file inside the Kdecom/Lightbox/etc/config.xml

<?xml version="1.0"?>
<config>
    <modules>
        <Kdecom_Lightbox>
            <version>1.0.0.0</version>
            <active>true</active>
        </Kdecom_Lightbox>
    </modules>
    <frontend>
        <layout>
            <updates>
                <lightbox module="Kdecom_Lightbox">
                    <file>layout.xml</file>
                </lightbox>
            </updates>
        </layout>
    </frontend>
</config>

Step 2:- Create a file called system.xml inside the Kdecom/Lightbox/etc/adminhtml/system.xml

<?xml version="1.0" encoding="UTF-8"?>
<config>
    <system>
        <section id="catalog">
            <group id="lightbox" translate="label" type="text" sortOrder="1" showInDefault="1" showInWebsite="1" showInStore="1">
                <label>Kdecom Lightbox</label>
                <field id="enable" translate="label comment" type="select" sortOrder="10" showInDefault="1" showInWebsite="0" showInStore="1">
                    <label>Enable</label>
                    <comment>Change Yes and No to Enable or Disable the Lightbox effect on Product Page</comment>
                    <source_model>Mage_Backend_Model_Config_Source_Yesno</source_model>
                </field>
            </group>
        </section>
    </system>
</config>

Step3:- Create a layout.xml file inside the Kdecom/Lightbox/view/frontend/layout.xml

<?xml version="1.0"?>
<layout version="0.1.0">

    <default>
        <reference name="head">
            <action method="addCSs">
                <name>Kdecom_Lightbox::css/lightbox.css</name>
            </action>
            <action method="addJs">
                <name>Kdecom_Lightbox::js/lightbox.js</name>
            </action>
        </reference>
    </default>
    <catalog_product_view>
        <reference name="product.info.media">
            <action method="setTemplate">
                <template>Kdecom_Lightbox::lightbox/media.phtml</template>
            </action>
        </reference>
    </catalog_product_view>    
</layout>

Step4:-  create a file called medial.phtml inside the Kdecom/Lightbox/view/frontend/lightbox/media.phtml

<?php
    $mediaBlock = $this->getLayout()->createBlock('Mage_Catalog_Block_Product_View_Media');
    $_product = $mediaBlock->getProduct();
    $_helper = $this->helper('Mage_Catalog_Helper_Output');
?>
<?php if ($_product->getImage() != 'no_selection' && $_product->getImage()): ?>
<p class="product-image product-image-zoom">
    <?php
        $_img = '<a href="'.$this->helper('Mage_Catalog_Helper_Image')->init($_product, 'image').'" rel="lightbox[kdecom]"> <img  id="image" src="'.$this->helper('Mage_Catalog_Helper_Image')->init($_product, 'image').'" alt="'.$this->__($mediaBlock->getImageLabel()).'" 
            title="'.$this->__($mediaBlock->getImageLabel()).'" /></a>';
        echo $_helper->productAttribute($_product, $_img, 'image');
    ?>
</p>

<?php else: ?>
<p class="product-image">
    <?php
        $_img = '<img src="'.$mediaBlock->getBaseImageUrl($_product).'" alt="'.$this->__($mediaBlock->getImageLabel()).'" title="'.$this->__($mediaBlock->getImageLabel()).'" />';
        echo $_helper->productAttribute($_product, $_img, 'image');
    ?>
</p>
<?php endif; ?>
<?php if (count($mediaBlock->getGalleryImages()) > 0): ?>
<div class="more-views">
    <h2><?php echo $this->__('More Views') ?></h2>
    <ul>
    <?php $_size = $mediaBlock->getBaseImageIconSize()?>
    <?php foreach ($mediaBlock->getGalleryImages() as $_image): ?>
        <li>
            <a href="<?php echo $this->helper('Mage_Catalog_Helper_Image')->init($mediaBlock->getProduct(), 'image', $_image->getFile()); ?>" rel="lightbox[kdecom]"
               title="<?php echo $this->__($_image->getLabel()) ?>">
                <img src="<?php echo $this->helper('Mage_Catalog_Helper_Image')->init($mediaBlock->getProduct(), 'image', $_image->getFile())->resize($_size); ?>" 
                     width="<?php echo $_size?>" height="<?php echo $_size?>" alt="<?php echo $this->__($_image->getLabel()) ?>"/>
            </a>
        </li>
    <?php endforeach; ?>
    </ul>
</div>
<?php endif; ?>

That’s all you need to do and make sure you download the css and images for lightbox as well. Well we don’t need the jQuery included in magento2 because magento2 use jQuery instead of prototype.js.

There is one thing we have to do is just to change the lightbox css to use relative path for  the image and remove the loading and close image from lightbox.js.

If you don’t want to do that then just simply download the code and use that js and css files.
Download code is here.

The post How to create a Magento2 Lightbox Extension appeared first on Kdecom.

Magento is a one of the best available Open source with a lot of featured E commerce platform. Best thing about the magento is it is designed to to be completely extendable. Specially magento 2 is the more better and more secure version and best thing in magento2 is it use jQuery instead of prototype.

Main concept for this extension is just to understand new magento2 folder structure and this is one step to start the developing magento2 extension.

How to create a Hello world extension in Magento2

If you don’t have a Magento2 Code base please download it from here.

First of all I will show you what is the new folder structure for the magento2 extension.

So now all code goes inside one folder structure which i prefer is an good idea then the all other magento previous version.

Now we are start creating files for the magento2 Hello World Extension.

First of all we will create a config file for magento2 which goes inside the

etc/config.xml

Create a file with below content.

<?xml version="1.0"?>
<config>
    <modules>
        <Kdecom_HelloWorld>
            <version>1.0.0.0</version>
            <active>true</active>
        </Kdecom_HelloWorld>
    </modules>
    <frontend>
        <routers>
            <helloworld>
                <use>standard</use>
                <args>
                    <module>Kdecom_HelloWorld</module>
                    <frontName>hello-world</frontName>
                </args>
            </helloworld>
        </routers>
        <layout>
            <updates>
                <helloworld module="Kdecom_HelloWorld">
                    <file>layout.xml</file>
                </helloworld>
            </updates>
        </layout>
    </frontend>
</config>

First

<modules>
    <Kdecom_HelloWorld>
        <version>1.0.0.0</version>
        <active>true</active>
    </Kdecom_HelloWorld>
</modules>

This block of code is just to enable and disabled your extension and specify your extension version.

<routers>
    <helloworld> <!-- This tag not that important but it has to be unique -->
        <use>standard</use>
        <args>
            <module>Kdecom_HelloWorld</module>
            <frontName>hello-world</frontName>
        </args>
    </helloworld>

</routers>

Route Xml Tag is used in magento2 to understand which controller i should get execute.
So from above route when you execute 
http://SITENAME/index.php/hello-world that will execute our module IndexController with IndexAction.

Another Example??

http://SITENAME/index.php/hello-world/CONTROLLER/ACTION-NAME (i hope it make sense) If not then don't worry you will see  an similar example in this module.

<layout>
    <updates>
        <helloworld module="Kdecom_HelloWorld">
            <file>layout.xml</file>
        </helloworld>
    </updates>
</layout>

This will defined our layout.xml file but now path for your layout file is been changed to /view/frontend/layout.xml

but if you have it like this  <file>kdecom/layout.xml</file> then it will look for your file inside the /view/frontend/kdecom/layout.xml

Next Step

Create a layout file which goes inside the view/frontend/layout.xml

<?xml version="1.0"?>
<layout version="0.1.0">
    <hello_world_index translate="label" type="page" parent="default">
        <label>Kdecom Hello World</label>
        <reference name="content">
            <block type="Kdecom_HelloWorld_Block_Index"  name="hello_world_index" template="index.phtml"/>
        </reference>
    </hello_world_index>
    <hello_world_test translate="label" type="page" parent="default">
        <label>Kdecom Hello World New Controller Action</label>
        <reference name="content">
            <block type="Kdecom_HelloWorld_Block_Index"  name="hello_world_test" template="test.phtml"/>
        </reference>
    </hello_world_test>
</layout>

Next Step is to create a IndexController.php file which goes inside the

controllers/IndexController.php

class Kdecom_HelloWorld_IndexController extends Mage_Core_Controller_Front_Action {
    public function indexAction() {
        $this->loadLayout();
        $this->loadLayout('hello_world_index');
        $this->renderLayout();
    }
    public function testAction() {
        $this->loadLayout();
        $this->loadLayout('hello_world_test');
        $this->renderLayout();
    }

}

Next Step :- Create a index.phtml file which goes inside the

view/frontend/index.phtml

echo $this->getHelloWorld();

Next Step:- Create a Index.php file which goes inside the

class Kdecom_HelloWorld_Block_Index extends Mage_Catalog_Block_Product_Abstract {

    public function getHelloWorld() {
        return "Hello World";
    }

    public function getHelloWorldTest() {
        return "Hello World Test Action";
    }

}

Next Last Step:-

Create test.phtml file

echo $this->getHelloWorldTest();

As Soon as you finished all the above step then you should try to check if your module works fine or not.

http://YOURSITENAME/index.php/hello-world

In my case it was

Live Demo

http://www.kdecom.com/mage2/helloworld

http://www.localhost.com/mage2/index.php/hello-world/

Here is what i am seeing in my screen.

This will execute controller testAction ..

Live Demo

http://www.kdecom.com/mage2/helloworld/index/test

http://YOURSITENAME/index.php/hello-world/index/test

http://www.localhost.com/mage2/index.php/hello-world/index/test

Here is what i am seeing in my screen.

If anyone has any problem please comment below to say any words.

The post How to create a Hello world extension in Magento2 appeared first on Kdecom.

Specially this post is all about to make wordpress developer life easy and improve code base.

How to Use post_content with well formatted

If you are a developer and you are working on a plugin or custom development. So many times it happens to be a you got the post content but when you echo out that content its not formatted.

In my example i was working with event plugin and i got the post_content but when i did echo out that content there was no formatting.  Just use the filter called the_content and you will get the content with well formatted.

Here is my solution:-

$content = $post->post_content;
$content = apply_filters('the_content', $content);

echo $content;

How to limit the meta box on certain page only.

global $post;
$screens = array('post', 'page');
    foreach ($screens as $screen) {
        if($screen == "page") {
            if($post->ID == '2' || $post->ID == 7) {
            add_meta_box('rhm_service_sectionid', __('Quote Box', 'rhm_service_textdomain'), 'rhm_service_inner_custom_box', $screen);
            }
        } else {
            add_meta_box('rhm_service_sectionid', __('Quote Box', 'rhm_service_textdomain'), 'rhm_service_inner_custom_box', $screen);
        }
}

How to add Category or tags within custom post type in WordPress

add_action('init', 'custome_post_type_add_default_boxes');

function custome_post_type_add_default_boxes() {
    register_taxonomy_for_object_type('category', 'your_custom_post_type');
    register_taxonomy_for_object_type('post_tag', 'your_custom_post_type');
}

The post WordPress Plugin Tips appeared first on Kdecom.

First thing that you need to do is listen for the key event when someone click on the back button.

public boolean onKeyDown(int keyCode, KeyEvent event)  {

    if (keyCode == KeyEvent.KEYCODE_BACK && event.getRepeatCount() == 0) {

    AlertDialog.Builder alertDialog = new AlertDialog.Builder(this);
    	alertDialog .setMessage("Are you sure you want to exit?").
    	setPositiveButton("Yes",new DialogInterface.OnClickListener() {
			public void onClick(DialogInterface dialog,int id) {
				// if this button is clicked, close
				// current activity
				MainActivity.this.finish();
			}
		  }).
		  setNegativeButton("No",new DialogInterface.OnClickListener() {
			public void onClick(DialogInterface dialog,int id) {
				// if this button is clicked, just close
				// the dialog box and do nothing
				dialog.cancel();
			}
		}).show();   

    return super.onKeyDown(keyCode, event);
}

So now as soon as you add the above code it start complaining about the some of the class missing so in your import list you need to add this if you dont have:

import android.view.KeyEvent;
import android.app.AlertDialog;
import android.view.KeyEvent;
import android.content.DialogInterface;

I hope above code helps. Anyone of you have a problem contact us or leave a comment and we all try to fix it.

The post How to close app with back button in android appeared first on Kdecom.

Google Plus history api demo

As i hope people knows but google just release the new API called google history.

Wat is google history?
It is a way to post on a user google plus activity list.

http://www.kdtips.co.nz/g-plus/php/examples/userinfo/

its under working condition.

Coming soon more information…

The post Google Plus History API Demo appeared first on Kdecom.