Please Note: This article was written using Magento Version 1.4.1.1. This article may not work on older versions.
Basic Installation:

• Download Magento from the website (http://www.magentocommerce.com/download).
• Extract Magento using the appropriate utility.
• Proceed to install using the Installation GUI.

After going through the installation screens you should have a fully functional Magento e commerce site.  We wanted a Multi-Website Installation so we have a few more things to cover.

Multi-Website Install: Additional Tasks:

• For each website you plan on having you need to create it in Magento.
• Log In to the admin panel. Go To System > Manage Stores. This brings you to the Manage Stores Page. Here you need to add a new Website, Store, and Store View. Be sure to correctly relate each Website/Store/Store View. We will use the information entered here in the next step.
• Now you need to set things up with the web server to notify Magento what site needs to be rendered. This is a decent tutorial on how to configure things Tutorial. I ended up having to add the settings in my .htaccess file.
• Now you can create a root category for each website. You will need to set each root category to each websites Store. Do this in System > Manage Stores.
• Now when you are doing things in the admin, remember, on most configuration/edit screens , there is a Scope switcher (switches between Sites). This will affect how the config setting are applied to the sites.

Delete the following file in the Zend Studio workspace:

Zend/workspaces/<your workspace name>/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.dltk.ui.prefs

Here is how I decided to go about it.

• Backup the database!!
• Clear all cache and disable caching
• Move code into a SVN Branch (assuming you use source controll, if you don’t you should!)
• Remove Old Core Magento Code (just leave community and local modules, keep my theme folder)
• Download Full Release from Magento’s Website(don’t use the downloader, use the full release!)
• Extract the New Release into the SVN Branch that was created earlier
• If your template was a sub-template of anther theme then you need to merge them together to use in 1.4. This is due to the fact that 1.4 changed a bunch of classes and layouts. Or you could start from a fresh theme and re code it.
• Change the theme to a default theme until you are sure that the update went ok.

Errors and Bugs I came across:

• When Trying to run indexing I got the following error, “can’t initialize indexer process”. This was because I was missing some database tables that failed to install during the upgrade. I installed and ran the database repair tool.
• Had to disable WYSIWYG so that page templates did not get messed up.
• The file “catalog/product/list/toolbar.phtml” changed quite a bit, so if you modified this file grab the new one then start from there. Also the file “page/html/pager.phtml” needs to be update the the 1.4 version if you modified this file.
• When editing or adding products the Category Tree was only showing the Default or Root Category.
  To Fix this I just created a new subcategory of the root catalog and move all the categories into this new category then move them back to there original position. This must rebuild what ever was messed up in the database.

My first issue was, How do I get the new node id that was created by drupal_execute(). Well It was easier than I thought. I did a little goggling and found people saying that you should use db_last_id(), well that did not work for me. Instead I used the “$form_state” variable that I passed into the drupal_execute function. I noticed that after running drupal_execute() I could use $form_state['nid'] to retrieve the nodes id. Wow wasn’t that easy.

The nodes I was creating were using cck fields. I noticed that only the first node’s cck fields were created correctly. All subsequent nodes were created with cck fields containing just 1 character(I believe this only happened on select fields). To fix this issue I had to use the node id that I retireved and set the cck fields again. Then do a node_save(). Now all my fields are correct and I can go Fishing.:)

I had a Block class called SideNavigation.php. I called it using a layout file. It was suppose to provide custom CMS functionality with a side navigation menue.

Below is the code from the layout file that did not work.

<?xml version="1.0"?>
     <layout version="0.1.0">
          <cms_page>
               <reference name="left">
                    <block type="advancedcms/sidenavigation" name="advancedcms.sidenav" />
               </reference>
          </cms_page>
     </layout>

The reason this did not work is because unix machines are case sensitive where as Windows is not case sensitive. Magento turns sidenavigation in the above code into Sidenavigation. It allways capitalizes the first letter. So windows would match Sidenavigation to SideNavigation because it is case insensitive. unix/linux machines would not match Sidenavigation to SideNavigation. So I had to change my code to the following to work.

<?xml version="1.0"?>
     <layout version="0.1.0">
          <cms_page>
               <reference name="left">
                    <block type="advancedcms/sideNavigation" name="advancedcms.sidenav" />
               </reference>
          </cms_page>
     </layout>

Now magento turns it into SideNavigation and the layout file correctly points to the SideNavigation.php file.

Hope this helps anyone with a simmilar problem.

Just a closing thought: Wouldn’t it be nice to be able to make windows case sensitive, so you don’t have to do trouble shooting like this.