All orders have an order status that is associated with a stage in the order processing workflow.
The state describes the position of an order in the workflow. By default, Magento store has a set of predefined order statuses and order state settings. All the available order statuses can be found in admin panel under
Stores -> Settings -> Order Status. Sometimes we need to create a new order status and state. Let’s figure out how to create a new order state and status programmatically in Magento 2.
In this blog post, I would like to share a pretty interesting and not obvious solution on how to join some additional details to cart item block on checkout cart page.
Let’s say we need to add the “Brand” custom product attribute and show its value within a specific block on the product view page and checkout cart page. It’s very simple in the scope of the product page, but how to deal with number cart items on checkout cart page. There are a couple of issues which you may face with. We will cover them further.
Magento 2 implements the service contracts design pattern – a set of PHP interfaces that are defined for a module. A service contract includes service and data interfaces, which hide business logic details from service requestors such as controllers, web services, and other modules.
Magento 2 Certified Solution Specialist is out there for a while and some of you may have already registered and are up to get more familiar with what to expect from the exam. However, some of you might still be wondering if it’s worth spending time on the preparation and test itself.
Magento 2 is known to be a powerful and feature-rich eCommerce platform. It delivers decent page load times but might be quite sluggish under heavy customizations.
Part of the performance problem might be a poorly developed custom theme. On one hand the default Luma and Blank themes are quite fast. On the other hand some of the customized themes are slow and could make your online shop a nightmare to buy from.
Magento Functional Testing Framework was presented by Tom Erskine during contribution day which followed MageTestFest, which took place in Amerfoort in November last year. Right now it’s under heavy development, there were already 2 releases and it reached version 2.0.3.
System configuration is a very useful feature of the Magento platform. At the same time, it’s easy to create new configurations for your own custom solutions. We’ve already touched the topic on how to add new system configurations with different fields. Today I would like to describe one more type of fields, which can be used depending on your needs. This is a dynamic field block. Sometimes we need to have some complex data managed via system configurations, or we even don’t know beforehand the number of records to be added. In this case it’s impossible to create the exact fieldset in a system configuration tab. Therefore, dynamic fields will be really useful.
2017 has truly been the year of Community Engineering for Magento. For many years we’ve been hearing voices from the Magento community on how great would it be if we were allowed to work on fixing bugs and improving Magento core code… And now we’re living this dream. Moreover, this dream already delivers: 24% of the code shipped by Magento in 2017 came from the community. And all this came from 511 unique contributors. Impressive, isn’t it? And what’s helped the success?
It’s well known that Magento team announces new platform upgrades quite often. There is a minor upgrade every second month and a more critical upgrade with new features and more changes to the core almost every quarter on average. If we look back, since the release of Magento 2.0 in November 2015 there were around 30 releases for Magento Open Source and Magento Commerce. Looks like a lot, doesn’t it? So the question arises: do these changes actually bring any value to the website?
After the latest Database data format changes in Magento 2.2.x version, there is a need to convert existing PHP serialized data to JSON format. The new release provides upgrade scripts that convert Magento serialized data. But how to deal with custom extensions, which also use automatic serialization mechanism provided by Magento framework? Thankfully, Magento took care of that too.