Hi
friends now I am going
to show you a next part of this article. This is the 3rd
part of the Centre Point of Magento development guide line.
Pre-Launch Checklist.
Error
Page Design- When
there is an error on the site, or the maintenance.flag file is set, a
different theme is used to display the error message. Without
changing this your customers will see the Magento logo and default
theme. To adapt this page to your own template you will need to
modify the files located in the errors directory. You will not want
the error page to print a stack trace. To stop this happening open
errors/local.xml (assuming you are working from the sample), and then
change the action from “print” to “email”. You can then set
an email address for it to send the error report to.
Index
Management- Make sure
you have re-indexed after making any catalogue changes.
Caching-
Caching, although on by default would have been the first thing you
disabled when beginning development. So, remember to re-enable and
refresh it when you are ready to go.
System
Compilation- Another
essential way to keep the loading time of your Magento
website down is to
compile it. Page loading times are said to have a performance
increase of up to 50%, this is definitely not something you want to
miss out on. You will be able to find settings for this in System ?
Tools ? Compilation.
Google
Analytics- Your client
is going to want to see how traffic fairs from day one. Magento does
all the hard word for you (as per usual). Set up your Google
Analytics account and then put your account number in System ?
Configuration ? Sales ? Google API ? Google Analytics.
Google
Base- Another
essential Google service that is already integrated into Magento.
There are a few steps to do this, but Inchoo have written a nice
article on it.
Google
Sitemap- No excuses
for this one, my Grandmother could do it and she still thinks the
postman delivers your emails (true story). Simply “Create Sitemap”
in Catalog ? Google
Sitemap. Then, if
you are using Google Webmaster Tools you can also point Google
towards it. There are further settings for this, e.g. to
automatically regenerate the sitemap, and they can be found in
System? Configuration? Catalog? Google Sitemap
Newsletter
Subscriptions- Test
that customers can sign up and unsubscribe and that newsletters can
be sent out. You don’t want to be testing this process once you
have real customers in the system.
Shipping
Methods- If you are
using a fixed product or cart fee then make sure it is set. If you
are going down the cart weight route then you should confirm that the
logic is correct and that all products have weights attached to them
Payment
Gateways- Double check
that your payment gateway is ready to jump from testing to live.
,SSL
Certificate- This is
one that is often “left on the shopping list”. Many payment
gateways will not allow you to take the system live until you have
one.
Now
next part will be release earlier next day.
Best
Service for Quick Search:
0 comments:
Post a Comment