Programming – Leogent Haromunthe

Magento 2 Coding Standard

February 10, 2019June 27, 2019 leogent Leave a comment

This entry is part 5 of 5 in the series Magento 2 Series: Understanding the Architecture

Coding standards are a result of conventions designed to produce high-quality code. Adopting certain standards yields better code quality, reduces the time taken to develop, and minimizes maintenance cost. Following coding standards requires knowing the standards in question and meticulously applying it to every aspect of the code that we write.

Magento 2 Request Flow

February 3, 2019June 15, 2019 leogent Leave a comment

This entry is part 4 of 5 in the series Magento 2 Series: Understanding the Architecture

URLs in Magento have the format of <AreaName>/<ModuleFrontName>/<ControllerName>/<ActionName>

Magento process a URL request by first stripping of the base URL. The first path segment of the remaining URL identifies request area. For example, admin for adminhtml area, and none for frontend area.

After the area name, the URI segment specifies the frontname which defined in related module. For example, in catalog/product/view, catalog is the module frontname, product is the controller folder, and view is the controller class (replacing action in Magento 1).

We use the router class to assign a URL to a corresponding controller and its action. The router’s match method finds a matching controller, which is determined by an incoming request.

Magento 2 Areas

February 2, 2019June 15, 2019 leogent Leave a comment

This entry is part 3 of 5 in the series Magento 2 Series: Understanding the Architecture

When doing development in Magento, we define which resources are visible and accessible in a given area. We use this area to control behavior that we need for specific area.

For example:

we want to add some logic using event observer, which will happened customer data is saved by customer, but not when updated from admin page. To achieve this, we will need to define the observer configuration only in frontend area, but not in adminhtml.
we want to optimize our REST queries by providing only necessary data to answer a REST query, not the entire HTML

Magento is organized into following main areas:

adminhtml : Magento Admin.
frontend : Magento Storefront.
base : use as a fallback for files absent in adminhtml and frontend areas
crontab : Cron.
webapi_rest : Web API REST
webapi_soap : Web API SOAP
graphql : Web API GraphQL

Magento 2 Application Modes

February 1, 2019June 15, 2019 leogent Leave a comment

This entry is part 2 of 5 in the series Magento 2 Series: Understanding the Architecture

There are 3 modes of Magento application, i.e. default (which is the default mode after install), developer, and production.

Here is the difference between them:

default:
- Not optimized for production
- Symlinks to static view files are published to the pub/static directory
- Errors and exceptions are not shown to the user, as they are logged to the filesystem
- This is the default mode after install, use it if you only want to view and explore Magento. You should avoid using it in development or production environment.
developer
- Symlinks to static view files are published to the pub/static directory
- provides verbose logging
- Enables automatic code compilation
- Enables enhance debugging
- Slowest performance
production
- Errors and exception are not shown to the user, as they are logged to the filesystem
- Static view files are not materialized, as they are served from the cache only
- Automatic code file compilation is disabled, as new or updated files are not written to the filesystem
- Enabling and disabling the cache types is not possible from Magento admin
- Fastest performance

Difference of using $this and $block in Magento 2 template

August 22, 2017August 24, 2018 leogent Leave a comment

One new thing I found in Magento 2 is the usage of object $block in phtml template to get the block method, instead of using $this as we did in Magento 1.

Let’s say we have this method getFoo() in our block:

public function getFoo() {
return "here is Foo";
}

then we can call the method from our template with:

echo $block->getFoo();

and surely will outpout “here is Foo“.

Now, let’s call the method using object $this:

echo $this->getFoo();

and… it turns out that its output still the same: “here is Foo“. WHY??

Cara melakukan backup database MongoDB

March 10, 2016March 10, 2016 leogent Leave a comment

Untuk melakukan backup database MongoDB, jalankan perintah berikut di shell:
mongodump

Backup database tertentu:
mongodump --db

Secara default, Hasil backup akan disimpan di folder dump, di direktori yang sedang aktif (current directory).

Apabila anda ingin menentukan lokasi penyimpanan backup, jalankan perintah berikut:
mongodump --db --out

Magento 2 Standard Fieldset Type

February 25, 2016February 25, 2016 leogent Leave a comment

protected $_standardTypes = [
        'button',
        'checkbox',
        'checkboxes',
        'column',
        'date',
        'editablemultiselect',
        'editor',
        'fieldset',
        'file',
        'gallery',
        'hidden',
        'image',
        'imagefile',
        'label',
        'link',
        'multiline',
        'multiselect',
        'note',
        'obscure',
        'password',
        'radio',
        'radios',
        'reset',
        'select',
        'submit',
        'text',
        'textarea',
        'time',
    ];

Source : https://github.com/magento/magento2/blob/2335247d4ae2dc1e0728ee73022b0a244ccd7f4c/lib/internal/Magento/Framework/Data/Form/Element/Factory.php#L26-L55

Bagaimana menggunakan tipe data varchar pada InstallSchema Magento 2?

February 21, 2016August 22, 2018 leogent Leave a comment

InstallSchema pada Magento berguna saat kita ingin membuat skema tabel baru. Dalam istilah terminologi database sering disebut dengan DDL (Data Definition Language). Dengan menggunakan installer ini kita bisa membuat table dengan contoh cara berikut:

namespace Tutorial\SimpleNews\Setup;

use Magento\Framework\Setup\InstallSchemaInterface;
use Magento\Framework\Setup\ModuleContextInterface;
use Magento\Framework\Setup\SchemaSetupInterface;
use Magento\Framework\DB\Ddl\Table;

class InstallSchema implements InstallSchemaInterface
{

public function install(SchemaSetupInterface $setup, ModuleContextInterface $context)
{
$installer = $setup;
$installer->startSetup();

// Get tutorial_simplenews table
$tableName = $installer->getTable('new_table');
// Check if the table already exists
if ($installer->getConnection()->isTableExists($tableName) != true) {
// Create tutorial_simplenews table
$table = $installer->getConnection()
->newTable($tableName)
->addColumn(
'id', Table::TYPE_INTEGER, null, [
'identity' => true,
'unsigned' => true,
'nullable' => false,
'primary' => true
], 'ID'
)
->addColumn(
'description', Table::TYPE_TEXT, null, ['nullable' => false, 'default' => ''], 'Description'
)
->setOption('type', 'InnoDB')
->setOption('charset', 'utf8');
$installer->getConnection()->createTable($table);
}
$installer->endSetup();
}

}

Menghapus Custom Attribute Magento

December 30, 2015December 30, 2015 leogent Leave a comment

Untuk menghapus custom attribute tanpa menggunakan installer atau SQL query, buat satu file, misalnya test.php dengan isi di bawah ini:

<?php
error_reporting(E_ALL | E_STRICT);

require_once './app/Mage.php';
umask(0);
Mage::app();
$setup = new Mage_Eav_Model_Entity_Setup('core_setup');
$setup->removeAttribute( 'catalog_product', 'your_custom_attribute_code' );
//ganti your_custom_attribute dengan code attribute yang diinginkan

Simpan file test.php di root folder magento. Misalkan url untuk project anda adalah http://magento_project.com, maka untuk mengeksekusi file test.php cukup jalankan http://magento_project.com/test.php, maka attribute sudah berhasil dihapus.

Mengubah awalan/prefix nomor order Magento

December 29, 2015December 29, 2015 leogent Leave a comment

Secara default, nomor order pada Magento terdiri dari 9 digit berupa angka, misalnya 145000020. Magento tidak menyediakan pilihan konfigurasi untuk menambah awalan/prefix pada nomor order, misalnya S145000020, jadi kita harus melakukannya langsung melalui query sql.

Untuk menambah prefix order pada semua store, jalankan query berikut:

UPDATE eav_entity_store
INNER JOIN eav_entity_type ON eav_entity_type. entity_type_id = eav_entity_store.entity_type_id
SET eav_entity_store.increment_prefix='S'
WHERE eav_entity_type .entity_type_code= 'order';

Jika anda ingin menambah prefix order hanya pada toko tertentu, jalankan query berikut:

UPDATE eav_entity_store
INNER JOIN eav_entity_type ON eav_entity_type.entity_type_id = eav_entity_store.entity_type_id
SET eav_entity_store.increment_prefix= 'S'
WHERE eav_entity_type.entity_type_code='order' AND eav_entity_store.store_id = 'kodetoko';

ganti ‘kodetoko’ dengan kode store Magento anda.

Jika anda ingin membuang kembali prefix, jalankan query berikut:

UPDATE eav_entity_store
INNER JOIN eav_entity_type ON eav_entity_type. entity_type_id = eav_entity_store.entity_type_id
SET eav_entity_store .increment_prefix= NULL
WHERE eav_entity_type .entity_type_code= 'order';