Monthly Archives: June 2022
Hello Magento fans,
This June we've got plenty of news and updates for you since we've released 2 new extensions and added plenty of new features and fixed to about 12 of them.
So, let's dive in. You have a lot to discover.
New Magento 2 Order Edit Extension!
Order management is one of the most essential processes in your Magento 2 store. It directly influences customers' experience and their desire to return and purchase from you repeatedly.
Sometimes customers want to change the shipping address or remove some products they added to the order accidentally. Here's when Edit Order Extension takes the stage to help you process customers' requests faster and keep the order data organized.
You can edit all of the order details: status, number, website, customer, shipping&biling addresses, payment methods, and ordered items.
The module tracks all of the changes and offers a Quick Order Edit feature, so you can conveniently edit orders without canceling them.
Generating new content for your blog constantly allows you to keep visitors engaged and rank for more keywords in search. It is a vital strategy if you want to drive more people to your store and increase revenue correspondingly.
However, sometimes you just don't have enough time to create and post all of the content. To keep up with the schedule you have to log in to your admin panel and enable the blog posts you want to publish.
Today we'll fix that.
If you've created and edited some of the posts beforehand, you can schedule the publication, and our Magento 2 Blog will publish them automatically.
To schedule blog posts in Magento:
1. Navigate to Content > Blog > Posts and go to the blog post you'd like to schedule.
2. Scroll down to the Display Setting, find the Publish Date, and set the future date when you need a blog post to go live.
Note: if you need to disable the blog post after some time you can use the End Date. Our extension will not only disable the blog post at a set
If you decided to remove Magento 2 Edit Order Extension, please follow the steps below. You can contact our team for a free consultation in case you have any issues with Magefan's extension.
Remove Extension Files
Removing files instruction depends on the way the Edit Order extension has been installed in.
1. If you can find the extension files in the folder
app/code/Magefan/OrderEdit
then remove this folder.
2. If the extension was installed via the composer and its files located in the folder
vendor/magefan/module-order-edit
then run composer CLI command to remove it
composer remove magefan/module-order-edit
Once extension files have been removed, run these Magento CLI commands:
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
Note: if you don't want your website to be down during deployment, try these zero downtime deployment commands for Magento 2.
Remove Extension Data (optional)
Attention! This will clean all Edit Order
If you need to update Magento 2 Edit Order Extension by Magefan, please follow the steps below.
Note: the updating instructions depend on the method the Edit Order extension was installed with.
Update using composer
If the Edit Order module was installed via the composer (check if vendor/magefan/module-order-edit
folder exists), then you need to run these simple CLI commands in Magento 2 directory:
composer remove magefan/module-order-edit
composer require magefan/module-order-edit
^x.x.x
# replace x.x.x with the version you want to use
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
Note: if you don't want your website to be down during deployment, try these zero downtime deployment commands for Magento 2.
Update using archive and FTP
If the Edit Order module was installed via FTP (check if app/code/Magefan/OrderEdit
folder exists), then follow these commands:
1. Download the latest version of the Edit Order extension
You can install Magento 2 Edit Order Extension by Magefan, using composer or archive installation methods.
Do you want us to install and configure the Order Edit extension for you? Let our technical engineers do it – check out our installation service.
Installation via composer (recommended)
Please navigate to your Magefan Account > My Downloads > Install via Composer to get the composer installation instructions.
If you decided to remove Magento 2 POS System, please follow the steps below. You can contact our team for a free consultation in case you have any issues with Magefan's extension.
Remove Extension Files
1. If you can find the extension files in the folder
app/code/Magefan/Pos
app/code/Magefan/PosApi
app/code/Magefan/PosCashPayment
app/code/Magefan/PosGraphQl
app/code/Magefan/PosShippingCarrier
app/code/Magefan/PosStaffSession
app/code/Magefan/PosStaffSessionGraphQl
app/code/Magefan/PosTerminal
app/code/Magefan/PosTerminalGraphQl
app/code/Magefan/StoreLocator
app/code/Magefan/StoreLocatorGraphQl
app/code/Magefan/StoreLocatorUser
app/code/Magefan/StoreLocatorUserGraphQl
app/code/Magefan/PosPlus
app/code/Magefan/PosBarcode
app/code/Magefan/PosBarcodeGraphQl
app/code/Magefan/PosCreditCardPayment
app/code/Magefan/PosCustomerCartGraphQl
app/code/Magefan/Pos
app/code/Magefan/Pos
app/code/Magefan/Pos
then remove this folder.
2. If the extension was installed via the composer and its files
If you need to update Magento POS System by Magefan, please follow the steps below.
Note: the updating instructions depend on the method the POS system was installed with.
Update using composer
If the POS system was installed via the composer (check if vendor/magefan/module-pos folder exists), then you need to run these simple CLI commands in Magento 2 directory:
composer remove magefan/module-NAME
composer require magefan/module-NAME ^x.x.x
# replace NAME with:
# pos - for Basic plan
# pos-plus - for Plus plan
# pos-extra - for Extra plan
# replace x.x.x with the version you want to use
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
If you want to upgrade to the Plus or Extra, check this guide on how to upgrade POS System plan.
Update using archive and FTP
If the POS system was installed via FTP (check if app/code/Magefan/Pos folder exists), then follow these commands:
1. Download the latest version of the POS system archive
You can install Magento 2 POS System by Magefan, using composer or archive installation methods.
Do you want us to install the POS System for you? Let our technical engineers do it – check out our installation service.
Note: if you want to install the POS System Plus or Extra please navigate to your Magefan Account > My Downloads > Install via Composer to get the composer installation instructions.
Installation via composer (recommended)
- Open command line.
- Using command "cd" navigate to your Magento 2 root directory.
- Run CLI commands:
composer config repositories.magefan-pos-m2 composer https://magefan.com/repo/46QpEMZJ8rjtfR0WbZ7b6oNdx9cw8bNX/fCmVkLKCEOcIR7UMf89kwPWRkiqrOP0Z/ composer require magefan/module-pos
# Authentication required (repo.magento.com)
# Get your Magento Marketplace authentication keys or use these:
# Username: 7c018006799466c681ad507e27904677
# Password: 289077c86e811661a8f7751828485d3a
php bin/magento setup:upgrade
php bin/magento setup:di:compile
Though most of the development tasks are done via developer mode, you have to switch Magento to production mode to ensure secure and fast environment.
Correspondingly to offer an exceptional customer experience you have to switch to production.
The only thing is, as during any static content deployment or DI compile your website will be down.
So to switch to production mode in Magento 2 with no downtime, you have to use the following command:
bin/magento magefan:zero-downtime:deploy-mode-set --mode production
It is part of the series of zero downtime deployment commands that enable you to customize Magento with no interruptions to customer experience.
All changes are deployed in the background, the same as switching Magento modes.
And the process is reversive. So if you need to switch back to developer or default, just use the following commands:
bin/magento magefan:zero-downtime:deploy-mode-set --mode developer
bin/magento magefan:zero-downtime:deploy-mode-set --mode default
Magento 2 back-in-stock notification is a great way to reduce cart abandonment due to product unavailability. It allows customers to sign up for product alerts and be notified when a product is back in stock.
However, it works only for registered customers and only in case you display out-of-stock products on the storefront. As an alternative, we offer you to create a Magento back-in-stock category where you gather all products you've restocked within a certain period.
Don't worry, you won't have to manually add and remove products from this category. You just need to enable Automatic Categories for Magento 2.
So, let's check how you can optimize your stock management with the Magento 2 back-in-stock or any other date-based category.
There are a few steps included in the process, but the result is worth the effort.
To create back-in-stock category for Magento:
1. Create Magento category
Before enabling any dynamic category rules you have to create a category which all the products
"In Stock" and "Out of Stock" options in Magento 2 store are important components of your inventory management. They give your customers information about the availability of the products.
Thus, it's recommended to display Magento 2 product stock status to improve customers shopping experience and show a professional, customer-oriented approach.
In Magento, you can set up stock for each product separately and configure the catalog stock options for all products at once. So, today, you'll learn how to do this.
To manage Magento 2 stock you need to navigate to Stores > Configuration > Catalog > Inventory.
Configure Magento 2 Stock Options
Magento 2 Stock Options apply to the entire product catalog. To configure it:
1. Enable the Decrease Stock When Order is Placed option in order to decrease the number of products in stock once someone purchases the product.
2. Enable the Set Items' Status to be In Stock When Order is Cancelled option to increase the number of products in stock once
Online is a new reality. So if you're wondering when is the right time to create eCommerce website in Magento, it's now.
Magento is a robust solution with more than 500 000 downloads and about 190 000 stores using it to cover their business needs. It is flexible, customizable, and scalable. This gives you plenty of opportunities to grow your business and deliver an exceptional online experience. That's exactly why Magento is best for eCommerce.
And since eCommerce sales are predicted to hit $6,5 trillion by 2023, chances are you don't want to catch the last train. Start acting now.
In this comprehensive guide, you will learn everything you need to know to create Magento website along with how to choose the right Magento edition. We will also discuss the price of Magento eCommerce development and the estimated time required to build Magento website.
There is too much to cover, so let's jump right to it.
What Magento Edition to Choose?
Once you decide to create Magento 2 store, you usually
Magento stores a lot of data in the database to optimize the performance of your store. However, once you update any of that data, the system starts indexing it to restore the changes in the database tables. That's exactly when the "One or more indexers are invalid. Make sure your Magento cron job is running" error appears in the admin panel.
It is one of the most common Magento errors all Magento users come across when working with Magento.
It might seem just annoying admin notice, but there is more than that behind it. Today you'll learn why "One or more indexers are invalid" appears and how you can easily fix it from the admin panel or via CLI.
Why "One or more indexers are invalid" error appears?
Since Magento is a complex system it has a special feature to schedule and run store tasks automatically — Magento cron jobs. Except for sending newsletters and notifications, updating catalog price rules and currency rates, cron tasks also run reindex.
So, usually, Magento reindex is run
Working with Magento 2, you can come across multiple errors or notices that keep destructive or interrupting the management process. One of the most common Magento errors is Access Denied HTTP error 403 which appears when you work with Magento 2 admin.
While many of you face this issue, few really know what it is connected with or how to solve this. So, in this guide, we'll provide a really simple and quick fix for the "Access denied" error to enable anyone with or without technical skills to deal with it.
However, let's define what is Magento "Access denied" error is in the first place.
What is Magento "Access denied" error?
Magento Access denied error is the most common Magento error that appears when you try to access a webpage without having the right to enter it. It usually appears in the Magento admin when you use incorrect admin panel credentials, create a new user with the wrong user role, or install Magento 2 extensions.
How to Fix the "Access denied" error in Magento 2?
Now
Implementing canonical tags helps to avoid duplicate content issues and indicate what pages you'd like to see in search results. However, it brings results just in case you implement canonical tags correctly. There are a lot of misconceptions about canonicalization which lead to a completely opposite of what you expect.
In this guide, we'll discuss the most common canonicalization mistakes with rel=canonical so you can avoid them while working on your SEO strategy.
If you think things like typos are your biggest problem when you add canonical tags to your website, I have bad news for you. Sometimes mistakes with rel=canonical are hidden in such plain sight it is hard to spot them.
Nevertheless, here are the most common canonicalization errors you should know about and avoid.
1. Wrong relative URLs
Like many other HTML tags, <link> tags also accept absolute and relative URLs. However, when applying canonical URLs many make the mistake of defining absolute URLs incorrectly.
Relative URLs