Magento 2 has a handy toolkit for static content management on the site that is called Content Management System (CMS). The toolkit consists of three main parts: pages, blocks and widgets. Pages allow us to manage content of an entire page. Blocks provide an ability to edit content of separate page elements. The main difference between blocks and widgets: if you need to change block parameters, you usually have to do it programmatically. Widgets are similar to static blocks, they allow to insert various content into static pages or static blocks. As a rule, widgets have configurable parameters that can be set up when adding it via admin panel.
When we were about to open our office in Bratislava we decided to create a series of posters inspired by Magento and eCommerce. We didn’t consider a possibility to have standard mainstream IKEA posters on the walls, so we wanted to create some custom artwork, which would represent our ideas, dreams and spirit in the best possible way. We have created 7 posters and each of them has a story behind. Lets dive into details.
In order to have a good and maintainable application, it’s very important to have a high quality product code. The code quality usually depends on the developer’s professionalism. But among the thousands lines of code something might be missed. Fortunately, there are few small but very useful utilities that can automate some routines and help you check the code using different rules for different coding standards. In PHP development there are two popular utilities for code validation: Code Sniffer and Mess Detector.
It’s interesting to know how Magento 2 works “under the hood” not only for developers but for all the people, who work with the platform. Not everyone has a possibility to dig in the code deeply enough in order to check the details. In this post we will put Magento 2 request flow in layman’s terms.
One of the key elements of building a store on Magento is the right choice of the hosting company. No doubt, stable hosting plays a significant role in a store functioning. In most cases, hosting resources have a direct effect on a Magento web store performance, therefore it is critically important to choose a trusted Magento optimized solution when reviewing hosting offers for the website.
Have you ever seen a page with “There has been an error processing your request” when using Magento 1 or Magento 2? If no, you are lucky. This page is usually displayed when an issue appears in a system execution flow. Magento processes such issues by creating a separate report file in the var/report directory and by showing the error page with the details. You can also see a similar page “Service Temporarily Unavailable” when the maintenance mode has been enabled. Did you know that you can easily customize these error pages?
Today I would like to get back to the 4th of July, when not only the USA became independent but also Meet Magento DE happened in the cozy city of Leipzig. It was not my first Meet Magento, but this time, I was the only one representing Atwix at the event and I should say that it was an extraordinary experience.
We’ve got the great feedback from you about our last Magento 2 wallpapers post. And as we promised, we have created new wallpapers this month. This time we used some classic pop culture characters to represent the leading positions of Magento products and give some respect to Magento Ninja Developers.
Bellow you will find 2 new wallpapers with several resolutions for desktops, laptops and lock screens for your phones. Need another image size? Just let us know in comments and we’ll make it for you.
Before running your store in production mode it’s very important to check as many Magento 2 performance aspects as possible, since even a minor performance issue might cost time and money in the future. Formally, a web application’s performance can be classified using two parts: frontend performance and backend performance.
During our work with Magento 2 Rich Snippets module we’ve noticed that the product list page has numerous errors if switched to the list mode. The errors were generated by the standard Magento 2 Luma theme, when attempting to aggregate rating markup rendering for each product in the product list. This blog post describes a configurable fix for the issue. We will have an opportunity to disable this fix for any custom theme which doesn’t have this error or in case the next Magento 2 version has a fix for this included.