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”?

When we started working with OroCRM we have met problems with differences between Symfony core commands and OroCRM commands. That is why we decided to share this experience and prepared a list with the most common commands for everyday work with OroCRM such as cache clearing, migration, entities.

If you are a web developer, there’s one thing you are doing from day to day, no matter how good you are. You can write a good code, and you may know your work like a pro, but usually you have to integrate your solutions into different systems which were, unfortunately, created by someone else. Here we meet the thing that can turn into the nightmare for you if you are following a wrong way – the debugging.

When starting Magento development, first thing you find out that in order to see the changes you have to clear the cache. There is also an option to disable the cache completely, but performance wise – it’s not a very smart move. As your experience on the system grows you are getting to know which exact cache to clear to see the changes, be it config, layout, FPC cache or any other. Nevertheless, these operations are pretty cumbersome as admin session times out from time to time. You may also know that enabling template hints is not a quick operation either.

I have often seen custom shell scripts on Magento instances, be it a script testing out some code snippet or an attribute installation script which hadn’t made it’s way to a separate module. This will create a mess in the files structure as there are quite a lot files already residing in the root folder. There is, however, the dedicated place where these scripts should be placed and this place is the ‘shell’ folder in the root of every Magento installation