<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
>
<channel>
	<title><![CDATA[Vinagento]]></title>
	<atom:link href="http://www.vinagento.com/blog/feed" rel="self" type="application/rss+xml" />
	<link><![CDATA[http://www.vinagento.com/blog/]]></link>
	<description><![CDATA[Vinagento]]></description>
	<lastBuildDate>Wed, 22 Feb 2012 21:12:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator><![CDATA[http://fishpig.co.uk/wordpress-integration/]]></generator>
			<item>
		<title><![CDATA[Magento speed up - Howto?]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-tutorial/how-to-speed-up-magento-site]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-tutorial/how-to-speed-up-magento-site#respond]]></comments>
		<pubDate>Wed, 25 Jan 2012 09:41:40 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=441]]></guid>
			<description><![CDATA[As you probably know by now, Google is Using site speed in web search ranking. And I couldn’t agree more: speed is important for your site, and not only for Google but mainly for the User Experience (UX) on your site. Research from Google and Microsoft shows that slower websites convert less and that the effect of a slow website is lasting.
Sidenote: As a psychologist this might be a form of Déformation professionnelle, but I kinda hate it when people always talk about optimizing for search engines/ Google. Don’t optimize for Google, keep in mind that you optimize for your...]]></description>
			</item>
		<item>
		<title><![CDATA[Identifying Magento Performance Problems with the Magento Profiler]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-tutorial/identifying-magento-performance-problems-with-the-magento-profiler]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-tutorial/identifying-magento-performance-problems-with-the-magento-profiler#respond]]></comments>
		<pubDate>Thu, 15 Dec 2011 13:18:00 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=436]]></guid>
			<description><![CDATA[The Magento Profiler is used to identify performance problems on the server side.  The Profiler can help you find PHP functions which use up too much CPU or functions with slow database queries.
These problems will first be noticed if you have high load on your server. Apache processes can be seen using “top”, where you will see apache or httpd processes jumping to the "top" using a large percentage of CPU.
Using the Profiler requires a fairly deep (e.g. time consuming) analysis, so make sure you are barking up the right tree before proceeding with this. You’ll want to eliminate any...]]></description>
			</item>
		<item>
		<title><![CDATA[Fix 404 error when access admin panel after upgrade or fresh install]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-tutorial/fix-404-error-when-access-admin-panel-after-upgrade-or-fresh-install]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-tutorial/fix-404-error-when-access-admin-panel-after-upgrade-or-fresh-install#respond]]></comments>
		<pubDate>Fri, 14 Oct 2011 13:06:26 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=410]]></guid>
			<description><![CDATA[Some time, you meet this 404 error after upgrade you magento website, or even fresh installation. Your frontend running smooth but you can not access your backend. Do the following ways to bring your backend accessible. One at a time, if problem fixed, it&#39;s not necessary to do anothers.

Clean your cache by manually remove var/cache dir content.
Check your local.xml (app/etc/local.xml). Look for following line...]]></description>
			</item>
		<item>
		<title><![CDATA[Magento - Wordpress Integration. The easiest way]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-tutorial/magento-wordpress-integration-the-easiest-way]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-tutorial/magento-wordpress-integration-the-easiest-way#respond]]></comments>
		<pubDate>Mon, 28 Mar 2011 11:11:56 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=406]]></guid>
			<description><![CDATA[Still searching a best way to intergrate your magento with wordpress, you can have it done in a few small steps, no more headache. Try Fishpig&rsquo;s Magento/WordPresss Integration Extension, and you can make your blog run with magento.
	In this tutorial, we have:
	- Magento installed in root folder (e.g., /public_html/)
	- Wordpress installed in a subfolder (e.g., /public_html/wordpress/)
	- Two software installed on separate database
	First, you need to install Fishpig extension. Grab it by click here. After successful install, you can see a new menu in your admin dashboad. Follow menu:
	&nbsp;
WordPress&gt;Settings&gt;Database / Integration
Config your database settings:
Database Location: Magento/WordPress share a database
Host: localhost
Username: your_wordpress_mysql_username
Password...]]></description>
			</item>
		<item>
		<title><![CDATA[Part 8 - Varien Data Collections]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-8-varien-data-collections]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-8-varien-data-collections#respond]]></comments>
		<pubDate>Tue, 01 Mar 2011 02:38:44 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=399]]></guid>
			<description><![CDATA[Originally, as a PHP programmer, if you wanted to collect together a group of related variables you had one choice, the venerable Array. While it shares a name with C&#39;s array of memory addresses, a PHP array is a general purpose dictionary like object combined with the behaviors of a numerically indexed mutable array.
In other languages the choice isn&#39;t so simple. You have multiple data structures to chose from, each offering particular advantages in storage, speed and semantics. The PHP philosophy was to remove this choice from the client programmer and give them one useful data structure that was &quot;good...]]></description>
			</item>
		<item>
		<title><![CDATA[Part 7 - Advanced ORM - Entity Attribute Value]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-7-advanced-orm-entity-attribute-value]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-7-advanced-orm-entity-attribute-value#respond]]></comments>
		<pubDate>Tue, 01 Mar 2011 02:26:50 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=396]]></guid>
			<description><![CDATA[In the first ORM article we told you there were two kinds of Models in Magento. Regular, or &quot;simple&quot; Models, and Entity Attribute Value (or EAV) Models. We also told you this was a bit of a fib. Here&#39;s where we come clean.
ALL Magento Models inherit from the Mage_Core_Model_Abstract / Varien_Object chain. What makes something either a simple Model or an EAV Model is its Model Resource. While all resources extend the base Mage_Core_Model_Resource_Abstract class, simple Models have a resource that inherits from Mage_Core_Model_Mysql4_Abstract, and EAV Models have a resource that inherits from Mage_Eav_Model_Entity_Abstract
If you think about it, this makes...]]></description>
			</item>
		<item>
		<title><![CDATA[Full page cache is now natively come with Magento CE 1.5.0.1]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-knowledge-base/full-page-cache-is-now-natively-come-with-magento-ce-1-5-0-1]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-knowledge-base/full-page-cache-is-now-natively-come-with-magento-ce-1-5-0-1#respond]]></comments>
		<pubDate>Fri, 25 Feb 2011 12:01:40 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=390]]></guid>
			<description><![CDATA[Great news for customers and developers, full page cache is now come natively with magento community version 1.5.0.1, check it out yourself.
Magento Enterprise Edition already come with full page cache, and this time Magento Community Edition have it.

]]></description>
			</item>
		<item>
		<title><![CDATA[Part 6 - Setup Resources]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-6-setup-resources]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-6-setup-resources#respond]]></comments>
		<pubDate>Thu, 24 Feb 2011 00:45:45 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=385]]></guid>
			<description><![CDATA[On any fast paced software development project, the task of keeping the development and production databases in sync become a sticky wicket. Magento offers a system to create versioned resource migration scripts that can help your team deal with this often contentious part of the development process.
In the ORM article we created a model for a weblog post. At the time, we ran our CREATE TABLE statements directly against the database. This time, we&#39;ll create a Setup Resource for our module that will create the table for us. We&#39;ll also create an upgrade script for our module that will update...]]></description>
			</item>
		<item>
		<title><![CDATA[Part 5 - Models and ORM Basics]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-5-models-and-orm-basics]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-5-models-and-orm-basics#respond]]></comments>
		<pubDate>Thu, 24 Feb 2011 00:37:53 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=381]]></guid>
			<description><![CDATA[The implementation of a &quot;Models Tier&quot; is a huge part of any MVC framework. It represents the data of your application, and most applications are useless without data. Magento Models play an even bigger role, as they typically contain the &quot;Business Logic&quot; that&#39;s often relegated to the Controller or Helper methods in other PHP MVC frameworks.
Traditional PHP MVC Models
If the definition of MVC is somewhat fuzzy, the definition of a Model is even fuzzier. Prior to the wide adoption of the MVC pattern by PHP developers, data access was usually raw SQL statements and/or a SQL abstraction layer. Developers would...]]></description>
			</item>
		<item>
		<title><![CDATA[Part 4 - Layouts, Blocks and Templatese]]></title>
		<link><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-4-layouts-blocks-and-templatese]]></link>
		<comments><![CDATA[http://www.vinagento.com/blog/magento-step-by-step/part-4-layouts-blocks-and-templatese#respond]]></comments>
		<pubDate>Tue, 22 Feb 2011 00:50:40 +0000</pubDate>
		<dc:creator></dc:creator>
			<guid isPermaLink="false"><![CDATA[http://www.vinagento.com/blog/?p=378]]></guid>
			<description><![CDATA[Developers new to Magento are often confused by the Layout and View system. This article will take a look at Magento&#39;s Layout/Block approach, and show you how it fits into Magento MVC worldview.
Unlike many popular MVC systems, Magento&#39;s Action Controller does not pass a data object to the view or set properties on the view object. Instead, the View component directly references system models to get the information it needs for display.
One consequence of this design decision is that the View has been separated into Blocks and Templates. Blocks are PHP objects, Templates are &quot;raw&quot; PHP files (with a .phtml...]]></description>
			</item>
	</channel>
</rss>
