Let’s start at the beginning, at installation.  Your web server likely has capable hardware, so you need to be sure that your software configuration meets requirements.  Luckily the host I’m on was set up just fine the way it was.  Obviously you need to download the software – I chose to download the Full Release (version 1.1.8 at the time).  The zipped package contains 6k+ files so you may want to look into an “unzip on the server” solution or you’ll have to wait a long time like I did.  If you decide to wait, take the time to read through the User Guide and the Designer Guide.

Setting up Magento

Once you have the files uploaded, CHMOD the directory (where you dropped those files) to 777.  Then navigate to the installer script – http://www.yourdomain.com/your-magento-folder/.  The script is very simple, and the most important part of it is inputting database connection information.  Proceed to create an admin account and log in to the administration panel.

I easily set up a “website”, “store”, and “store view”.  For my purposes, just one of each was necessary so I named them “clientname_website”, “clientname_store”, and “clientname_storeview”.  I haven’t set up any roles other than Administrators yet, since for now it’s just myself and another developer .

My two main tasks to work on:

1. Style the front-end to look like our client’s existing storefront
2. Import the client’s existing product catalog data (including manufacturer and category data)

I decided to work on styling the front-end first, since it seemed to be the more difficult task.  I imagined thousands of CSS declarations I’d have to modify, not to mention figuring out the XML-based layout system.  As for the catalog import, I imagined it would simply be the mapping of data fields into the Magento model.  I prefer to tackle more difficult tasks first, for peace-of-mind reasons.

Theming Magento

As I predicted, getting Magento to look the way I needed proved to be a very difficult task.  I was hoping for a more Wordpress style header/content/left+right/footer type of deal, but what I saw was something much more complicated.  To make the simplest of changes took many hours, with my development process being something like:

1. Figure out which file(s) contains the code (HTML, XML)  I need to edit.
2. Verify I have the right files.  Make a small test change and see if output is affected.
3. Remind self of what “block, layout, and template” mean.
4. ( trial/error, server timeout ) x 10
5. Break.  Resume. Now, what was I doing? /MyCompany/MyCompany/?  Oh right.
6. Search Google on how to solve the problem.  Search is fruitless.  Try Experts-Exchange.
7. ( trial/error, server timeout ) x 10
8. Almost there.
9. Major revelation! Break.

All in all, theming was/is very complicated.  It’s hard to determine what references what, and how to go about making changes to get the desired effect.  My impression is that the Magento team would have us use their system in one way, and only that way.  The whole hierarchical system seems like a good idea, but in practice it’s cumbersome and difficult to master.

Importing the Product Catalog

After walking barefoot over hot coals, or theming Magento, I was really hoping that importing the product catalog would be a no-brainer – just map fields in my existing database to fields in the Magento database.  I couldn’t have been more wrong.  Magento’s database model is an instance of the entity-attribute-value model (EAV).  The difference between EAV and conventional modeling is that table records don’t represent an instance of a data object.  Instead, the data object’s values are spread out over multiple tables, making manipulating the delicate database directly incredibly complex.

The route I decided to take, as recommended on several sites, was to:

1. Create a single category (under “root category” or “Default Category” of course)
2. Create and assign a single product to that category.
3. Run the “Export All Products” profile to generate a CSV file
4. Export existing data to CSV according to the exported CSV’s column format
5. Upload the new CSV using the “Import All Products” profile.

When exporting existing data to the Magento format, be sure to use the category ID values for category instead of the category names.  You can find out a category’s ID by navigating to its “edit category” page and looking at the URL.  The ID is in the URL.

When running the “Import All Products” profile, you might have to limit the number of records that you import at a time.  If that doesn’t work, (as in my case) try reducing the number of rows that are in the CSV file.  You would have to upload many many CSV files and run the profile over and over again for those files.  I don’t understand why adding records to just a few tables should consume a large share of server resources.  Import crashes for me a lot, which isn’t good because I’m unclear of whether all products have been imported or not.

Speed and Performance

I’ve decided to dedicate a section to speed and performance, because Magento’s slowness was a huge distraction during the development process.  It would be nice if at the very least that the system didn’t crash every 1/5 page loads.  It would also be nice if I could see the results of a few CSS declarations quickly.  There seems to be a LOT of overhead in Magento, I could go on forever about it.

Based on what I’ve read, you should go with a dedicated or a virtual-private-server (VPS) if you choose to run Magento.  A lot of developers working on a shared hosting solution seem to have huge speed issues.  Trust me, save yourself a lot of headaches and upgrade your hosting.

Now I’ve only just started to become familiar with the platform.  I should also mention that I have no experience working with other eCommerce platforms like OSCommerce or anything, but the talk-of-the-town is that Magento blows everything else out of the water.  More importantly, based on what I’ve read in their comprehensive User Guide, the software can handle (1) everything our client needs, (2) everything they’ve requested, and (3) everything our client hasn’t even thought of yet.

Some of the cool stuff includes:

• Automatic product comparisons page (based on product attributes that you define)
• “Layered navigation” – when browsing through a category of products, the layered navigation offers nifty drill-down filters so shoppers can easily find products that are within their budget/needs/tastes.
• Related products, upselling, and cross-sellling (important to know the distinction between the three)
• URL rewrites (very very very important for SEO)
• Support for UPS, UPS XML, FedEx, USPS, and DHL
• Multiple images per product and slick zoom-in capability

For the full feature list, go here.

Expect more posts regarding Magento to come as I journey through deployment.  This post was just kind of like a trailer.

Say for example that you added a blue polka dot shirt of size “large” to your shopping cart.  Then, after continued browsing through the online catalog, you decide that you want a “small” blue polka dot shirt.  The problem was that after adding this shirt of size “small”, your shopping cart would contain two (correct) shirts of size small (wrong).  Obviously, you should have a small shirt and a large shirt.

This cart was indexing items by product ID, and not accommodating for multiple sizes.

Our solution for them was a cart structured to be unique on product ID and size.  Short, Sweet, and Simple.  S, S, & S the solution may have been, it still took a long time to develop because of the fact that there was no sandbox (development) environment and the system was in the process of taking orders as we were developing.  Some would say that’s a huge no-no, but the issue had to be addressed.  With the utmost planning and preparation, the coding was done and no order processes were interfered with.

On a humorous note, I charged my credit card a $xxx.xx item (yes, in the hundreds of dollars) to test the new shopping cart’s functionality.  When doing e-commerce development, make sure to obtain test credit card numbers.  Most online payment processors should have these readily available for developers.