Adminnotification or Magento is phoning home.

How this feature works and what we should do with it


There is this tiny module, which goes us on our nerves all the time we install a new magento. It is called Mage_Adminnotification. If you don't know, what I'm talking about, maybe this picture will help you:

This little bar should be interessting for administrators, store owners, marketing and product people, but not for us developers. It is just annoying.

The workflow behind

Whenever you request a page, the Mage_AdminNotification_Model_Observer::preDispatch() method is called, which listens on controller_action_predispatch.

It checks wether an admin is logged in and checks for updates

if (Mage::getSingleton('admin/session')->isLoggedIn()) {

In checkUpdate() it is checked, wether the last request for updates was more than an hour ago, if yes, the data are requested from the Magento Notifications RSS Feed and written to the database.

// app/code/core/Mage/AdminNotification/Model/Feed.php:75
if (($this->getFrequency() + $this->getLastUpdate()) > time()) {
    return $this;

$feedXml = $this->getFeedData();

What we should do with it

If you ask me, this notifications are awesome. I saw a few modules which use this notifications to send informations to their module buyers. We should have an easy to use extension which only needs a configuration node with an url. This url is checked regularly for updates for all the people which USE the backend.

It is really important to inform the shop owners about security problems of modules, but although to achive, that the shop owner update our modules.

Avoid spam

Please be careful with this feature. Don't send them offers, discounts or informations about new modules. This is an information channel, not a marketing channel!

Phoning home

I think this URL is only used inside of magento, this means, every request to this RSS feed is a magento shop.

If you don't want these informations or don't want, that magento knows, that you installed their awsome software, you can disable the observer with this snipplet in a config.xml of you module:


Thanks to Fabrizio Branca for his gist.