As you might know Varien is going to release Magento 1.4 stable in this month. In 1.4 there are a couple of changes that infect extensions like ours. So it’s important for you to know which versions of our extensions are compatible with Magento 1.4 and which are not.

Teaserbox: All versions above/equal 1.2 are Magento 1.4 compatible
Productslider: All versions above/equal 1.6 are Magento 1.4 compatible
Superstage: All versions above/equal 1.5 are Magento 1.4 compatible

It’s very important to only use compatible versions together with Magento 1.4. Using older extension versions on Magento 1.4 shops will lead to problems.

We are very happy to annouce, that we have released a new Community Extension called Magento Teaserbox – the best thing about it, it’s totally free. The extension is available on Magento Connect and has surpassed 100 downloads in total already.

 
So, if you are interested in a flash based Magento extension which can handle easily your recently added or featured products, this module might be the right tool for your needs. The possibilities are almost boundless. Features like auto-sliding your images the vertical or horizontal way within a specific time period, which you can define within the Magento backend, are implemented. Find more features on the product page itself. If you have any trouble, just take a look at the official extension forums and skim the threads or open a new one. You will also find a showcase thread where you can post your store’s URL containing Magento Teaserbox. Now take a look at the demo.

One of the things you have to deal with when switching from another e-commerce software to Magento are URL redirects. Over the past years you (hopefully) received many incoming deep links. You surely know that incoming links are one of the main ranking factors for most search engines. So when you switch to another e-commerce software, these deep links get useless because they point to subpages that don’t exist (unless you don’t have the exact same URL structure in your new shop). The common way to solve this issue is just to do a 301 redirect (permantly redirect) from the old URLs to the new ones. You have the possibility to define the redirects in your .htaccess file or with the Magentos build-in “URL Rewrite Management” (in the Backend “Catalog” -> “URL Rewrite Management”).

However, both of these methods have some disadvantages. The .htaccess file could be overwritten when you update Magento. Also if you change the URL structure inside Magento you’ll have to update the .htaccess file each time. The Magento build-in Tool is nice if you only have to do a couple of rewrites. But let’s say you have 2000 or more redirects you want to define… you can take a week off, because you have to define each redirect manually.

I decided to write a small extension to give you an alternative way of defining redirects. Just named it “Massredirect”. You can download it here. For installation just copy it into your Magento main folder and run the command “tar -xvf massredirect.tar”. This will extract the extension files to the desired places. Before you start defining the redirects, make sure you got rid of the cache and the extension shows up in the advanced tab of the configuration site. To define the redirects open the CSV file “redirects.csv” located in the folder “/app/code/local/Velite/Massredirect/etc/” in a text editor. Each row in the CSV defines a redirect. Basically there are two possibilties of defining a redirect:

Possbility 1:

old-URL;type;entity_id;website_id;store_id

for example:

www.myshop.com/product.php?productid=123;product;5;1;1

This will redirect a user typing the URL “www.myshop.com/product.php?productid=123″ to the product page of the product with the ID 5 on the default website and store. Notice that the URL must be specified without “http://”. “type” can either be “product” or “category”.

Possbility 2:

old-URL;new-URL

for example:

www.myshop.com/product.php?productid=123;www.myshop.com/my-nice-product.html

Keep in mind that the second possbility has the same disadvantage like defining the redirects in the .htaccess file. This means, if you change the URL structure inside of Magento you will also have to update the CSV. However, you can mix both possibilities in the CSV file.

So how does this extension work?

Basically the preDispatch method of the Mage_Core_Controller_Varien_Action gets observed (the event is named “controller_action_predispatch”). If the requested action is “noRoute”, the CSV gets parsed and looked up if there is a mapping available for the typed-in URL. In that case the user (or the bot) gets redirected to the new URL (with a Status 301-Redirect).

Feel free to make any further suggestions.

Magento Experts (Mxperts) is the number one Magento related Blog in Germany. Today they released a Magento extension that allows you to easily load jQuery into your Magento store. You just have to install the extension and jQuery gets automatically loaded. In the configuration menu of your Magento backend there is a new section, where you can enable different settings like loading jQuery in the minified/compressed way or turning on/off the conflict mode. The extension keeps your jQuery version up-to-date but also allows you to specify a certain jQuery version to be loaded.

I was actually interested in how the extension places the jQuery script-tag into the html header. So I had a look into the source code. What they basically do is overriding the block Mage_Page_Block_Html_Head with their own Mxperts_Jquery_Block_Page_Html_Head. Within their custom block they override the getCssJsHtml() method and append their script-tags inside of it. At the the end they call the getCssJsHtml() method of the parent class Mage_Page_Block_Html_Head, merge their script tags with the rest of the head content and finally return it. The extension does perfectly what it was made for. Mxperts did a great job indeed!

I know it’s very common to override core classes within Magento extensions. I just asked myself what happens if two or more extensions override the same core class. To test what happens, I created a little extenstion with a block class which overrides the Mage_Page_Block_Html_Head class (just like the jQuery extension does). As I already supposed, only one override has effect in this case.

This means, the more extensions (which modify a core class) you install in your Magento Admin Panel, the bigger is the risk that two extensions override the same core class. In order to solve such a conflict I guess you either have to merge both conflicting classes into one single class or you chain the classes (ExtensionClassA extends Core Class and ExtensionClassB extends ExtensionA). Somehow this is a big lack in Magento extension development in my opinion. Please correct me if I’m missing something.