The Magento Community Edition 1.8 was announced during the Imagine Conference in Las Vegas in April 2013. An alpha version was released and stay as it is until now. Finally, the release 1.8 has been published today. We can understand the situation when we are aware that the Magento Team concentrates itself on the Magento 2 version which is a big release and hopefully would come in 2014.
Although the community engaged its effort to fix a big amount of bugs with the collaboration of the Magento Team during the Hackathon in Zürich and Bugathon Los Angeles in March 2013, most of those fixes will be published in the version 1.8.1 later in Q4. So I may advise you to wait if you are not in hurry for your project to get this short coming soon release.
However for those who are not patient or would like to benefit quickly of the new features and enhancements, find here the list of the improvements:
Definitely a subject which should enjoy enterprise having VAT. Several problems have been fixed: rounding errors calculation confusing buyers and merchants and discount calculation. You will find more information how to handle the configuration of your shop depending in which country you are, see the Magento Knowledge Base for more explanation.
I’d like to take the opportunity to inform you of a module which can help you to setup the tax calculation rules in a fast way when you are installing Magento. It is very helpful for European Countries, Russia and Switzerland. The module has been developed by the Firegento Association (a developer community based in Germany) and available for free on Github. You may find also an article explaining more in details the module.
- of the speed of page loading during checkout process.
- of the cache for single server, minimising the refreshment of caches when product is updated
- of the backend when a store has huge amount of products or tax codes
- Add Redis cache module from Colin Mollenhour
350 functional improvements that boost product quality in key areas, including the web store, shopping cart, admin order creation, import and export functionality, web API components, and payment methods.
- Session fixation vulnerability
- Oauth attacks
- Remote code execution
- Block attackers to get access to billing information
- Block web browsers to save user and password from backend
- Additional CSRF protection
- Session ID change after registration to prevent man in the middle
- Cryptographic method to store password has been improved
Download the new release in the download section of Magento Website
Sources: Moses from Magento Inc. / 1.8 Release notes / Magento Blog
You always hear about this event. Since one month, everybody is tweeting, facebooking, googling plusing, blogging, chatting but for what the hell reasons should you come! They pushed you against the wall and told you: “You MUST go in Zürich on 8-10th March 2013! That’s the Magento Developer event of the year in Switzerland.”. Sad isn’t it! Find here some arguments to NOT come:
- Magento, what is it? I’ve never heard about that. I’m still using the dark side of the ecommerce solution, osCommerce, the best ever Open Source solution!
- I’m the best coder of the world. I need no friend, no tips, no network, no fun. I don’t want to share my knowledge with no one because I prefer to work alone, I’m more efficient. PHP is the bottleneck for Magento, I don’t want to improve it.
- I prefer to do a world tour. It’s more interesting. Where the hell is Matt? http://www.wherethehellismatt.com
- Achmed – The Dead Terrorist (http://www.youtube.com/watch?v=1uwOL4rB-go) didn’t allow me to go. He said if I go: “I kill you!”
- The last time I came, it was in Berlin, a Dutch opened all people’s beers with my shiny MacBook Air. It doesn’t work anymore. I’m shocked for all of my life.
- I’m not the sponsor. I’m sad and sulking!
- I still didn’t digest the sweets of the Munich Hackathon in last october. I cannot move anymore, sorry!
If unfortunately, after all these reasons, you still didn’t find yours. It seems you have no reason to not coming.
Visit the event website to enjoy with us and get some surprises in Zürich on 8-10 March 2013: http://www.magento-hackathon.ch
PS: if you have better, funnier or others arguments, please comment them
The Magento Hackathon is a Magento Developer Event which was located this last week end (26-28 October 2012), in Munich. It’s a good moment to share knowledge about the development process or some tips to improve his skills with Magento. This is also an opportunity to create some challenge or emulation with different projects and make some good friends
In Munich, we were more than 24 developers from different companies based in Germany and Switzerland and did during this event some projects that you can find on Magento Hackathon Github like:
- Product sort order in categories via Drag’n drop: A good idea module, to help you to sort your products into your categories thanks to Drag’n drop action which can be used from the backend or the frontend of your online shop.
- Login Provider Framework: A framework to provide other authentication methods to get access to the backend. It could be for example, to implement an authentication method with a LDAP server.
- Honey Spam: A Magento module to block automatic process which try to use the forms of your shop to hack it for example.
- Social Commerce: Do you want to make your shop more social? Thanks to this module some events which happens on your shop, can be published on social media automatically. While I’m writing these lines, a newly created and enabled product saved from the backend can be published automatically to twitter with its name and a shorten frontend link.
- Magento Composer Installer: The purpose of this project is to enable composer to parse and execute modman files. Magento modules are installable as long as they have a valid modman file.
I discovered few weeks ago an interesting tool to develop Magento modules with Eclipse PDT or Zend Studio: the Magento Eclpise plugin. I use it personnaly with Zend Studio 8 and it works pretty well, so we are going to see the different feature you can get from this module. With this module you can:
- Find two wizards to help you to extend or create Magento modules
- Code completion for core class or method even when you use Mage::getModel() or Mage::getSingleton() and so on.
It is with a great pleasure that the Magento Core Team published a public version of the development Magento 2 and information about it. This new version is still in development and will be available when stability, code quality, features and documentation will be finished. It is expected in one year (end 2012). Lots of lack blamed for version < Magento 2 are going to be history (we hope).
The target of this new version is to provide a better documentation (a complete wiki for store owner, developer, system administrator or designer target public is available and still in progress), an improvement of the performance / security / scalability (EAV still exists), PHPUnit Tests and Automatic Static Code Analysis Tests (including PHP Detector Copy/Paste, PHP Code Sniffer, PHP Mess Detector), easier and better support of multilanguage, etc.
But don’t worry dear Magento 1.x developers, not everything has been changed. At the program, refactoring of some classes, naming convention and templating and skin folders restructuration have been done at the moment. We will see some changes in this first article and how to handle it to upgrade your extensions. Remember, it’s still in development, so the information are there just to keep you informed. I will try to prvovide you up to date information until the official release on this website.
If you are a third party developer, you should follow the recommandations and best practises based on Zend Framework Best Practises and Magento Best Practises (Licenses and category/package/author tags in the docblock of class’ header) to migrate your extensions.
You will find all necessary links about the Magento 2 development version (documentation, svn, tools) at the bottom of this article. But first, I did for you, a resume of the significant changes done between Magento 1.x and 2.x based on the documenation available in the Magento 2 Wiki.