We are going to talk about event system approach in development. The event is a very flexible way to extend application logic. This approach is actual in both Magento 1 and Magento 2. Let’s go ahead and check how it works.
Redirects is a widely used approach not only in Magento but in most of other web applications. Saying “redirect” we usually mean a rule or a set of rules for sending user from one URL to another. Using Magento 1 you can easily handle redirects by writing just one line of the code, but in Magento 2, because of its new architecture based on Dependency injection, the process of building a redirect is a bit more complex. Let’s review a new redirect creation by building a simple extension that redirects user from a category page to a product view page if there’s only one product in this category.
Localization or internationalization process means adapting a software to different languages, regional particularities and technical requirements of a target market. Well-designed software usually does not require code changes and deep engineering knowledges for localization or/and internationalization processes.
As you may know, Magento released security patch SUPEE-7405 on 20th of January 2016. This patch contains changes to more than 50 core files and in this article we are going to review the changes and potential issues that could be faced after the patch implementation.
In the part 2 we have described the powerfulness of terminal multiplexers and reviewed one of the most popular terminal utilities – Tmux. Such kind of multiplexers might greatly boost your performance in handling different CLI operations. Let’s go forward and imagine the trivial situation, when you have created your own handy CLI environment with many terminal windows in one tab or so. You have everything under your hand but sooner or later you have to reboot your computer because of a new system update or installing some applications that require the system restart. In this case, your terminal multiplexer process will be shut down and you will lose all your settings. Fortunately, there are few lovely utilities that help save all your windows/tabs configurations and allow to recreate the entire tabs with windows.
In the previous article we wrote about few improvements that you can implement for your Command Line Interface (CLI). But “Perfection knows no limits” and in this article we would like to dig deeper and describe few additional solutions that will make your CLI more powerful in your hands.
Many developers/system administrators sooner or later face with the situation when one terminal window or even few terminal tabs is not the most convenient solution. You want to have everything close at hand: to see all terminal windows at the same time. Sure, you can tile all terminal windows or improvise in some other way but for making the things easier let’s give a shot for a terminal multiplexer.
Every change should be carefully tested before the release on the live store to make sure that it does not break any functionality. The most important is to check the main places such as customer registration process, customer log in to the account, adding different types of products to the shopping cart, checkout steps etc. We need to check the mentioned parts for every modification made for the website, these repetitive actions take a lot of time. But what do you think – is it possible to speed up and improve this process? As one of the most obvious solutions is to develop functional tests for the website and, in such way, we will automate all the actions.
Magento is one of the biggest and most popular e-commerce platforms written in PHP. The very first Magento release, known as ‘Bento’, is dated to March 31, 2008. For that time the actual PHP version was 5.2. Nowadays we are happy users of Magento 1.9 that supports PHP versions up to 5.5.x (officially announced), but the platform also smoothly runs on PHP v5.6. Recently we had good news about Magento 2.0 release and that fact is really great. From the opposite side, the first version of Magento will lose official support quite soon but, we are sure, there are many merchants who will stick with Magento 1.x for the next couple of years because of different reasons.
Most of modern softwares have a handy graphical user interface that allows executing different operations by few actions. We are talking not only about user interfaces for social networks, messengers, email clients etc. You can even create an entire website or a standalone application by few clicks and labels using different automated software with a good UI toolkit. That’s really great because it involves more and more people into attempts to create something new and special. However, what about people who stand behind this scene – developers, who create “software for creating a software”?
Magento has released a new security patch SUPEE-6788, and we would like to share our experience with its installation troubleshooting. We are describing this topic assuming that you’ve already checked a web store on magereport.com and implemented the security recommendations like closing access to var directory, downloader, changed the URL to the admin panel to more secure etc. We will also try to avoid the discussion of the admin routes compatibility here because the patch already contains the back routes compatibility. Therefore, the main goal of this article is to make your store functioning correctly after applying the patch.
