Page 30 - Mari Skula

Your store homepage is a place where most of your visitors actually land. That's why adding as much information about your brand there is crucial. Testimonials, best sellers, new arrivals, brand story — you provide all the details here to make an impression. But don't forget that if you manage a blog, it deserves to be there too. So in this guide, you'll learn how to add blog posts to the Magento homepage and homepage sidebar. The makes the entire process super easy. Ready to start? Add Recent Posts to Magento Homepage You can add recent blog posts to the Magento homepage in two ways: through Magento widgets or directly into the CMS page content (using the widget tool). We'll go with the first option.  1. Navigate to Content > Widgets and click the Add Widget button. 2. Select Magefan Blog Extension - Recent Blog Posts as a widget Type, set the Design Theme and press the Continue button. Note: you can display featured posts on the Magento homepage the same way. Justihor

If you need to update  by Magefan, please follow the steps below. Note: the updating instructions depend on the method the Rocket Javascript extension was installed with. Update using composer If the rocket javascript module was installed via the composer (check if vendor/magefan/module-rocketjavascript folder exists), then you need to run these simple CLI commands in Magento 2 directory: composer remove magefan/module-rocketjavascriptcomposer require magefan/module-rocketjavascript ^x.x.x# replace x.x.x with the version you want to usephp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Update using archive and FTP If the rocket javascript module was installed via FTP (check if app/code/Magefan/RocketJavaScript folder exists), then follow these commands: 1. Download the latest version of rocket javascript extension archive from magefan.com. 2. Extractihor

If you need to update by Magefan, please follow the steps below. Note: the updating instructions depend on the method the Command Line Interface extension was installed with. Update using composer If the command line interface module was installed via the composer (check if vendor/magefan/module-cli folder exists), then you need to run these simple CLI commands in Magento 2 directory: composer remove magefan/module-clicomposer require magefan/module-cli ^x.x.x# replace x.x.x with the version you want to usephp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Update using archive and FTP If the command line interface module was installed via FTP (check if app/code/Magefan/Cli folder exists), then follow these commands: 1. Download the latest version of command line interface extension archive from magefan.com. 2. Extract archive. 3. Make the backupihor

If you need to update by Magefan, please follow the steps below. Note: the updating instructions depend on the method the Conflict Detector extension was installed with. Update using composer If the conflict detector module was installed via the composer (check if vendor/magefan/module-conflict-detector folder exists), then you need to run these simple CLI commands in Magento 2 directory: composer remove magefan/module-conflict-detectorcomposer require magefan/module-conflict-detector ^x.x.x# replace x.x.x with the version you want to usephp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Update using archive and FTP If the conflict detector module was installed via FTP (check if app/code/Magefan/ConflictDetector folder exists), then follow these commands: 1. Download the latest version of the conflict detector extension archive from magefan.comihor

If you need to update  by Magefan, please follow the steps below. Note: the updating instructions depend on the method the Product Widget Advanced extension was installed with. Update using composer If the product widget advanced module was installed via the composer (check if vendor/magefan/module-productwidget folder exists), then you need to run these simple CLI commands in Magento 2 directory: composer remove magefan/module-productwidgetcomposer require magefan/module-productwidget ^x.x.x# replace x.x.x with the version you want to usephp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Update using archive and FTP If the product widget advanced module was installed via FTP (check if app/code/Magefan/ProductWidget folder exists), then follow these commands: 1. Download the latest version of product widget advanced extension archive from magefan.comihor

If you need to update  by Magefan, please follow the steps below. Note: the updating instructions depend on the method the YouTube Widget extension was installed with. Update using composer If the youtube widget module was installed via the composer (check if vendor/magefan/module-youtube-widget folder exists), then you need to run these simple CLI commands in Magento 2 directory: composer remove magefan/module-youtube-widgetcomposer require magefan/module-youtube-widget ^x.x.x# replace x.x.x with the version you want to usephp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Update using archive and FTP If the youtube widget module was installed via FTP (check if app/code/Magefan/YouTubeWidget folder exists), then follow these commands: 1. Download the latest version of youtube widget extension archive from magefan.com. 2. Extract archive. 3. Makeihor

If you need to update  by Magefan, please follow the steps below. Note: the updating instructions depend on the method the Twitter Cards extension was installed with. Update using composer If the twitter cards module was installed via the composer (check if vendor/magefan/module-twitter-cards folder exists), then you need to run these simple CLI commands in Magento 2 directory: composer remove magefan/module-twitter-cardscomposer require magefan/module-twitter-cards ^x.x.x# replace x.x.x with the version you want to usephp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Update using archive and FTP If the twitter cards module was installed via FTP (check if app/code/Magefan/TwitterCards folder exists), then follow these commands: 1. Download the latest version of twitter cards extension archive from magefan.com. 2. Extract archive. 3. Make the backupihor

If you need to update  by Magefan, please follow the steps below. Note: the updating instructions depend on the method the Image Lazy Load extension was installed with. Update using composer If the image lazy load module was installed via the composer (check if vendor/magefan/module-lazyload folder exists), then you need to run these simple CLI commands in Magento 2 directory: composer remove magefan/module-lazyloadcomposer require magefan/module-lazyload ^x.x.x# replace x.x.x with the version you want to usephp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Update using archive and FTP If the image lazy load module was installed via FTP (check if app/code/Magefan/LazyLoad folder exists), then follow these commands: 1. Download the latest version of image lazy load extension archive from magefan.com. 2. Extract archive. 3. Make the backup copyihor

If you decided to remove , 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 extension has been installed in. 1. If you can find the extension files in the folder app/code/Magefan/RocketJavaScript then remove this folder. 2. If the extension was installed via the composer and its files located in the folder vendor/magefan/module-rocketjavascript then run composer CLI command to remove it composer remove magefan/module-rocketjavascript Once extension files have been removed, run these Magento CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Remove Extension Data (optional) Attention! This will clean all extension data. 1. Just in case please make a full backup (dump) of your Magentoihor

If you decided to remove , 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 extension has been installed in. 1. If you can find the extension files in the folder app/code/Magefan/Cli then remove this folder. 2. If the extension was installed via the composer and its files located in the folder vendor/magefan/module-cli then run composer CLI command to remove it composer remove magefan/module-cli Once extension files have been removed, run these Magento CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Remove Extension Data (optional) Attention! This will clean all extension data. 1. Just in case please make a full backup (dump) of your Magento 2 database. 2. Run next MySQL queriesihor

If you decided to remove , 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 extension has been installed in. 1. If you can find the extension files in the folder app/code/Magefan/ConflictDetector then remove this folder. 2. If the extension was installed via the composer and its files located in the folder vendor/magefan/module-conflict-detector then run composer CLI command to remove it composer remove magefan/module-conflict-detector Once extension files have been removed, run these Magento CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Remove Extension Data (optional) Attention! This will clean all Conflict Detector configurations, etc. 1. Just in case please make a fullihor

If you decided to remove , 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 extension has been installed in. 1. If you can find the extension files in the folder app/code/Magefan/ProductWidget then remove this folder. 2. If the extension was installed via the composer and its files located in the folder vendor/magefan/module-productwidget then run composer CLI command to remove it composer remove magefan/module-productwidget Once extension files have been removed, run these Magento CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Remove Extension Data (optional) Attention! This will clean all extension data. 1. Just in case please make a full backup (dump) of your Magento 2 databaseihor

If you decided to remove , 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 extension has been installed in. 1. If you can find the extension files in the folder app/code/Magefan/YouTubeWidget then remove this folder. 2. If the extension was installed via the composer and its files located in the folder vendor/magefan/module-youtube-widget then run composer CLI command to remove it composer remove magefan/module-youtube-widget Once extension files have been removed, run these Magento CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Remove Extension Data (optional) Attention! This will clean all extension data. 1. Just in case please make a full backup (dump) of your Magento 2 databaseihor

If you decided to remove , 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 extension has been installed in. 1. If you can find the extension files in the folder app/code/Magefan/TwitterCards then remove this folder. 2. If the extension was installed via the composer and its files located in the folder vendor/magefan/module-twitter-cards then run composer CLI command to remove it composer remove magefan/module-twitter-cards Once extension files have been removed, run these Magento CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Remove Extension Data (optional) Attention! This will clean all the data. 1. Just in case please make a full backup (dump) of your Magento 2 databaseihor

If you decided to remove , 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 a way the extension has been installed in. 1. If you can find the extension files in the folder app/code/Magefan/LazyLoad then remove this folder. 2. If the extension was installed via the composer and its files located in the folder vendor/magefan/module-lazyload then run composer CLI command to remove it composer remove magefan/module-lazyload Once extension files have been removed, run these Magento CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Remove Extension Data (optional) Attention! This will clean all extension data. 1. Just in case please make a full backup (dump) of your Magento 2 database. 2. Run nextihor

You can install by Magefan, using composer or archive installation methods. Installation via composer (recommended) Open command line. Using command "cd" navigate to your Magento 2 root directory. Run CLI commands: composer require magefan/module-lazyload# Authentication required (repo.magento.com)# Get your Magento Marketplace authentication keys or use these: # Username: 7c018006799466c681ad507e27904677# Password: 289077c86e811661a8f7751828485d3aphp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Installation using archive and FTP Download Image Lazy Load Extension ZIP-Archive from magefan.com website (not GitHub or other sources). Extract files. Copy app folder from the archive to your Magento 2 folder. In a command line, using "cd", navigate to your Magento 2 root directory. Run CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephpihor

You can install by Magefan, using composer or archive installation methods. Installation Method via composer (recommended) Open command line. Using command "cd" navigate to your Magento 2 root directory. Run CLI commands: composer require magefan/module-cli# Authentication required (repo.magento.com)# Get your Magento Marketplace authentication keys or use these: # Username: 7c018006799466c681ad507e27904677# Password: 289077c86e811661a8f7751828485d3aphp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Installation using archive and FTP Download Command Line Interface Extension ZIP-Archive from magefan.com website (not GitHub or other sources). Extract files. Copy app folder from the archive to your Magento 2 folder. In a command line, using "cd", navigate to your Magento 2 root directory. Run CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephpihor

You can install by Magefan, using composer or archive installation methods. Installation Method via composer (recommended) Open command line. Using command "cd" navigate to your Magento 2 root directory. Run CLI commands: composer require magefan/module-conflict-detector# Authentication required (repo.magento.com)# Get your Magento Marketplace authentication keys or use these: # Username: 7c018006799466c681ad507e27904677# Password: 289077c86e811661a8f7751828485d3aphp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Installation using archive and FTP Download Conflict Detector for Magento 2 ZIP-Archive from magefan.com website (not GitHub or other sources). Extract files. Copy app folder from the archive to your Magento 2 folder. In a command line, using "cd", navigate to your Magento 2 root directory. Run CLI commands: php bin/magento setup:upgradephp bin/magentoihor

You can install by Magefan, using composer or archive installation methods. Installation via composer (recommended) Open command line. Using command "cd" navigate to your Magento 2 root directory. Run CLI commands: composer require magefan/module-rocketjavascript# Authentication required (repo.magento.com)# Get your Magento Marketplace authentication keys or use these: # Username: 7c018006799466c681ad507e27904677# Password: 289077c86e811661a8f7751828485d3aphp bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these . Installation using archive and FTP Download Rocket Javascript ZIP-Archive from magefan.com website (not GitHub or other sources). Extract files. Copy app folder from the archive to your Magento 2 folder. In a command line, using "cd", navigate to your Magento 2 root directory. Run CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephpihor

You can install by Magefan, using composer or archive installation methods. Installation via composer (recommended) Please navigate to your Magefan Account > Downloads > Install via Composer to get the composer installation instructions. Installation using archive and FTP Download Product Widget Advanced Extension ZIP-Archive from magefan.com website (not GitHub or other sources). Extract files. Copy app folder from the archive to your Magento 2 folder. In a command line, using "cd", navigate to your Magento 2 root directory. Run CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these .

You can install by Magefan, using composer or archive installation methods. Installation via composer (recommended) Please navigate to your Magefan Account > Downloads > Install via Composer to get the composer installation instructions. Installation using archive and FTP Download YouTube Widget Extension ZIP-Archive from magefan.com website (not GitHub or other sources). Extract files. Copy app folder from the archive to your Magento 2 folder. In a command line, using "cd", navigate to your Magento 2 root directory. Run CLI commands: php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deploy Note: if you don't want your website to be down during deployment, try these .