Category: Store

A Complete List Of Developer Tools In Magento 2 Admin Panel

During front-end development, developers can use the Advanced Developer tools to decide the compilation mode, create a whitelist of IP addresses, display template path hints, and make spot changes to text in the interface of the storefront and Admin.

There are 7 tools in this section

Provides access to the Client and IPN logs, if enabled in the Developer Options section of the Amazon Pay configuration. The following Amazon Logs are available in the System menu of the Magento Admin:

Client

Logs all API calls and responses.

INP

Logs all Instant Payment Notifications that are sent by Amazon.

Follow these steps to display the Amazon Logs:

1. On the Admin sidebar, click System.
2. Under Amazon Logs, select Client or IPN

The Frontend Development Workflow type determines if Less compilation takes place on the client- or server side during development. Less is an extension of CSS that has additional features and conventions, and that produces streamlined code. Client-side Less compilation is recommended for theme development. A server-side compilation is the default mode. The development workflow options are not available for stores in production mode.

For technical information, see Client-side LESS compilation vs. server-side in the developer documentation.

The Frontend Development Workflow configuration is available in Developer Mode only.

Front-end Development Workflow
Front-end Development Workflow

1. On the Admin sidebar, tap Stores. Then under Settings, choose Configuration.
2. In the panel on the left under Advanced, choose Developer.
3. Expand the Front-end Development Workflow section.
4. Set Workflow Type to one of the following:

Client-side less compilation

Compilation takes place in the browser using the native less.js library.

Server-side less compilation

Compilation takes place on the server using the Less PHP library. This is the default mode for production.

5. Click Save Config.

How To Configure Cron In Magento 2 Admin Panel

  • Email
  • Catalog Price Rules
  • Newsletters
  • XML Sitemap Generation
  • Currency Rate Updates

Besides, you can configure these things to run according to a cron schedule:

  • Order System Grid Updates and Reindexing
  • Pending Payment Lifetime

Remember that the base URLs for the store are set correctly, so the URLs that are generated during cron operations are correct. For further information, please read: Set up cron jobs.

Follow these steps to configure cron:

1. On the Admin sidebar, click Stores. Under Settings, click Configuration.
2. On the left of the panel under Advanced, click System.
3. Open the Cron tab.

Cron (Scheduled Tasks)

4. After that, edit settings for the Index and Default groups

  • Generate Schedules Every
  • Schedule Ahead for
  • Missed if not Run Within
  • History Cleanup Every
  • Success History Lifetime
  • Failure History Lifetime
  • Use Separate Process
Schedule Ahead for
Schedule Ahead for
  • Missed if not Run Within
  • History Cleanup Every
  • Success History Lifetime
  • Failure History Lifetime
  • Use Separate Process
Cron Configuration for Group: Index
Cron Configuration for Group: Index
Click Save after config.
Above is a tutorial on How To Configure Cron In Magento 2 Admin Panel. We hope that after reading this article, you can completely control and configure the cron. Please like and share if you think this article is beneficial. On the next article, we will describe some developer tools in Magento 2 default installation. Keep tracking Magestandard by subscribing button to read the new Magento 2 tutorial and guideline articles. See you in the next blog post

A Few Steps To Create A Backup In Magento 2 Admin Panel

In the previous Magento 2 article, we described a manual of index triggers event in Magento 2. In this article, we will describe how to create a back up in Magento 2 admin panel

Magento Open Source allows store administrators to back up different parts of the installation, for example, the file system, database, and media files, and to recover automatically. A record for each backup displays in the table grid of the Backups page. Deleting a record from the list removes the archived file as well. Database backup files are compressed using the .GZ format. and the .TGZ format is used for the system backups and database and media backups. As a best practice, you should restrict access to backup tools, and back up before installing extensions and updates.

 

Restrict access to backup tools. You can restrict access to the Backups and Rollback management tool by configuring user permissions for backup and rollback resources. To limit access, unselect the corresponding checkbox. If you need to grant access to recover resources, you must allow access to backup resources.

Back up before installing extensions and updates. Before you install an extension or update, always perform a backup. You can use the backup option in the Component Manager that you can use before upgrading to a new release or installing an extension.
Backups in magento 2
Backups

Follow these steps to create a backup:

1. On the Admin sidebar, click System. Under Tools, click Backups.
2. Select the backup type you want to create by clicking the button on the right:

System Backup

Creates a complete backup of the database and the file system. During the process, you can include the media folder in the backup.

Database and Media Backup

Creates a backup of the database and the media folder.

Database Backup

Creates a backup of the database.

3. To change to the maintenance mode during the backup, select the checkbox. After that, maintenance mode is turned off automatically.
4. For a system backup, mark the Include Media folder to System Backup checkbox if you want to include the media folder. Confirm the action.

To schedule backups

1. On the Admin sidebar, tap Stores. Then under Settings, click Configuration.
2. On the left of the panel under Advanced, click System.
3. Open the Scheduled Backup Settings tab, and do the following:
4. When complete, tap Save Config.

A Manual Of Index Trigger Events In Magento 2 Admin Panel

Reindexing Triggers

INDEX TYPE REINDEXING EVENT
Product Prices Add the customer group

Change configuration settings
Flat catalog product data Add the store

Add the store group

Add, edit, or remove attribute (for searching and filtering)
Flat catalog category data Add the store

Add the store group

Add, edit, or remove attribute (for searching and filtering)
Catalog category/product index Add, edit, or remove products (single, mass, and import)

Change product-to-category relations

Add, edit, or remove categories

Add or remove stores

remove store groups

remove websites
Catalog search index Add, edit, or remove products (single, mass, and import)

Add or remove stores

remove store groups

remove sites
Stock status index Change inventory configuration settings.
Category permissions index Add the store, add the store group, add or remove or update attribute (for searching and filtering)

Index Actions and Controls

Index Actions

ACTION RESULT TO CONTROL
Creating a new store, a new customer group, or any action listed in “Actions that Cause a Full Reindex.” Full reindex Your Magento cron job determine to perform full reindexing on the schedule.
Mass loading of items in these ways:

  • Magento import/export
  • Direct SQL query
  • Any other method that directly adds, changes, or removes data.
 Partial reindex (only changed items are reindexed) Determined at the frequency by your Magento cron job.
Changing scope (for example, from global to website) Partial reindex (only changed items are reindexed) At the frequency determined by your Magento cron job.

Events that Trigger Full Reindexing

Full Reindex Triggers

INDEXER EVENT
Catalog Category Flat Indexer Create a new web store

Create a new web store view

Create, or remove an attribute that is any of the following:

  • Searchable or visible in advanced search
  • Filterable
  • Filterable in search
  • Used for sorting

Change an existing attribute to be any of the preceding.

Enable flat category storefront options
Catalog Product Flat Indexer Create a new web store

Create a new web store view

Create, or remove an attribute that is any of the following:

  • Display in advanced search
  • Filterable in search
  • Filterable
  • Used for sorting

Change an existing attribute to be any of the preceding.

Enable flat category storefront options
Stock status indexer When the following Catalog Inventory options change in the system configuration:

Stock Options Display Out of Stock Products
Product Stock Options Manage Stock
Price Indexer Adding a new customer group.

When the following Catalog Inventory options change in the system configuration:

Stock Options Display Out of Stock Products
Product Stock Options Manage Stock
Price Catalog Price Scope
Category or Product Indexer Create or remove a store view

remove a store

remove a website

A Simple Way To Configure The Full-Page Cache In Magento 2 Admin Panel

To display category, product, and CMS pages quickly, Magento Open Source uses full-page caching on the server. Full-page caching enhance response time and reduces the load on the server, Magento Open Source uses full-page caching on the server. Without caching, each page might need to run blocks of code and retrieve information from the database. However, with full-page caching enabled, a fully-generated page can be read directly from the cache.

We recommend using Varnish only in a production environment.

The system can use the cached content to process the requests from similar types of visits. Pages shown to a casual visitor might differ from those shown to a customer. For the purposes of caching, there are 3 types of visit:

Non-sessioned: During a non-sessioned visit, a customer views pages but does not interact with the store. The system caches the content of each page viewed and serves them to other non-sessioned customers.

Sessioned: During a sessioned visit, customers who interact with the store through activities such as comparing products or adding products to the shopping cart, are assigned a session ID. Cached pages that are generated during the session are used only by that customer during the session.

Customer: Customer sessions are created for those who have registered for an account while logged in to their accounts. During the session, special offers, promotions, and prices that are based on the customer group to which they are assigned can be present to them.

For technical information, see Configure and Use Varnish and Use Redis for the Magento page and default cache in the developer documentation.

To configure the full-page cache, you can follow these steps:

  1. On the Admin sidebar, click Stores. Under Settings, click Configuration.
  2. On the left of the panel under Advanced, select System.
  3. Open the Full Page Cache tabconfig-advanced-system-full-page-cache
  4. Set Caching Application to one of these options:Built-in ApplicationVarnish Caching
  5. Enter the TTL for public content (the default value is 86400) to set the time-out for the page cache
  6. If using Varnish, complete the Varnish Configuration section as follows
    • In the Access list field, enter the IP addresses that can purge the Varnish configuration to generate a config file. Separate multiple entries with a comma. The default value is “localhost.”
    • In the Backend host field, enter the IP address of the backend host that generates config files. The default value is “localhost.”
    • In the Backend port field, identify the backend port that is used to generate config files. The default value is: “8080.”
    • Click the button for the version of Varnish that you use to export the configuration as a varnish.vcl file, Export VCL for Varnish 3

    Export VCL for Varnish 4

    config-advanced-system-full-page-cache-varnish

  7.  Click Save Config