Best Practices for caching

• Enable Full Page Cache (FPC): Adobe Commerce comes with a built-in Full Page Cache that can dramatically speed up the loading time of pages. Enabling FPC can be done by going to System > Cache Management > Full Page Cache and selecting “Enable” from the drop-down menu. Once enabled, FPC will store the HTML of each page, reducing the amount of processing required to generate each page.
• Use Varnish Cache: Varnish Cache is a powerful caching solution that can be used in conjunction with Adobe Commerce’s built-in FPC. Varnish Cache sits between the web server and the client and caches the content of each request, serving cached content to subsequent requests. To enable Varnish Cache, you need to configure it in your web server and configure Adobe Commerce to use it as a caching proxy.
• Use Redis Cache: Redis is an in-memory key-value store that can be used as a cache backend for Adobe Commerce. By default, Adobe Commerce uses file-based caching, which can be slow and inefficient. Redis can be faster and more efficient because it stores data in memory instead of on disk. To use Redis Cache in Adobe Commerce, you need to install and configure the Redis extension, and then configure Adobe Commerce to use Redis as a cache backend.
• Use Content Delivery Networks (CDN): A CDN is a network of servers that cache static content, such as images, CSS, and JavaScript files, and serves them from the server closest to the user. This can dramatically improve the loading time of static content and reduce the load on your server. Adobe Commerce has built-in support for CDN integration, which can be configured under System > Configuration > Web > CDN.
• Monitor Cache Performance: It’s important to regularly monitor the performance of your caching solutions to ensure they are working effectively. You can use tools like New Relic or Blackfire to monitor the performance of your website and identify any caching-related issues.

Types Cache:

• Configuration Cache: Stores configuration settings for the website, including the website’s system configuration and database configuration.
• Layout Cache: Stores the layout of pages and blocks on the website, including the position of blocks, their content, and other layout settings.
• Block Cache: Stores the HTML output of blocks on the website, reducing the amount of processing required to generate each page.
• Collections Data Cache: Stores data related to collections, such as product or category data, to speed up database queries.
• Reflection Cache: Stores metadata about classes and interfaces, reducing the amount of time required to load and process classes.
• Page Cache: Stores the entire HTML output of a page, including dynamic content, to reduce the amount of processing required to generate each page.
• EAV Cache: Stores data related to entities, attributes, and values, speeding up database queries.
• Translations Cache: Stores translations for the website, reducing the amount of processing required to generate translated content.
• Integration Configuration Cache: Stores configuration settings for integrations, including third-party integrations and APIs.
• Web API Cache: Stores data related to the Magento Web API, reducing the amount of processing required to generate API responses.

Create a custom cache list in Magento

• Create a new file named cache.xml in the directory app/code/<Vendor>/<Module>/etc/.
• In the cache.xml file, define the custom cache type by adding the following code:

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Cache/etc/cache.xsd">
   <type name="custom_cache_type" translate="label description" instance="<Vendor>\<Module>\Cache\Type\CustomCacheType">
       <label>Custom Cache Type</label>
       <description>Custom Cache Type Description</description>
   </type>
</config>

In this code, replace <Vendor> with the name of your module vendor, and <Module> with the name of your module. Also, replace CustomCacheType with the name of your custom cache type.

• Create a new file named CustomCacheType.php in the directory app/code///Cache/Type/.
• In the CustomCacheType.php file, define the custom cache type class by adding the following code:

<?php
namespace <Vendor>\<Module>\Cache\Type;
class CustomCacheType extends \Magento\Framework\Cache\Frontend\Decorator\TagScope
{
   const TYPE_IDENTIFIER = 'custom_cache_type';
   const CACHE_TAG = 'CUSTOM_CACHE_TYPE';
   public function __construct(\Magento\Framework\App\Cache\Type\FrontendPool $cacheFrontendPool)
   {
       parent::__construct($cacheFrontendPool->get(self::TYPE_IDENTIFIER), self::CACHE_TAG);
   }
}

In this code, replace <Vendor> with the name of your module vendor, and <Module> with the name of your module. Also, replace CustomCacheType with the name of your custom cache type.

• Clear the cache by running the following command in the Magento 2 root directory:

php bin/magento cache:clean

• Verify that your custom cache type is listed in the cache list by going to System > Cache Management in the Magento 2 admin panel.

Once your custom cache type is added, you can use it to cache custom data or functionality in your module.

By effectively using cache in Adobe Commerce, you can significantly improve the performance of your website and provide a better user experience for your customers.

Also read the what is partial caching in Mageto 2

The post How to effectively use cache in Adobe Commerce(Magento) first appeared on Tag Vibe.

Magento 2 Access Control List Rules
The Magento 2 Admin ACL resources are visible under the Magento 2 admin System > Permissions > User Roles area. When we click on the Add New Role button or access a role.  In Magento 2, we can apply the ACL rule in the menu or form, but this article will help you apply the ACL rule on specific filed in the form.

Step: 1

Create a UI component file vendor\module-name\Ui\Component\Form\Field\DisableField

<?php


namespace vendor\module-name\Ui\Component\Form\Field;

use Magento\Framework\View\Element\UiComponent\ContextInterface;
use Magento\Framework\View\Element\UiComponentFactory;
use Magento\Framework\View\Element\UiComponentInterface;
use Magento\Framework\AuthorizationInterface;
use Magento\Ui\Component\Form\Field as FormField;

/**
 * Class DisableField
 *
 * @package I95DevConnect\CloudCustomizations\Ui\Component\Form\Field
 * @author Rajat Kar
 */
class DisableField extends FormField
{
    /**
     * @var AuthorizationInterface
     */
    private $authorization;

    /**
     * Constructor
     *
     * @param ContextInterface $context
     * @param UiComponentFactory $uiComponentFactory
     * @param AuthorizationInterface $authorization
     * @param UiComponentInterface[] $components
     * @param array $data
     */
    public function __construct(
        ContextInterface       $context,
        UiComponentFactory     $uiComponentFactory,
        AuthorizationInterface $authorization,
        array                  $components = [],
        array                  $data = []
    )
    {
        $this->authorization = $authorization;
        parent::__construct($context, $uiComponentFactory, $components, $data);
    }


    /**
     * Prepare component configuration
     *
     * @return void
     * @throws \Magento\Framework\Exception\LocalizedException
     */
    public function prepare()
    {
        parent::prepare();


        $isAllowed = $this->authorization->isAllowed(‘Vendor_ModuleName:: editable_fields’);
        if (!$isAllowed) {
            $currentConfig = $this->getData(‘config’);
            $currentConfig[‘disabled’] = true;
            $this->setData(‘config’, $currentConfig);
        }
    }
}

Step: 2

Create etc/acl.xml

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../../../lib/internal/Magento/Framework/Acl/etc/acl.xsd">
    <acl>
        <resources>
            <resource id="Magento_Backend::admin">
                <resource id="Magento_Customer::customer">
                    <resource id="Magento_Customer::manage">
                        <resource id="Vendor_ModuleName:: editable_fields" title="allow edit some field" translate="title" sortOrder="110" />
                    </resource>
                </resource>
            </resource>
        </resources>
    </acl>
</config>

Step: 3

view/adminhtml/ui_component/customer_form.xml

<form xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Ui:etc/ui_configuration.xsd">
    <fieldset name="customer">
        <field name="customer_field_name" formElement="input" class="Vendor\ModuleName\Ui\Component\Form\Field\DisableField">
            <argument name="data" xsi:type="array">
                <item name="config" xsi:type="array">
                    <item name="source" xsi:type="string">customer</item>
                    <item name="sortOrder" xsi:type="number">100</item>
                    <item name="visible" xsi:type="boolean">true</item>
                </item>
            </argument>
        </field>
    </fieldset>
</form>

Hope this article help you. Thank you

The post Magento2: Apply ACL to custom field first appeared on Tag Vibe.

If else conditions in KO template

<!-- ko if: myData -->
..if statement goes here
<!-- /ko -->
<!-- ko if: !(myData) -->
..else statement goes here
<!-- /ko -->

If else conditions in KO template with && operator

<!-- ko if: X && Y -->
//your code
<!-- /ko -->

<!-- ko if: X && !Y -->
//your code
<!-- /ko -->

<!-- ko if: !X && !Y -->
 //your code
 <!-- /ko -->

The post How to set ‘if’, ‘else’, ‘and’ conditions in knockout js Magento 2? first appeared on Tag Vibe.

Follow the below steps to achieve this:

Add the below code into your existing menu.xml

File path: app\code\Vendor\Extension\etc\adminhtml\menu.xml

<?xml version="1.0"?>

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Backend:etc/menu.xsd">
    <menu>
        <add id="Vendor_Extension::extensionmenu" title=" Extension Menu" module="Vendor_Extension" sortOrder="10" resource="Vendor_Extension::mainmenu" dependsOnConfig="section/group/field"/>
    </menu>
</config>

let us know via the comment box if you need any help on this, we will be happy to solve it! Do share the article with your friends and stay updated with us.

The post Hide Admin Menu Based on System Config in Magento 2 first appeared on Tag Vibe.

bin/magento module:disable Vendor_Module

But in the above method below problem will be arise:

• Module will be disable but files are still there.
• If you run integration tests or static tests, it will run with including the disabled modules.
  So, we need a method to remove the module in a right way with the help of composer

Remove module with composer

As the core modules are loaded via composer as dependencies, we cannot simply remove them from the composer.json. we can remove those via replace capability.

composer file looks like below with replace key

“require”: {
[…]
},
“replace”: {
     “magento/module-marketplace”: “*”
},
“config”: {
[…]

Example to remove core modules like dotmailer, vertex, yotpo  below

“replace”:{
      “dotmailer/dotmailer-magento2-extension”: “*”,
      “dotmailer/dotmailer-magento2-extension-package”: “*”,
      “dotmailer/dotmailer-magento2-extension-enterprise”: “*”,
      “dotmailer/dotmailer-magento2-extension-chat”: “*”,
      “vertex/module-tax”: “*”,
      “vertex/sdk”: “*”,
      “vertex/module-address-validation”:”*”,
      “yotpo/magento2-module-yotpo-reviews” : “*”
},

Then, run the “composer update” command to remove the core modules which is mentioned inside replace section.

The post How to remove unused core modules from Magento 2? first appeared on Tag Vibe.

The list of most important  CLI commands for Magento 2 for developer .

Setup Upgrade Using Command Line

php bin/magento setup:upgrade or php bin/magento s:up

If you don’t want to remove pub/static files while installing/updating database then use following command.

php bin/magento setup:upgrade --keep-generated

Cache Clean Using Command Line

php bin/magento cache:clean  or php bin/magento c:c

Cache Flush Using Command Line

php bin/magento cache:flush or php bin/magento c:f

View cache status Using Command Line

php bin/magento cache:status or php bin/magento c:s

Enable Cache Using Command Line

php bin/magento cache:enable [cache_type]

Disable Cache Using Command Line

php bin/magento cache:disable [cache_type]

Static Content Deploy Using Command Line (Use -f for force deploy on 2.2.x or later)

php bin/magento setup:static-content:deploy -f or php bin/magento s:s:d -f

Static Content Deploy For Particular Language Using Command Line

php bin/magento setup:static-content:deploy en_US

Static Content Deploy For Magento Backend Theme Using Command Line (Working on 2.1.1 or later)

php bin/magento setup:static-content:deploy --theme="Magento/backend"

Static Content Deploy For Specific Themes Using Command Line (Working on 2.1.1 or later)

php bin/magento setup:static-content:deploy --theme Magento/luma --theme Magento/second_theme

Exclude Themes on Static Content Deploy and does not minify HTML files Using Command Line (Working on 2.1.1 or later)

php bin/magento setup:static-content:deploy en_US --exclude-theme Magento/luma --no-html-minify

Reindexing Using Command Line

php bin/magento indexer:reindex

View the list of indexers Using Command Line

php bin/magento indexer:info

View indexer status Using Command Line

php bin/magento indexer:status

Show the mode of all indexers Using Command Line

php bin/magento indexer:show-mode

See all modules Status Using Command Line

php bin/magento module:status

Enable module Using Command Line

php bin/magento module:enable Namespace_Module

Disable module Using Command Line

php bin/magento module:disable Namespace_Module

Uninstall Module Using Command Line

php bin/magento module:uninstall Namespace_Module

Check Current Mode Using Command Line

php bin/magento deploy:mode:show

Change To Developer Mode Using Command Line

php bin/magento deploy:mode:set developer

Change To Production Mode Using Command Line

php bin/magento deploy:mode:set production

Run the single-tenant Compiler Using Command Line

php bin/magento setup:di:compile or php bin/magento s:d:c

Unlock Admin User Using Command Line

php bin/magento admin:user:unlock adminusername

Enable Maintenance Mode Using Command Line

php bin/magento maintenance:enable

To enable maintenance mode for all clients except 127.0.0.1 and 127.0.0.2:

php bin/magento maintenance:enable --ip=191.0.0.1 --ip=191.0.0.2

To clear the list of IPs.

php bin/magento maintenance:enable --ip=none

Disable Maintenance Mode Using Command Line

php bin/magento maintenance:disable

Check Maintenance Mode Status Using Command Line

php bin/magento maintenance:status

Allow IP on Maintenance Mode Using Command Line

php bin/magento maintenance:allow-ips --ip=191.0.0.1 --ip=191.0.0.2

Set Magento crontab Using Command Line

php bin/magento cron:install --force

Use –force to rewrite an existing Magento crontab.
To view the crontab, enter the following command as the Magento file system owner.

crontab -l

Remove Magento crontab Using Command Line

php bin/magento cron:remove

The post Magento 2 Useful Commands List for Developer first appeared on Tag Vibe.

Debug the Knockout JS issue

• At first we need to get a Knockout instance from the browser console.
  • var ko = require('knockout');
• Now we have Knockout instance in the ko variable. We can use it to get a context of any DOM element.

var context = ko.contextFor($0);

• where $0 is a special variable in browser console. It contains a link to a DOM element that is last inspected.

// Admin > Products > Catalog > Add Product
// Inspect "Product Name"
var fieldName = ko.contextFor($0).$data;

console.log(fieldName.name); // product_form.product_form.product-details.container_name.name

OR

You can install this https://chrome.google.com/webstore/detail/knockoutjs-context-debugg/oddcpmchholgcjgjdnfjmildmlielhof?hl=en knockout debugger and debug.

Hope this article helped you in some way. Please leave us your comment and let us know what do you think? Thanks.

The post How to debug Magento 2 issues? first appeared on Tag Vibe.

As a Magento developer we are facing lot of issue which is common while developing and customizing a module. Today we are going to discuss about How to fix the “Area code not set” issue. This error occurs mainly from four reason CRON, CLI , Setup Scripts and use of session in wrong area and it will pop up when you are either compiling or running setup upgrade command. In both of the cases, it tries to create an object using the constructor of your classes but couldn’t find the area code and it fails to load.

WHAT IS AREA CODE IN MAGENTO 2?

Magento uses area codes to define the entry point to application to load given a specific request context. There are seven distinct ‘areas’ of the system, each with their own area code:

1. global
2. doc
3. crontab
4. frontend
5. adminhtml
6. webapi_rest
7. webapi_soap

When setting the session for customer or Order we should define the area.

It’s Fixed related to this :

1. Magento 2.2 area code not set: area code must be set before starting a session.
2. upgrading data.. area code not set: area code must be set before starting a session.
3. Magento 2 setup upgrade import failed: area code is not set
4. import failed: area code not set: area code must be set before starting a session.
5. Magento 2 area code admin does not exist
6. processing configurations data from configuration file… import failed: area code is not set
7. import failed: area code is not set magento2
8. area code “” does not exist Magento 2

For Example:

We are creating a plugin or overriding a method of core class in custom class and we have injected Magento core session manager and customer session in custom class constructor.

For overriding the existing core class method we are using preference in di.xml and keep in global onside our custom module. when we run complile and upgrade we will get “AREA CODE NOT SET” issue.

Solution:

To resolve this issue we should keep the di.xml in frontend area as we are using customer session in our class. Likewise if you are using Magento Backend session in your custom class you should keep the di.xml in adminhtml area.

Hope this article helped you in some way. Please leave us your comment and let us know what do you think? Thanks.

The post How to fix the “AREA CODE NOT SET” issue? first appeared on Tag Vibe.

For an easy way to change the password for bulk of customer in Magento 2, you can import customer CSV file data of existing customer email id and password field. You can give your password which you want to change and password_hash should be blank.

Please refer the below sceenshots:

The post How to change customer password quickly in Magento 2 first appeared on Tag Vibe.