Monthly Archives: October 2020

Creating Magento 2 user roles is the security action you should take before creating admin users in your store. They help you define the level of permissions some users are granted with. This restricts their access to certain admin sections to ensure a secure admin panel environment.

Create Magento 2 User Roles

1. Navigate to Admin Panel >  System> >  Permissions >  User Roles and hit the Add New Role button to add a new user role in Magento.

2. Fill in the User Role Information.

• Set the Role Name.
• Specify Your Password (user you are currently logged in under).

3. Move to the Role Resources tab and choose the Resources admin a user will have access to.

• Choose All in Resource Access if you want a user to have access to all pages and capabilities of the admin panel.
• Choose Custom in Resource Access to select interfaces to which you want to give a user access to.

Press the Save Role button once you finish.

Track Admin User's Activity

Once you create a user role in Magento,

As you may know Magento 2 Login as Customer extension by Magefan was integrated into the Magento 2.4.0 core, and we transferred the copyright for "Login as Customer" extension to Adobe. More about it you can read in the article about Login as Customer & Magento Integration.

So if you use Magento 2.4.x or greater you have 2 options:

1. Remove Magefan Login as Customer extension and use core Magento Login As Customer

2. Disable core Login As Customer and continue using original Magefan Login as Customer.

To disable core modules you can run these commands:

bin/magento module:disable Magento_LoginAsCustomer
bin/magento module:disable Magento_LoginAsCustomerAdminUi
bin/magento module:disable Magento_LoginAsCustomerApi
bin/magento module:disable Magento_LoginAsCustomerAssistance
bin/magento module:disable Magento_LoginAsCustomerFrontendUi
bin/magento module:disable Magento_LoginAsCustomerLog
bin/magento module:disable Magento_LoginAsCustomerPageCache
bin/magento module:disable

This year Magefan is proud to be among the Silver Sponsors of an online MageCONF that will take place on October 24, 2020.

Mageconf 2020 is a must-attend online conference that allows you to dive into the world of unique shared experience presented by Magento expert agencies, service providers and developers, learn about the latest eCommerce trends and innovations.

Register now for free. Don’t miss it!

If you use Magento 2 WebP Images Extension and the CLI conversion by the bin/magento magefan:webp:convert command is run very long, the issue may be in cwebp library on your server. WebP extension works in a way to check if the proper software is installed on the server first and then use its own binary files if there is no software installed. So if you already have the cwebp lib on the server, then the extension will use it.

Cwebp on the server can be outdated, please try to update or reinstall the cwebp.

If for some reason you are not able to update it, try to modify the following file:

/lib/internal/Magefan/Lib/WebPConvert/Convert/Converters/Cwebp.php

or

vendor/rosell-dk/webp-convert/src/Convert/Converters/Cwebp.php

Find method discoverCwebpBinaries and comment the lines like on a screenshot:

The result will look like this:

If this does not help, please contact us.

As you create your eCommerce store, there are multiple stages you go through: starting with development and gradually moving to live. Each stage has corresponding tasks to keep your website running.

Magento 2 handles this through the mode functionality. There are three Magento modes: default, development, and production. Each facilitates different store operations.

However, to use Magento 2 deploy modes effectively, you need to know what each is useful for. This is exactly what you will find out today: what Magento modes are, how they differ and how to switch between them. 

What Are Magento 2 Deploy Modes?

Magento 2 deploy modes are modes that create specific operation conditions suitable for different store operation tasks. As we've mentioned, there are 3 core Magento deploy modes that make your experience better. Let's have a closer look at each of them.

1. Default mode

After installation, Magento 2 is in a default mode making it possible to use the platform without applying

Since Magento is a complex platform, it might be hard to cover all the sections on your own. You need to create other Magento admin users who will manage products, monitor orders and create email templates, etc.

However, you must grant each user access only to certain areas of your store to ensure high admin panel security.

So today you'll learn how to create admin users in Magento and monitor their actions in the admin panel.

Magento 2: Create Admin User in the Admin

1. Go to Admin Panel > System > Permissions > All Users and press the Add New User button.

3. Fill out the new user Account Information:

• Set the User Name that will be used during login, and specify the First and Last Names.
• Enter the user's Email.
• Create a Password, and confirm it in the Password Confirmation field.
• Choose the language of the admin panel interface for the user in the Interface Locale.

In case you use one of the Amasty extensions, e.g. Amasty Layered navigation, you may face the issue of the broken blog featured images after the upload.

We have found the issue in Amasty_Shopby extensions, that breaks some other extensions using image upload functionality, including our Magento 2 Blog Extension.

Amasty_Shopby in this file:

app/code/Amasty/Shopby/etc/adminhtml/di.xml

adds the plugin to Magento\Catalog\Model\ImageUploader model.

Judging from the code in the following file:

app/code/Amasty/Shopby/Plugin/Catalog/Model/ImageUploaderPlugin.php

it looks like some fix Amasty added for Magento 2.3.4. and the issue lies in the plugin beforeMoveFileFromTmp.

The original Magento MoveFileFromTmp declaration looks like this:

public function moveFileFromTmp($imageName, $returnRelativePath = false)

and Amasty's plugin missing the second parameter $returnRelativePath:

public function beforeMoveFileFromTmp(\Magento\Catalog\Model\ImageUploader $subject, $path)

So, basically, Amasty's