This way don’t need install any extension or module. Useful Magento Tips.

Creat a catalog  on your magento admin panel,  Set the status to  “NO”  don’t show on your magento  store. and check from URL find out this catalog’s ID. OK you could enter this ID to Refer those best sellers or special promotion products:

<h3>Bestsellers</h3>
{{block type=”catalog/product_list” category_id=”49″ template=”catalog/product/list.phtml”}}

The above image is only a low-resolution diagram example table list. Its usefull for you learn magento database diagram.

Follow is introduce my experience on how transfer Magento Mysql Database from one server to another remote server:

Option A
Click the database that you wish to backup (eg. d01234567)
Click Export
Click the appropriate option:
-Structure only
-Structure and data (recommended)
-Data only
Click the “Save as File” option
Click the “Go” button

This is for small database file transfer.

Option B
If your database is too large to backup via phpMyAdmin, you may backup the database through an SSH session if your plan supports it (SSH available on Advantage and Business plans):
Your MySQL databases can be administered through an SSH session via command line (especially if you have large sized data to import/export):

First, turn SSH on for your account:

1. Login to the Control Panel
2. Click Hosting
3. Click Settings
4. In the SSH section, use the pull-down menu to enable SSH if it’s not yet enabled

5. Then find an SSH client such as WinSCP (available for free from http://prdownloads.sourceforge.net/winscp/winscp380.exe?download )

SSH connections can be established with the following login credentials:

Username
Password
Host: Your hosting IP(port 22)

6. Using Netfirms File Manager or the touch command in SSH, create a file called dbBackupFile.sql. The file may reside anywhere inside your /www folder.

7. To make a backup copy of your mysql magento database via a SSH session:

%/usr/local/nf/bin/mysqldump -e –force –quick -h mysqlhost -u Username -pPassword DatabseID > dbBackupFile.sql

(You will then be prompted to enter your database password.)

Option C
You may use a PHP or Perl script to backup your Magento MySQL data.

The following sample codes (you can name the file dbBackupFile.php in place it inside your www folder) will create a backup .sql file of your database inside your www folder:

PHP

backup.sql”;
exec($command,$error);
if ($error) {
echo “Error: “. $error;
}
?>

Perl/CGI

#!/usr/bin/perl
print “Content-type: text/htmlnn”;
$cmd=system “/usr/local/nf/bin/mysqldump -uu70459875 -p8c2f28 d60417018 > perldbbackup.mysl”;
if ($cmd)
{
print “Error!!!!”;
}
else
{print “Sucess!!!!”;
}

Option D

SCHEDULING YOUR MAGENTO DATABASE BACKUPS
To create a cron job to schedule your database backups please click here for further instructions.

Chapter 1: Introducing Magento

What is Magento
Magento is a new professional open-source eCommerce solution offering unprecedented flexibility and control. With Magento, never feel trapped in your eCommerce solution again.
Since it is open-source, Magento‘s code is available free for download. Just go to www.magentocommerce.com/download to download your copy today. In this guide we will introduce key concepts and walk you through setting up your Magento store, from installing Magento, to entering products.
Elements and Terminologies of Magento Sites
Magento is made up of a few different elements which define the functionality, design and business logic of the site. In order to follow along with the User Guide it is crucial that you have a good grasp of the terminologies used to describe these elements of the Magento system. The terminologies introduced in this chapter are most likely new territory for you, so take your time and read through them thoroughly. But most importantly, don‘t be discouraged if you can‘t fully grasp the concept of all these new terminologies – This chapter merely serves to introduce them, and further chapters will dig deeper into, and expand upon, these simple definitions.
Websites and Stores
One of the most powerful features of Magento is the ability to manage multiple websites and stores from one back-end. This allows store owners to manage stores on different URLs, display the same products in different languages on the same URL, along with a variety of other setups. If you will only be selling your products from one URL in one language you will not need to use this functionality, but the ability to easily expand into additional languages makes Magento scalable as your business grows out of your home market.
Websites
A website is made up of one or more stores which share the same customer information, order information and shopping cart. This is a very broad term that can be adopted to define the unique needs of individual merchants.
Stores
Stores can be setup in a variety of ways, but remember that if they are part of the same website they will share certain information.

Store Views
Store Views are mainly used for different languages, so if you wanted to have a store displayed in English and Spanish, for example, you could create the store once and create two different store views for that store. A few scenarios to define the different uses of website and store are as follows:
Scenario 1: One Website with multiple stores
Scenario 2: Two Stores with two store views each
Scenario 3: One Website with one store and one store view The most common setup will be a one website and one store setup, but understanding the functionality of multiple websites and stores will help you understand why certain values are

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (`/catalog_product_

| |- etc/
| – sql/
Code Pools
Modules are located in one of three code pools. The code pools are: core, local, and
community. All of the modules distributed with the base Magento are in the core
code pool. All of the custom modules that you develop can be installed in the local
code pool. The community pool was originally designed for installed third-party
modules, but this idea might be phased out, as you can simply install any module in
local as well as community.
- app/
- code/
|- local/
|- community/
- core/
Module Packages
All models exist under a package directory. The package serves no purpose other
than to allow for consistent naming of classes. All Magento modules are part of the
Mage package. Thus, all Magento class names begin with Mage_. It is an acceptable
practice to create a new package for your custom modules that has the name of your
company or organization instead of Mage. There is no functional detriment when not
using Mage as your package.
Models
Models are the muscle ofMagento. They help move data from the database into the
program itself. The output, or rendering, of the data is done by the Blocks, but the
models are mainly responsible for manipulating the data. Models, in any programming
environment, help to identify and shape data domains. What this means is that
models draw boundaries between definitions of data groups and relate data groups
to other data groups.

Figure 3.1
Magento provides standard functionality that you would expect from any shopping
cart, including:
• Multiple category trees

• Definable attributes
• Customer and customer groupmanagement
• Discount rules for promotions
• Newsletter management
• Web page manager
• Order review system
• Reporting features
• System configuration and settings
In addition to these features, there are a number of features that would not be provided
by default in other shopping carts. A short list of these impressive features
include:
• Reviewing search terms
• Reviewing customer tags
• Poll manager
• Currency exchange rates
• Google Sitemap integration
• Abandoned shopping cart report
• Layered category navigation
None of these features by themselves are probably that impressive. But to have a
system in which they are all present, by default, with no plugins necessary, is truly a
breath of fresh air in the open source e-commerce arena.
By now, you’ve probably “clicked” around in the backend a little. The remainder
of this chapter will guide you through the basics of what Magento has to offer and
cover Magento specific terms. It is necessary to have a thorough understanding of
Magento’s basic operation in order to better understand the code. Let’s start with
Magento’s product catalog.

http://magentocommerce.com/.

LAMP/WAMP Platform
If you are on theWindows platformthe easiest way to install PHP, Apache andMySQL
is with the XAMPP family of packages from http://apachefriends.org. Install the
XAMPP-lite package anywhere on your drive and run the setup.bat file. There is a
version of XAMPP forMac OS X and Linux as well.
Subversion
For developing your own modules, it is recommended that you use Subversion
version control to keep track of all of your code changes. TortoiseSVN from
http://tortoisesvn.tigris.org is the recommended client and server for Windows
users. For Mac and Linux users, the command line svn program plus the PHP package
websvn is recommended. If you are not familiar with the Subversion system, you
can read more about it at the SubversionWeb site (http://subversion.tigris.org/).

MySQL Tools
Apart from the actual MySQL server, it is most useful to have a graphical client to
inspectMagento’s database tables from time to time. TheMySQL Query Browser tool
is the official client provided by MySQL AB and is available for all major operating
systems. Some users prefer mysqlcc or phpMyAdmin over MySQL Query Browser,
though.
Installation
Unzip Magento into your Web server’s document root (from here on, referenced as
{docroot}). You should see a directory layout like this:
{docroot}/magento/
app/
index.php
js/
lib/
LICENSE.txt
media/
pear
skin/
var/
Database Setup
Magento will not create its required database for you, even if your database user
has proper rights to create a database. Because of this, we will need to create the
database using one of the previously mentioned MySQL tools. A normal database
name, sometimes called a schema, can be “magento”, or “magento_dev”, or you can
even include the version number “magento_10”.
Magento Setup
You should now continue withMagento’s base installation by pointing your browser
to http://localhost/magento/. Here, you will see a basic step-by-step form for in

stalling most PHP Web applications. Follow the on-screen directions and your Magento
installation will be complete.
Sample Data
If this is your first time trying out Magento you should install the optional sample
data. The sample data is provided as a separate download as it is about 35 MB. The
sample data provides some sample products, categories, and product images. Once
you have downloaded the package, copy the media folder over your own media folder
under your Magento installation. Then run the provided SQL file with your MySQL
management tool.
As of the time of thiswriting, the sample data is distributed as a complete database
installation. Therefore, it needs to be inserted before you proceed with the regular
setup. The regular setup will actually upgrade the sample data to the latest version.
Initializing Subversion
Magento has three directories from which modules are executed: core, community,
and local. All the examples in this book assume that you are developing in the local
module directory. Under the local directory, you can group all of your modules together
under one package. This package is called Mage for all magento core modules,
but this book will use Company for all the examples. You can use any package name
besides Company for a package name that represents your company or organization.
Initializing subversion is a bit tricky. First, you need to initialize a repository. Then,
you need to create a folder or directory to import into this new repository. After that
you are not ready to start using subversion. The directory which was imported needs
to be removed, and then checked out of the repository in order for it to be connected
with subversion. Let’s look at the steps in detail.
Picking a subversion repository on the Linux platform is pretty easy. After
installing Subversion from RPM, there usually exists a directory similar to
/var/lib/subversion/repositories/. Initialize a new repository with the command:
svnadmin create /var/lib/subversion/repositories/magento_modules

If you are using TortoiseSVN underWindows, create a folder anywhere on your computer,
right-click that folder, and select Create repository here… from the TortoiseSVNmenu.
Our goal for setting up Subversion is to have a folder named Company under the
app/code/local directory of Magento. This will allow us to easily add new modules
and save our work to Subversion whenever we want. Create a new directory under
the app/code/local folder called svn_import. Under this temporary svn_import directory
create another folder called Company, or whichever name you’ve decided to use
for your packaging. If you are running on a Unix platform, run this command from
inside the svn_import directory (ignoring the shell prompt):
[svn_import]$ svn import . \
file:///var/lib/svn/repositories/magento_modules/
OnWindows, use TortoiseSVN by right-clicking on the svn_import folder and choosing
the Import… menu item. A new dialog will appear and ask you to input the
URL of the repository. Click the ellipses button and browse to the folder which you
designated as your repository in the previous step.
Delete the svn_import folder after successfully importing into your new repository.
Next, we need to checkout the folder we just imported to get a Subversion activated
directory. On Unix:
[local]$ svn checkout \
file:///var/lib/svn/repositories/magento_modules/Company
OnWindows, right click on the local folder and choose SVN Checkout…. Accept the
default settings in the dialog, and confirm Yes when it asks you if you really want to
overwrite the folder.
Covering all Subversion commands is beyond the scope of this book. But you are
now prepared to develop and save your custom Magento modules in a subversion
directory if you so choose.

examples in this book are shortened to fit on the pages, so style may suffer in some
instances to conserve space.
When referring to variables, classes, objects, or concepts this book will put the
word or words in question into italics. When specifically referring to the word of a
variable, class name, etc. the words will be formatted as inline code. File names will
also be formatted this way.
When talking about Mage_Core_Model_Abstract the object class italics will be
used, but when talking about why a class is named Mage_Core_Model_Abstract, inline
code formatting will be used.
XML Examples
When referencing XML the ellipses, …, are used to suggest that other, optional, or
pre-existing XML tags are present. Given the XML structure below:
<config>
<modules>
<Company_RewardPoints>
<version>0.1.0</version>
<depends>
<Mage_Customer />
<Mage_Checkout />
</depends>
</Company_RewardPoints>
</modules>
<global>
<resources>
<rewardpoints_setup>
<setup>
<module>Company_RewardPoints</module>
<class>Mage_Core_Model_Resource_Setup</class>
</setup>
<connection><use>core_setup</use></connection>
</resources>
</global>
</config>
The section enclosed in the rewardpoints_setup tag may be represented as this:
<config>

…
<global>
…
<resources>
<rewardpoints_setup>
<setup>
<module>Company_RewardPoints</module>
<class>Mage_Core_Model_Resource_Setup</class>
</setup>
<connection><use>core_setup</use></connection>
</resources>
…
</global>
…
</config>
Operating SystemConsiderations
When possible, this book will describe technical procedures for Linux,Mac OS X, and
Windows operating systems. However, to keep examples brief, simple references to
file locations will use Windows directory and file naming conventions. When listing
directories, the forward slash (/) will be used as a directory separator as this convention
falls in line with standard Unix behavior (Mac OS X and Linux) plus PHP and
Apache can automatically translate forward slashes to back slashes where need be
onWindows.
Do not be surprised to see a directory like this:
C:/xampp/apache/htdocs/magento/