PART- 2: Centre Point of Magento development guide line. Pre-Launch Checklist

zipper johnAugust 21, 20125min410

Invoice and Packing Slip Design- Here, you will need to upload the logo that is to be used for invoices. Alternatively you can place logo_email.gif in your images folder in the skin directory. There are a few other settings that you should pay attention to.

Tax Settings- These should be all set up already, but it does not hurt to see if anything in the configuration was overlooked. These can be found in System ? Configuration? Sales ? Tax and also Sales? Tax.

Shipping Origin- Directly related to the tax settings, the shipping origin needs to be set to the correct country in order to use the appropriate tax rates.

404 Page- Not to be pushed to the side of a development of any site. Remember to test it. Customers that find it will already be disappointed; do not let you down by leaving the default Magento blocks still there. So, please remember to “Kill the dog”. Also, in the default 404 page which can be found in CMS? Pages, there is reference to “Magento Store development”. Ditch it.

Clear Test Data- Remove all products, orders and customers that were created during development

Product Inventory- When importing products the first time around, it is likely that you did not bother with managing stock. It’s an unnecessary hassle when developing. Before you go live, check with your client what configuration he would like set up. You may have to do another product import with stock levels before going live.

Flush JavaScript to 1 file- One essential measure to reduce loading time is by limiting the number of HTTP requests that are made each time. Magento stores can be heavy in JavaScript, but you can keep the requests down by flushing all of your JavaScript files into one: System ? Configuration ? Developer ? JavaScript Settings.

You may have used the odd bit of inline JavaScript when developing. These will need to be moved in to their own file to avoid any unnecessary slowing of page load times.

CSS Settings- Use a CSS compressor. Keep two versions of the css, one in readable form e.g. styles.css.orig and then have a minified version styles.css. This is the same idea as the JavaScript flushing, but be careful, it is currently an experimental feature.

Best to enable on the staging server before taking it live to see if it has any side effects. It can be found in System ? Configuration? Developer ? CSS Settings. A useful extension available on Magento Connect is Fooman Speedster. It combines, minifies and compresses all JavaScript and CSS.

Maintenance.flag- Touch this file in the root of the Magento installation and it will display a holding page while you are going live. Especially useful if you are using something slow like FTP. Move this file across first and then queue the rest of Magento to transfer.

Now next part will be release earlier next day.

For more helps and guide line Hire Magento Developer, Magento Development, Magento Developer