Here’s the link: http://bit.ly/9BHlVU

Anyway, the second part is actually quite easy. It is pretty much about setting up your empty MySQL database for use with Magento. Here are the steps:

1. Install MySQL Server (obviously) – this process should be a no brainer process. Just download the installation package and run it. You need to configure the MySQL to support both InnoDB and ISAM for Magento to work. Follow the setup wizard and you will be okay
2. You may want to download MySQL GUI Tool as well. Or if you are looking for a good GUI, I suggest you try NaviCat. It is probably the closest application that give you something similar to what we see on our Microsoft SQL Management Studio tool
3. Create new database (or schema). Name whatever you want. I usually create user along with that and assign the user to the database and give all access
4. That’s it. You are ready to install Magento

So now the rest should be pretty straight forward. Once you put the Magento code on the Apache, call out the main URL (don’t use localhost or IP, if you don’t have domain, create dummy one through host file). You will see the Magento setup wizard. Follow the setup steps and you will be good to go.

Cheers.

Here are the cheat sheet to retrieve those attributes (EAV).

1. Query to find different type of entity available

SELECT *
FROM eav_entity_type

2. Then use that entity type above to find EAV available for that entity using this query:

SELECT et.*,att.attribute_code,g.attribute_group_name,eset.attribute_set_name
FROM eav_entity_attribute et
INNER JOIN eav_attribute att ON att.attribute_id=et.attribute_id
INNER JOIN eav_attribute_group g ON g.attribute_group_id=et.attribute_group_id
INNER JOIN eav_entity_type etype ON etype.entity_type_id=et.entity_type_id
INNER JOIN eav_attribute_set eset ON eset.entity_type_id =
etype.entity_type_id AND eset.attribute_set_id=et.attribute_set_id
WHERE etype.entity_type_code=’{replace with entity type}’;

Here’s some of the links first:

How OO Almost Destroyed My Business -

http://www.advantexllc.com/blog/post.cfm/how-oo-almost-destroyed-my-business

Response from Steve Bryant:

http://www.bryantwebconsulting.com/blog/index.cfm/2009/5/26/The-Trouble-with-OO

And of course the one where I find the whole thread originally – Sean Corfield’s Blog:

http://corfield.org/blog/index.cfm/do/blog.entry/entry/To_OO_or_not_to_OO_What_is_the_question

The one that I agree with Sean is “: there is no One True Way. What works for me might not work for you and even I will solve the same problem different ways at different times in different circumstances. ” That is so true. My philosoph

First make sure you only use PHP 5.2+ but not version 5.3. You can use the latest MySQL or version 5 and above. Now once you have both PHP and MySQL downloaded, let’s start by configuring IIS to work with PHP first.

On part 1 of this blog, I will start with configuring PHP with IIS7 using FastCGI. If you have Windows 2008 or Windows 7, then you will be using the new IIS version 7. I typically choose the manual PHP installation process. Magento Commerce supports FastCGI, therefore, we can setup our IIS to use FastCGI. IIS 7.0 comes with FastCGI as an option when you install it. Here’s the steps:

1. Make sure FastCGI is installed with your IIS 7 (go to control panel – program and features – Turn Windows feature on or off – under Internet Information Services, make sure CGI is checked (inside world wide web services – application development feature)

2. Unzip the PHP into a directory.

3. Next we are going to install PHP using FastCGI. Open IIS manager. In the site that you want the PHP engine to run, click on the “Handler Mappings” and add click on “add module mapping”. Enter the following:

• Request Path: *.php
• Module: FastCGIModule
• Executable: {Your PHP directory, i.e. c:\PHP}\php-cgi.exe
• Name: PHP via FastCGI

It will prompt whether you want to create a FastCGI application for this application. Just choose “yes”.

4. On your PHP directory, make sure PHP.ini is there. You can copy from “php.ini-recommended” and rename it to “php.ini” to start with. Inside PHP.ini, these are the settings that need to be set right:

* Set fastcgi.impersonate = 1. FastCGI under IIS supports the ability to impersonate security tokens of the calling client. This allows IIS to define the security context that the request runs under.
* Set cgi.fix_pathinfo=1. cgi.fix_pathinfo provides *real* PATH_INFO/PATH_TRANSLATED support for CGI. PHP’s previous behavior was to set PATH_TRANSLATED to SCRIPT_FILENAME, and to not care what PATH_INFO is. For more information on PATH_INFO, see the cgi specs. Setting this to 1 will cause PHP CGI to fix its paths to conform to the spec
* Set cgi.force_redirect = 0.
* Set extension_dir to point to a location where PHP extensions reside. Typically, for PHP 5.2.X that would be set as extension_dir = “./ext”
* Enable the required PHP extension by un-commenting corresponding lines, for example:
extension=php_mssql.dll
extension=php_mysql.dll

5. Now we are ready to test the PHP.

To test your PHP installation, on your webroot, create a test php file. You can named it “phpinfo.php”. Inside simply type in the following code:
<$php phpinfo();

6. Open your browser and go to that page that you just created. If everything install correctly, then you should see all the php settings of your PHP installation.

That's it. On the next part, I will cover installing MySQL and preparing the empty database for Magento.

Here are some of the key highlights of Ashland:

1. Master Pages

Ashland finally supports the .NET master page and theme approach for website skinning. Skin base has been deprecated, but the XML Package is still fully supported. This change allows any .NET developer to easily skin the eCommerce site without having to know XSLT language, like in previous versions of AspDotNetStorefront.
This move not only leverages master page and themes better, but it also allows for easier integration with AJAX toolkit and the creation of custom user controls. This makes the development of the site much more streamlined and faster.

2. Enterprise Modules

This is a certainly a big, significant move for AspDotNetStorefront. With Ashland, they’ve established what has been called ERP Synchronization Specification or ERPS, which combines the use of WSI (the Web Service API they’ve made available since version 7.1) and the “in Process” add-in model. The Add-In model leverages standardized contracts that allow developers to extend and develop “add-ins” to enhance AspDotNetStorefront’s core functionalities.
Here’s a list of available contracts (which can be extended):

• Payment gateway
• Shipping methods and rates calculation
• Order fulfillment
• Tax Rates
• Inventory
• Order Options
• XSLT Extension

All of these create new possibilities to extend AspDotNetStorefront without touching the core source code of the software. These also allow developer communities to share and/or develop custom add-ins that can be reused by other developers.

3. Support for Multi Stores

With Ashland, you can now create and manage multiple stores within the AspDotNetStorefront installation. Each store can have its own look and feel (skin), product subsets (through product mapping), shipping method, and even payment method. However, all stores will share the same product and variants database, order database and admin interface.
This feature is perfectly suited for companies that want to “launch” micro sites or subsidiary sites where all order processing needs to funnel through one system. However, this is not to be confused with a “mall” solution, where a company hosts multiple eCommerce sites under a single installation.

4. Other notable enhancements

• Configurable URL rewrites
• User-configurable error handling
• Revised shopping cart logic
• Versioned topic
• Page-level role based security

5. PA-DSS certification

The platform’s PCI compliance will be replaced with a new certification called PA-DSS. AspDotNetStorefront takes payment security standards very seriously, and as such, Ashland will undergo the full PA-DSS certification process as well as an independent security review. This will guarantee that all future AspDotNetStorefront-built eCommerce sites will meet the industry standard for payment security regulation.

The scheduled release date of Ashland is August 31st, 2009. The pricing should not be too different from the current version except for the multi-stores functionality, which they have yet to determine the licensing model for it.

But that’s not all for AspDotNetStorefront. Ashland may be the next version, but they are already started working on the next enhancement list which will be included on the next version of AspDotNetStorefront (code name “Vegas”). Here are some of the key features that are planned to be included in Vegas:

• Multi Payment support
• RMA generation
• Invoicing capabilities
• Order Archival
• Enhanced back order support
• Line Item order transaction
• Iterative (faceted) navigation and search capabilities
• Advanced phone order
• VAT inclusive pricing
• User-defined entities
• Fully localized admin site
• Integrated blog engine
• Mobile capabilities
• Admin redesign

The expected release date for Vegas is end of December 2009.

Taking a look at both Ashland and Vegas, we are very excited to the platform maturing and growing at the same time. The feature sets are fully updated and reflect the ever-changing needs of eCommerce websites and online stores. Kudos to the development team of AspDotNetStorefront! We are looking forward to working with both Ashland and Vegas.

Here are some of the things that I predict will be BIG in the next 6-12 months:

1. Facebook Connect
URL: http://developers.facebook.com/connect.php

More and more sites are leveraging this to allow their visitors to connect to their Facebook account and reach out to their Facebook friends. Facebook connect allows site to “embed” facebook functionalities such as share to friends, comments, post to wall directly from the site (without going to Facebook sites). Facebook opens up more and more functionalities under this wing. Rather than building your own social network, why not just integrate with Facebbok?

2. Open ID
URL: http://openid.net/

This is another big undertaken that has been slowly adopted by all major social media sites including Facebook. This allow users to use one login to access all their favorite Web 2.0 sites. This also opens up the door of communication between one site to another. Big retailer Sears just recently announced of supporting Open ID on their community sites: MySears and MyKmart.com.

3. HTML 5.0
URL: http://www.w3schools.com/tags/html5.asp

The new spec of HTML is out and adding a lot of Web 2.0 specific functionalities to the core HTML. Now you embed video directly to HTML without the need of external player. Another big thing in HTML 5.0 is to allow having local storage of data (this will replace what we do with cookies todays) If you haven’t checked the spec out, make sure you start looking to it. Firefox 3.5, Opera and Safari 4 have already support this.

4. Google Wave!!!
URL: http://wave.google.com/

If you have not watched their video presentation of Google Wave, go search at Google and watch it. It is too cool to miss out. From the same brothers who create the awesome Google Maps, they are trying to revolutionize the way people communicate to each other. This is going to change everything we know about online communication and colaboration. Moreover, they meant for both personal and corporate world! No more Exchange Server, Share Point and Facebook?

Alright, see you all on my next report.

1) Era of Social Relationships: People connect to others and share
2) Era of Social Functionality: Social networks become like operating system
3) Era of Social Colonization: Every experience can now be social
4) Era of Social Context: Personalized and accurate content
5) Era of Social Commerce: Communities define future products and services

I found his opinions are so true and we are definitely entering the era #3 and #4. With the release of Google Wave later this year and the wide support of OpenID everywhere, the maturity of these eras are right in the corner. Even Sears announced that they will be the first commerce site to support OpenID initiative. I won’t be surprise if one day Microsoft will announce that you can now login to your Windows with OpenID (Windows 8 probably?)

Here’s the original URL where I get the discussions and blogs:

http://tinyurl.com/prwqty

To me, I came from system analyst background and not computer science, then I grow as database programmer and then move to web developer with ColdFusion. Then I moved camp to pre-dominantly .NETdevelopers company and year later moved out from developers role and back to business analyst and project manager. I don’t have strong OO background and I am rarely code with OO in mind. But I know enough to understand all the benefits and know how big applications can benefit from good OO architecture.

However, this is what my observation. We (I refer to developers and engineers) have the tendency to only use one tool to accomplish all things. We believe in one thing and we love to make stuff more complicated that it should be. I guess that is in the blood of humanity. We excel in knowledge, creative brain, and create these all wonderful stuffs that supposed to make our life easier but they end up make our life more miserable (that is another subject that I won’t be sharing in this blog, but may be my other blog ).

When ColdFusion is out, I believe, it was designed to give us an alternative way to create dynamic web in the shortest amount possible. You need email functionality, done, it is there. You need to query a database, done it is there. Even on the newer version, the same trends are true. You need a web service, 3 lines of code, done. ColdFusion allows us to consume .NET code, Java code and that what makes ColdFusion unique. I think there will always be two type of application developers. One that loves creating all the complex mechanism at the background, and the other one just simply to get the business done quick and accurate. My personal thought, ColdFusion will always be for the second person. If you need strong OO support, I think you should just write Java code and compile and let us INVOKE it within ColdFusion.

In this hetero languages technology world, I believe on hetero architecture too. Open API, write small functionality codes and easy inter-changeable code. Are you going to write OO oriented FBML? (facebook markup language) There is no such thing But you create sophisticated Java module that will interact with FBML. The one thing that I learned from day one that I think is very important is this 4 acronyms: -KISS – keep it simple stupid

That’s my 2 cents.

“The campaign’s plot is simple. Weird, but simple. Consumers go to a Papa John site and grab an icon of the “1972 Z28 Camaro that founder John Schnatter sold 25 years ago to open his first restaurant,” the chain said. As of Monday (June 1), consumers can use webcams to capture the image from a pizza box. Once selected, the consumer can then drive along a virtual road, being shown virtual billboards, which are discount coupons.” — StorefrontBacktalk

I think this is more a consumer retention strategy toward their younger consumers and hope that they will find this new coupon hunting interaction fun.

Read here for the full post: http://tinyurl.com/py46wx