Page 30 - Blog

Sometimes you can see notifications in Magento 2 panel that are displayed over and over again. This is Magento 2 admin notifications. To stop showing these messages you need to mark them as read.  For this please navigate to Noficiations Manage page. Click on the bell icon in the top right corner in the admin panel and then press the "See All (X  unread)" link. Select the messages you want and mark them as read. Tha's all. However, there are some notifications that are useful for you, as the admin, to receive.  e.g. new review, disabled cache and low stock notifications Check out to receive emails about changes on your store directly to your email box.

If you have installed or updated Magento 2 extension and received the error message e.g.: Module 'Company_Module' from 'app/code/Company/Module' has been already defined in 'vendor/company/module'. this means that you have 2 versions of the extension: 1) in the folder app/code/Company/Module2) in the folder vendor/company/module In vendor folder Magento stores all components (extensions, themes, language packages) that have been installed using Composer. As installing or updating extensions via Composer is preferred, you need to remove the extension folder app/code/Company/Module (please don't forget about a backup before removal) and run installation commands. Example: If you get the error: Module 'Foo_Bar' from 'app/code/Foo/Bar' has been already defined in 'vendor/foo/module-bar'. You need to: 1. Make a backup of "app/code/Foo/Bar" folder 2. Remove "app/code/Foo/Bar". 3. Run commands php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento setup:static-content:deployihor

Originally you cannot reindex Magento from admin panel. To perform you need to use PuTTY or another terminal application to run the CLI commands, e.g. command for reindexing: php bin/magento indexer:reindex So, most often developers use . However, wiith FREE Magento 2 Command Line (CLI) Extension by Magefan you can run CLI commands directly from Magento 2 admin panel. To reindex Magento 2 from admin panel: 1. Install the Magefan CLI extension to see a new menu item "System > Command Line" to be added to the admin menu. 2. Enter your current admin user password (for security reasons) On the "Comand Line" page and enter the Magento 2 reindex command. 3. Press ENTER to start the reindexing after you have entered the "php bin/magento indexer:reindex" command. Result: With the Magefan CLI module, you can run any other Magento 2 commands. Check out the video to see how easy it actually is:

If you use Magento 2.2.x or greater and receive the error message: 1 exception(s): Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'block', attribute 'class': [facet 'pattern'] The value '\Magento\Framework\View\Element\Text\ListText' is not accepted by the pattern '[A-Z][_a-zA-Z\d]*(\\[A-Z][_a-zA-Z\d]*)*'. Line: 982 Element 'block', attribute 'class': '\Magento\Framework\View\Element\Text\ListText' is not a valid value of the atomic type 'blockClassType'. Line: 982 Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'block', attribute 'class': [facet 'pattern'] The value '\Magento\Framework\View\Element\Text\ListText' is not accepted by the pattern '[A-Z][_a-zA-Z\d]*(\\[A-Z][_a-zA-Z\d]*)*'. Line: 982 Element 'block', attribute 'class': '\Magento\Framework\View\Element\Text\ListText' is not a valid value of the atomic type 'blockClassType'. Line: 982 You need to check all layout files in your theme and custom extensions, they may have aihor

If you need to extend Magento 2 Blog Module by Magefan and add a new custom text field to Blog Post edit page in Magento 2 Admin panel (Content  > Blog > Posts) you must to create a simple custom Magento 2 Extension. You can download a sample extension from our GitHub page or you can create it manually using the steps below: 1. Create composer.json file app/code/Magefan/BlogCustomField/composer.json { "name": "magefan/module-blog-custom-field", "description": "Implements Blog functionality on Magento 2 store", "require": { "magefan/module-blog" : ">=2.8.0" }, "type": "magento2-module", "version": "2.0.0", "license": [ "OSL-3.0", "AFL-3.0" ], "autoload": { "files": [ "registration.php" ], "psr-4": { "Magefan\\BlogCustomField\\": "" } }}   2. Create registration.php file app/code/Magefan/BlogCustomField/registration.php <?php/*** Copyright © Magefan (support@magefan.com). All rights reserved.* See LICENSE.txt for license details (http://opensource.org/licenses/osl-3.0.php).*/ \Magento\Framework\Component\ComponentRegistrar::register(ihor

If you receive the error message "No such entity.", "No such entity with" or "No such entity with customerId" in Magento 2, the issue usually occurred when you try to load not existing object via Magento 2 Repository Class. To debug this , please open the following file: vendor/magento/framework/Exception/NoSuchEntityException.php and at the beginning of the __construct method temporary add debug backtrace code: foreach (debug_backtrace() as $_stack) {    echo ($_stack["file"] ? $_stack["file"] : '') . ':' .        ($_stack["line"] ? $_stack["line"] : '') . ' - ' .        ($_stack["function"] ? $_stack["function"] : '');}exit(); example: public function __construct(Phrase $phrase = null, \Exception $cause = null, $code = 0) {     foreach (debug_backtrace() as $_stack) {        echo ($_stack["file"] ? $_stack["file"] : '') . ':' .            ($_stack["line"] ? $_stack["line"] : '') . ' - ' .            ($_stack["function"] ? $_stack["function"] : '');     }    exit();ihor

When you update Magento 2, or switching git branches on your dev environment, sometimes you can get the error: The following modules are outdated: Vendor_Module schema: current version - x.x.x, required version - z.z.z  To solve this issue, please do next: 1. Try to get the latest extension code. Run CLI command in the Magento root directory: composer install If you get troubles with running this command, then just skip it, and move to step 2. 2. Try to upgrade your database. Run CLI command: php bin/magento setup:upgrade 3. If step 1 and 2 didn't help, then navigate to your database and run this SQL Query (don't forget to change the text in bold): UPDATE `table_prfix_setup_module` SET schema_version="z.z.z", data_version="z.z.z" WHERE  module="Vendor_Module"; "table_prfix_" can be found in app/etc/env.php, note that it can be empty.    

Usually, you get the error bash permission denied when running some script/file that does not have execute permissions. It is one of the . All you need to do to fix it is to change file permissions and add executive one. To fix the bash permission denied error follow these steps: 1. Open terminal (shell) 2. Navigate to the folder with the script 3. Run the CLI command to change file permission settings: chmod +x path_to_file/file_name For example, if you run a : bin/magento ... and get the error: bash: bin/magento: Permission denied You need to add an execute (x) permission to the bin/magento file. For this, please run the CLI command: chmod +x bin/magento In case of Magento 2 you can also use the next command to avoid the issue (php before bin/magento): php bin/magento ... Another issue you might face when running bin/magento commands, like the following ones, is the website breakdown during deployment: bin/magento setup:upgrade bin/magento setup:di:compile bin/magentoihor

Use the following code to insert the template block in WYSIWYG (Important! add it in inside double curly braces):  block class="Magento\Framework\View\Element\Template" template="Magefan_Blog::content/block-template-example.phtml" The template identifier VendorName_ModuleName::some-template.phtml should be changed. Attention! You can not use the block tag in the WYSIWYG product and category attributes. To make changes, install the magefan/module-catalog module.

Your store position in Google or other search engines depends on your SEO strategy. There are a lot of factors SEO is based on and even more things that depend on SEO, website traffic in particular. is one of the best ways to drive more traffic to your website. So we added the best SEO practices to our Blog Extension to make your blog pages rank. And in this article, you're going to learn about blog permalink settings — SEO-friendly blog URLs. To manage Blog Permalink Settings, go to Stores  > Configuration > Magefan Extensions > Blog and find Permalink Settings section. Blog Index Page Route 1. Blog Route indicates the blog's base URL.  If you want the pages of the blog to be accessible from https://mystore.com/news/, please set 'news' in this field. 2. Enable the Auto-redirect to No-Slash URL option to set all blog URLs to end without a slash. 3. Set the Permalink Type. If you choose Default, the URLs of the blog pages will look as follows:  https://mystore.com/{blog_route}/post/post-title/https://mystore.com/{blog_route}/category/category-title/https://mystore.com/{blog_route}/archive/2017-10/ihor

Magento 2 blog categories are a great way to improve blog navigation and organize your posts according to different criteria. Creating categories in , you improve customer experience and allow readers to find things they are interested in faster and more effectively. So, in this guide, you'll learn how to create blog categories and manage them. Note: before we start, note that some of the options described here are available only in the . Create Blog Categories in Magento We recommend creating categories before you create posts. However, you can also add a new category when . First, navigate to the Content > Blog > Categories and press the Add New Category button. 1. Fill out general information Enable your category and enter a Title. Then assign a category to Parent Category, if any. Set the Position of the category in the sidebar and choose whether to Include a category in the top navigation Menu. Additionally, you can set whether to Include a category in Sidebar Tree. 2. Create contentihor

Before you install Magento 2, make sure that the webserver (such as ) and are configured and meet Magento 2 requirements. Install the virtualhost script for the LAMP server, and create a new virtual host dev.mymagento.com, run the command: virtualhost create dev.mymagento.com Open this link in your browser and make sure you can see the content, not the error. Download the archive with the latest version of Мagento 2. When downloading, you can select the "Include sample data" option, so that after you install Magento 2 test products and categories are available in the store. Once you download the archive, place the folders and files from it in your domain directory /var/www/devmymagentocom. Edit the virtual host domain configuration file, run the command: gedit /etc/apache2/sites-available/dev.mymagento.com.conf and change the string DocumentRoot /var/www/devmymagentocom to DocumentRoot /var/www/devmymagentocom/pub The pub folder must be the root one for the webserver. After saving theihor

When you , you shouldn't forget about their appearance on the and post lists. Especially if you have some short content added for the post. The "read more" is a call to action that encourages visitors to click on the posts.  So, in this guide, you'll learn how to add the "read more" button in Magento 2 blog in two different ways. Add "read more" via WYSIWYG editor Navigate to Content > Blog > Posts and select a blog post to which you want to add the "read more" button. Scroll down to the Content section. Insert Pagebreak tag wherever you want. 4. Save a post one you finish and go to the checkout to see the result. Add "read more" via Page Builder Go to Content > Blog > Posts and select a necessary blog post. Scroll down to the Content section and start editing using the page builder. Insert HTML Code block wherever you want to add the page break. 4. Start editing the HTML Code block. 5. Add the "ihor

Our provides multiple import options for you to move your blog content from one blog extension or platform to Magento 2. In this article, you will learn about WordPress. Take the following steps to import WordPress blog to Magento 2: Set the Database Name where you run the WordPress Blog. Enter the User Name and Password. Specify the Database Host. Enter the Table Prefix. Choose the Store View you want WordPress Blog to be imported to. If you want to see the WordPress blog import to Magento 2 in action, check this short video: Note: only the image links will be imported, so you have to move your WordPress blog images to Magento pub/media/magefan_blog folder for them to be displayed. Troubleshooting Due to security reasons, databases are configured to accept requests only from the same server as they are (localhost), and it blocks all requests from outside (another server).  So, if you have issues migrating WordPress blog to Magento 2, you have to move your WordPress database to theihor