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

An Easy Way To Configure Index Management In Magento 2 Admin Panel

Whenever one or more items change, Magento reindexes automatically. Any action such as price changes, creating catalog or shopping cart price rules, adding new categories, and so on can activate reindexing. Magento accumulates data into special tables using indexers to optimize performance. The indexed tables must be updated or reindexed when the data changed. Your store remains accessible during the reindexing background processes.

Reindexing data boost speed of processing, and reduces the waiting time of the customer. For example, if you edit the price of a product from 4$ to 3$, Magento reindexes the data to display the price change in the store. Without indexing, Magento has to calculate the price of every product on the fly, taking into account shopping cart price rules, bundle pricing, discounts, tier pricing, and so on. Customers have to wait longer to see the product.

system-index-management-actions

  • Index Management has a slightly different presentation for flat product catalogs.
  • To avoid problems when multiple Admin users update objects that trigger automatic reindexing, we recommend that you set all indexers to run on schedule as cron jobs. Otherwise, every time an object is saved, any objects with interdependencies might cause a deadlock. Symptoms of a deadlock include high CPU usage and MySQL errors. As a best practice, we recommend that you use scheduled indexing.

Follow these steps to change the index mode:

On the admin sidebar click System > Under Tools, click Index Management

Tick the checkbox to select indexer as you want, set action to Update on Save or Update by Schedule and click Submit to apply.

Above is a tutorial on how to configure index management in Magento 2 admin panel. We hope that you can optimize the loading progress of your website after reading this guideline. See you in the next article.