As I had noted earlier this week, I have not had a lot of Magento development time lately, so today I thought I’d spend a bit of time setting up a Magento 1.5 development environment on my Mac. This post will take you through the steps to set up Magento development with Eclipse for editing/debugging and SVN for version control, with deployment being managed by Modman. This relates to the project structure I described in my presentation at Magento Imagine, with the exception that I won’t go into detail about setting up a separate extensions repository, as that is probably more relevant to developers who build and release extensions than developers working on a single Magento project.
#In your ~/Downloads directory or some where suitablewget http://www.magentocommerce.com/downloads/assets/126.96.36.199/magento-188.8.131.52.tar.gz
tar xzf magento-184.108.40.206.tar.gz
# I keep all of my Magento development versions in a web folder within ~/Documentsmv magento ~/Documents/web/magento/220.127.116.11
#In your ~/Downloads directory or some where suitable
tar xzf magento-18.104.22.168.tar.gz
# I keep all of my Magento development versions in a web folder within ~/Documents
mv magento ~/Documents/web/magento/22.214.171.124
2010 is now well and truly behind me and I am sitting inside on a sunny day (sunburnt) reflecting on the year that was. It’s been a busy year. I thought, more so for my own sake than yours, that I would jot down a few notes to wrap things up.
Firstly my blog, Aschroder.com. 2010 has been good to me in several respects. From a traffic point of view my final tally (according to Google Analytics at least) clocked in at a touch over 100 thousand visitors and over 200 RSS subscribers, I feel like this is a recognition of the quality of my continued articles on Magento development. Continue reading 2010 ☑ Bring on 2011
Wow, where did November go? It’s been over a month since my last post and I thought I should probably just drop a quick note here to let you know what’s been going on, and what’s coming up. There’s no Magento tips or advice here though I’m afraid – but there is a little sneak peek at a project I have been tinkering around with – I’d really love some feedback on it.
The first 5 Magento Installations I do will be free! Whats the catch? You have to provide me a review of the work I do and my professional service in general that I can put on my blog for others to see. Simple eh?
I’ve decided to start offering Professional Magento Installations as a service, there is high demand for a well installed Magento. All too many people with not quite enough knowledge or skills are having a go at it then ending up with failed installations. I have helped a number of people on the Magento forums who for a small fee could have saved themselves hours of headaches and had the work done quickly by a professional.
My standard price will be $99, I see that Magento themselves charge $149 – so naturally I wanted to make my Magento Installation cheaper without cutting back on quality or timeliness. I will often be able to install same day, and usually install within 2 days.
Because I haven’t offered any professional service on this blog before I thought I’d offer to do the first 5 Magento Installations free of charge to get some references from happy customers! So if you want your Magento installed for you by an expert, check out my professional services page. Be in quick, I’m sure this won’t last.
There is a lot going on when Magento actually sends a cart to Google Checkout, even more so if you are using Merchant calculated shipping. As a result lots of things can go wrong, with the merchant calculated shipping callback or with the actual server to server posting of the cart contents.
To help you with diagnosing problems I thought I’d shared my top 3 methods for finding out what is going wrong when Magento and Google Checkout are not communicating properly.
1) The Intergration Console
The first and most obvious place to try is the Google Checkout Intergration Console. As you can see in the screenshot below the console is hidden away in the Tools tab of the main seller dashboard. You’ll find it at the bottom of the left menu.
If the Google callbacks have failed or incorrect XML has been sent to Google you will find a report of the errors here. It is a good idea to keep an eye on the timestamps as you do not want to wind up chasing an old problem. It’s also good to periodically check this console while in production, just in case something starts to go wrong. I found when I upgraded to the latest Magento that the HTTPS callback was failing, but I hadn’t found it during development because I do not use SSL in development environments.