Simply go to your magento installation folder, locate the errors folder and you will find local.xml.sample, simply duplicate the file and rename it local.xml
- Find out what I'm doing, Follow Me :)
Thursday, April 15, 2010
Sunday, April 11, 2010
Magento 1.4 cronjobs
On some points, Magento needs regular maintenance. For instance, when running a shop of which the products are updated frequently, it is needed to refresh catalog indices. Also the search-index might need regular updating. To accomplish these tasks you can run Magento cronjobs. With MagentoTM 1.4 this is even easier. Here's how.
Meet cron
Within Linux environments, the program responsible for running scheduled tasks is called cron. Tasks that are run through cron are referred to as cronjobs. By runnning cronjobs daily or perhaps weekly, you can automate certain processes like refreshing the Magento indices or cleaning up logfiles.
Running cronjobs is something that depends on your hosting environment. Almost every Linux-server is shipped with cron-functionality, but within shared hosting environments it just depends whether you are allowed to use or not. Popular control panels like DirectAdmin or CPanel often allow you to create new cronjobs.
Running a Magento 1.4 job through cron
With Magento 1.3 and older, you had to write your own PHP-scripts to get things done. With Magento 1.4 this has become much easier. Within the Magento directory "shell" you can find various PHP-scripts that automate certain actions. The rest of this tutorial will discuss those actions as well.
Running such a script through cron doesn't mean calling this script through the browser. You'll need command-line access to your Magento site to run such a script manually. In exactly the same way that you run this from the command-line, the cronjob is also run. In the following examples, you will need to replace "/path/to/magento" with the exact directory that contains Magento.
php /path/to/magento/shell/indexer.php reindexall
This will reindex all the Magento indices. Now this command first calls the PHP-program "php" with as first argument the location of the PHP-script, and as second argument something that is used as argument for the script.
It might be that the "php" program is not found by cron, in which case you will need to define the exact path to the "php" binary program:
/usr/local/bin/php /path/to/magento/shell/indexer.php reindexall
To surpress output from the Magento script you can also add the flag "-q" (quiet):
php -q /path/to/magento/shell/indexer.php reindexall
More Magento reindexing
When running the indexer.php script from the command-line we can find more tricks. First of all we can check for the current status of all the indices:
php /path/to/magento/shell/indexer.php --status
We can also refresh a specific index. To do so, we first need to find out which arguments can be used:
php /path/to/magento/shell/indexer.php info
This gives a listing like the following:
catalog_product_attribute Product Attributes
catalog_product_price Product Prices
catalog_url Catalog Url Rewrites
catalog_product_flat Product Flat Data
catalog_category_flat Category Flat Data
catalog_category_product Category Products
catalogsearch_fulltext Catalog Search Index
cataloginventory_stock Stock status
Now we found the technical names for the various indices, which we can use like the following example:
php /path/to/magento/shell/indexer.php --reindex catalog_product_flat
The last example is again something we can use through cron.
Clean logs and using the Magento compiler
Besides refreshing indices, we can also clean up all the logs within the database:
php /path/to/magento/shell/log.php clean
Even cooler is the new Magento Compiler module which is still in beta but gives great performance benefit by reducing the number of include-paths (4 by default) to one single include-path. This mainly saves CPU-resources.
You can check for the current state of the compiler by running the following:
php /path/to/magento/shell/compiler.php state
Once checked you can disable the compiler temporarily, rebuild the include-paths again with the flag "compile" and enable the compiler once more.
php /path/to/magento/shell/compiler.php disable
php /path/to/magento/shell/compiler.php compile
php /path/to/magento/shell/compiler.php enable
Meet cron
Within Linux environments, the program responsible for running scheduled tasks is called cron. Tasks that are run through cron are referred to as cronjobs. By runnning cronjobs daily or perhaps weekly, you can automate certain processes like refreshing the Magento indices or cleaning up logfiles.
Running cronjobs is something that depends on your hosting environment. Almost every Linux-server is shipped with cron-functionality, but within shared hosting environments it just depends whether you are allowed to use or not. Popular control panels like DirectAdmin or CPanel often allow you to create new cronjobs.
Running a Magento 1.4 job through cron
With Magento 1.3 and older, you had to write your own PHP-scripts to get things done. With Magento 1.4 this has become much easier. Within the Magento directory "shell" you can find various PHP-scripts that automate certain actions. The rest of this tutorial will discuss those actions as well.
Running such a script through cron doesn't mean calling this script through the browser. You'll need command-line access to your Magento site to run such a script manually. In exactly the same way that you run this from the command-line, the cronjob is also run. In the following examples, you will need to replace "/path/to/magento" with the exact directory that contains Magento.
php /path/to/magento/shell/indexer.php reindexall
This will reindex all the Magento indices. Now this command first calls the PHP-program "php" with as first argument the location of the PHP-script, and as second argument something that is used as argument for the script.
It might be that the "php" program is not found by cron, in which case you will need to define the exact path to the "php" binary program:
/usr/local/bin/php /path/to/magento/shell/indexer.php reindexall
To surpress output from the Magento script you can also add the flag "-q" (quiet):
php -q /path/to/magento/shell/indexer.php reindexall
More Magento reindexing
When running the indexer.php script from the command-line we can find more tricks. First of all we can check for the current status of all the indices:
php /path/to/magento/shell/indexer.php --status
We can also refresh a specific index. To do so, we first need to find out which arguments can be used:
php /path/to/magento/shell/indexer.php info
This gives a listing like the following:
catalog_product_attribute Product Attributes
catalog_product_price Product Prices
catalog_url Catalog Url Rewrites
catalog_product_flat Product Flat Data
catalog_category_flat Category Flat Data
catalog_category_product Category Products
catalogsearch_fulltext Catalog Search Index
cataloginventory_stock Stock status
Now we found the technical names for the various indices, which we can use like the following example:
php /path/to/magento/shell/indexer.php --reindex catalog_product_flat
The last example is again something we can use through cron.
Clean logs and using the Magento compiler
Besides refreshing indices, we can also clean up all the logs within the database:
php /path/to/magento/shell/log.php clean
Even cooler is the new Magento Compiler module which is still in beta but gives great performance benefit by reducing the number of include-paths (4 by default) to one single include-path. This mainly saves CPU-resources.
You can check for the current state of the compiler by running the following:
php /path/to/magento/shell/compiler.php state
Once checked you can disable the compiler temporarily, rebuild the include-paths again with the flag "compile" and enable the compiler once more.
php /path/to/magento/shell/compiler.php disable
php /path/to/magento/shell/compiler.php compile
php /path/to/magento/shell/compiler.php enable
Thursday, April 1, 2010
How to link pages using store URL short code
If you want to add hyperlinks between the pages on your site you could specify the full http://www.yourdomain/…, but Magento provides a short code which automagically prefixes your base store URL. If you have a CMS page with the slug “about-us”, you can link to that page from any other CMS page
using:
<a href="{{store url='about-us'}}">About Us</a>
If you wanted to link to your home page use:
<a href="{{store url=''}}">Home Page</a>Friday, March 26, 2010
Increase the quality of photos on Magento
I was recently confronted with problems of quality photos on Magento.
At first, I vainly sought an option to resolve this with the Magento backend... I finally get to the obvious: this is not possible (at least until version 1.3).
I then studied the source code to determine how the framework manages and generates mainly the different sizes of pictures (on the page list, thumbnails, etc..) products.
I discovered that Magento uses GD2, with a quality setting to 80% by default (not changeable via configuration, back-office or XML). A value 80/100 quality is good in most cases. Nevertheless in e-commerce have known that a very good picture quality can make the difference.
The idea is to push the compression quality (jpeg) to 90%, the possible options are:
1. modify the PHP code found above: No, you should never directly edit the code from the core of Magento! (just as one shouldn’t cross the streams.)
2. create a module to administer the value of the compression quality via the back office: interesting, but reusable too long to achieve. I pass! :-)
3. override the code: easy, fast and clean: the solution I have chosen
Change the compression quality photos Magento:
1.
Step 1
Copy the file "/ lib/Varien/Image/Adapter/Gd2.php" to "/ app/code/local/Varien/Image/Adapter/Gd2.php" by creating the missing directories if necessary.
2.
Step 2
Open the file Gd2.php (copy, not original) at about line 80 and substitute:
call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName);
by:
if ($this->_fileType === IMAGETYPE_JPEG) {
call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName, 90);
} else {
call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName);
}
In the code above, I opted for 90, but you can change this value from 0 to 100 quality.
3.
Step 3
Finally, don’t forget to empty the cache of images via System> Cache Management.
That was simple, effective and reusable on any project, from the time you work with images in jpeg format (which format most common with digital photography) and your server supports GD2.
At first, I vainly sought an option to resolve this with the Magento backend... I finally get to the obvious: this is not possible (at least until version 1.3).
I then studied the source code to determine how the framework manages and generates mainly the different sizes of pictures (on the page list, thumbnails, etc..) products.
I discovered that Magento uses GD2, with a quality setting to 80% by default (not changeable via configuration, back-office or XML). A value 80/100 quality is good in most cases. Nevertheless in e-commerce have known that a very good picture quality can make the difference.
The idea is to push the compression quality (jpeg) to 90%, the possible options are:
1. modify the PHP code found above: No, you should never directly edit the code from the core of Magento! (just as one shouldn’t cross the streams.)
2. create a module to administer the value of the compression quality via the back office: interesting, but reusable too long to achieve. I pass! :-)
3. override the code: easy, fast and clean: the solution I have chosen
Change the compression quality photos Magento:
1.
Step 1
Copy the file "/ lib/Varien/Image/Adapter/Gd2.php" to "/ app/code/local/Varien/Image/Adapter/Gd2.php" by creating the missing directories if necessary.
2.
Step 2
Open the file Gd2.php (copy, not original) at about line 80 and substitute:
call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName);
by:
if ($this->_fileType === IMAGETYPE_JPEG) {
call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName, 90);
} else {
call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName);
}
In the code above, I opted for 90, but you can change this value from 0 to 100 quality.
3.
Step 3
Finally, don’t forget to empty the cache of images via System> Cache Management.
That was simple, effective and reusable on any project, from the time you work with images in jpeg format (which format most common with digital photography) and your server supports GD2.
Wednesday, March 24, 2010
Remove unwanted PEARLib files
When you install or update Magento Commerce or one of the Magento Extensions that uses PEAR (PHP Extension and Application Repository), the files will be downloaded to {path_to_magento}/downloader/pearlib/cache/ and {path_to_magento}/downloader/pearlib/download/ within your Magento installation directory. After installation the downloaded files are not automatically deleted. These directories can grow quite large if they go unchecked. Remember to run the following command after installing or upgrading Magento or a Magento Extension
$ cd {path_to_magento}
$ rm -rf downloader/pearlib/cache/* downloader/pearlib/download/*Alternatively remove all the files and folders in these two directories using an FTP Client or a Browser File Manager within CPanel
Sunday, March 21, 2010
How to Speed up your Magento Site
It has surely been a pain to have such a nice eCommerce platform, but with slow page loading problem. It mainly happens for the javascript and css and all files being loaded at the same time. As Yahoo YSlow says, the more number of HTTP requests, more slow is the website.
So, here is a small htaccess trick, which makes the Magento Site real FAST!! We are enabling the GZip Compression here. Works perfect and has been tested..
Just goto your site root and find the .htaccess file.
Open it and edit it on your text editor.
So, here is a small htaccess trick, which makes the Magento Site real FAST!! We are enabling the GZip Compression here. Works perfect and has been tested..
Just goto your site root and find the .htaccess file.
Open it and edit it on your text editor.
You will find this code there, around Line 77 - 97,
## http://developer.yahoo.com/performance/rules.html#gzip
# Insert filter on all content
###SetOutputFilter DEFLATE
# Insert filter on selected content types only #AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript # Netscape 4.x has some problems...
#BrowserMatch ^Mozilla/4 gzip-only-text/html
# Netscape 4.06-4.08 have some more problems
#BrowserMatch ^Mozilla/4.0[678] no-gzip
# MSIE masquerades as Netscape, but it is fine
#BrowserMatch bMSIE !no-gzip !gzip-only-text/html
# Don't compress images
#SetEnvIfNoCase Request_URI .(?:gif|jpe?g|png)$ no-gzip dont-vary
# Make sure proxies don't deliver the wrong content
#Header append Vary User-Agent env=!dont-vary
Just Replace it with ,
## http://developer.yahoo.com/performance/rules.html#gzip
# Insert filter
SetOutputFilter DEFLATE
# Netscape 4.x has some problems_
BrowserMatch ^Mozilla/4 gzip-only-text/html
# Netscape 4.06-4.08 have some more problems
BrowserMatch ^Mozilla/4.0[678] no-gzip
# MSIE masquerades as Netscape, but it is fine
BrowserMatch bMSIE !no-gzip !gzip-only-text/html
# Don’t compress images
SetEnvIfNoCase Request_URI .(?:gif|jpe?g|png)$ no-gzip dont-vary
# Make sure proxies don’t deliver the wrong content
Header append Vary User-Agent env=!dont-vary
# enable resulting html compression
php_flag zlib.output_compression on |
Friday, March 19, 2010
Problem: logging into magento 1.4 backend after installation on localhost
This problem I had during magento community installation process on localhost. I have used EasyPHP5.2.10 and after the installation of magento with the downloader I was not able to login in the backend.
After a research on internet I have seen many posts talking about languages session problem. So I noticed that if you try to change language in the installation problem it reload the page on the default EN-US.
So I managed the problem by going in the apache server config file changing “localhost:80 “to “127.0.0.1:80“. After that I have installed magento again at uri http://127.0.0.1/mangento/. In this way when I have chosen English to Italian language it worked! Than I was able to join my magento backend.
Subscribe to:
Posts (Atom)
