Monthly Archives: September 2014

Work from anywhere

I have worked remotely for a few years. Actually I have worked remotely almost since the beginning of my career. There was a time when I was heading to the office almost everyday, but it was just “almost” and I wasn’t able to hang on there for more than 5 or 6 hours.

I love the mobility and ability to change the place I’m working from. Usually I work at my home office or on the terrace. Catching up with other team members is also important so this month I worked for a few days in our Bucharest office, and next month I’m going to start working in a co-working space once or twice a month. Sometimes changing to a completely different environment helps me to maximize productivity and keeps me happy.

This summer I got a chance to stay in a cottage house in Uniszowa for a week and work from there. It’s a place located in the Western Carpathians, so calm that it’s hard to see any house in a neighborhood there. The only thing I needed to figure out was the internet access. Fortunately it was really easy as the cottage was in a 4G LTE network coverage so connection was even better than at home. I was only missing a comfortable chair there but a sunbed did the job for these few days. Photo above shows a lovely sight I had from my work space.

I’m looking forwad to go to Uniszowa again this year. However, I need to wait til next summer to try a few crazy ideas about working from other calm and quiet places – work from forest or meadow :-)

What other places do you recommend for remote work?

Top 10 n98-magerun command calls

n98-magerun is a very useful tool when working on Magento stores. It saves time and makes a lot of Magento development related tasks much easier. Check out a list of my 10 favorite commands.

1. dev:module:rewrite:conflicts

This one is a must have. It’s a good replacement for an Extension Conflict module which I have been using before I found the n98-magerun. It shows rewrite conflicts in a clean ASCII table:

2. mysql-client

Command opens a mysql command line client without need of looking for a host, a port and credentials in local.xml file.

However, it doesn’t work on a server with proc_open() function disabled.

3. cache:flush

It flushes all Magento caches. If a store uses filesystem cache, this command isn’t much more helpful than simple  rm -rf var/cache* var/full_page_cache/* . However, when using the n98-magerun I don’t need to wonder what cache type is used in a store and this command provides an interface working for all cache types.

The only glitch is that in some cases it doesn’t clean cache if file permissions are not correct.

4. sys:cron:list

Prints list of all active CRON jobs configured in a Magento store. It shows output in readable way, showing a job code, minutes, hours, days, month and week days.

Another usable command related to CRON may be sys:cron:history which lists recently finished CRON jobs.

5. sys:setup:run

It’s useful to run database updates from a command line when installing an extension or upgrading Magento.

Recently I used that when working on a Magento upgrade from 1.12 to 1.14. Frontend kept throwing error as PHP code was trying to use things which haven’t existed in the database yet, but sys:setup:run command dealt with that perfectly.

6. dev:theme:duplicates

This could be used when working on templates, to clean them from not needed files. I ran that command in 3 projects I’m working on and it found a few duplicated templates.

7. sys:info

Command allows to quickly show an overall picture on the store. It shows a store edition and version, list of vendors coming from all code pools and a few other information. Additionally it shows basic factors which can determine the store size – amount of attributes, categories and products.

It’s handy when starting to work on an already existing site.

8. sys:check

It checks for missing system paths such as media/, var/ or a local.xml config file and checks if required PHP modules are installed. For example on my local server it keeps complaining about a missing index.php.sample file and about missing bytecode cache extension. I will need to get rid of this to get a nice green output :-)

Additionally it checks if each base URL contains dot, however I don’t get this part.

9. dev:console

This opens an interactive console with Magento initialized. It’s marked as experimental but works pretty well. It allows to run code in interactive way, most useful when I need to check multiple objects one by one eg. go through blog posts. For example to open console run:

And then run code to dump the blog post data:

Or order:

10. sys:modules:list

It lists all modules along with fields like code pool, key, version and status.

Documentation says it’s possible to filter list by a code pool and a status, but I couldn’t get it working. It simply shows nothing when I use any filter. However, even without filtering it’s pretty useful.

I chose these 10 commands as most interesting, but there are many other handy tools: a command for working with database dumps, a command for debugging Magento configs and all toggle commands which allow to enable/disable things like a cache, a demo notice, template hints and many more.

Take a look on to see all of them or better just play with the tool. Also make sure to subscribe my RSS feed or my twitter as soon I will talk more about cool n98-magerun use cases.

How to handle zero dollar checkout

Zero Dollar Checkout is a core Magento payment method available to handle checkouts with a zero total. Of course it’s not really desired to have too many  zero dollar checkouts in e-commerce, but it can occur in some cases. It could be an order completely paid with reward points, an order with a 100% discount code or an order containing only a free item.

If method is enabled and the order total is zero, it becomes visible and the customer can choose to finish checkout without using other payment methods. However, if other payment methods are still enabled and displayed, it can confuse the customer. I saw use cases in which the customer tried to pay $0 using credit card payment method. It failed as payment gate throws error in such case.

A good way to handle that is setting Minimum Order Total configuration value to $0.01 for all methods other than Zero Dollar Checkout. Then all other methods will be automatically hidden if total is $0.

Unfortunately not all methods implement Minimum Order Total field.

Luckily, it’s very easily to fix that. It’s only about adding a new configuration field for the payment method.

I’ve added a new field for my payment method in system.xml file under XML path “config -> sections -> payment -> groups -> your_payment_method_key -> fields”:

And then added default value in config.xml file under XML path “config -> default -> payment -> your_payment_method_key”:

That’s it, the rest should be automatically done thanks to Magento core Mage_Payment_Block_Form_Container::_canUseMethod() method.

I see that as good practice to implement Minimum Order Total field in each method and use that properly. Don’t try to process $0 with payment gates.

Photo: it’s Common Raven, my favourite bird, which we spotted in way to Detiffoss waterfall in Iceland.


A few years ago, in  2006 I started a PHP and Zend Framework blog under domain. The intention was to share my Zend Framework knowledge and experience with Polish developers while the framework grows. I stopped writing in 2009 as it was really hard to find time for blogging . It was even harder to start blogging again because a lot of important things started happening in my life – a serious job, family, children and a lot of hobbies.

Now I’m going to start blogging again. However, my areas of expertise have evolved a bit. Now the main focus is Magento. I’m going to share my Magento knowledge as well as general e-commerce and work experience.

My previous blog was naruniec.INFO and contained mostly information. This one is naruniec.ME and will also include few things about me.