Основы работы с Git

• Введение
• Основы работы с удаленным репозиторием
• git clone — создание копии (удаленного) репозитория
• git fetch и git pull — забираем изменения из центрального репозитория
• git push — вносим изменения в удаленный репозиторий
• Работа с локальным репозиторием
• Базовые команды
• Ветвление
• Прочие команды и необходимые возможности
• Серверные команды репозитория
• Рецепты
• Ссылки

Введение

Git (произн. «гит») — распределённая система управления версиями файлов. Проект был создан Линусом Торвальдсом для управления разработкой ядра Linux. На сегодняшний день поддерживается Джунио Хамано.
Система спроектирована как набор программ, специально разработанных с учётом их использования в скриптах. Это позволяет удобно создавать специализированные системы контроля версий на базе Git или пользовательские интерфейсы. Например, Cogito является именно таким примером фронтенда к репозиториям Git, а StGit использует Git для управления коллекцией патчей.

Конфигурация Nginx + PHP + FastCGI для Magento

Не так давно пришлось оптимизировать сервер у заказчика. Нужно было заменить Apache на Nginx. 
На официальном форуме можно найти примеры конфигурации, например
http://www.magentocommerce.com/boards/viewthread/7931/ ,
однако использование rewrite для таких случаев всячески порицается разработчиком сервера.

Замечания

* Процесс сборки nginx и php описан на офсайтах
* Предполагается, что php с поддержкой fast-cgi настроен и работает на
127.0.0.1:8888, а nginx на 127.0.0.1:80
* Папка, в которой лежат файлы Magento: /home/alex/www/server.com/
* Так как Nginx работает с php напрямую, а не через связку с Apache, следует
обратить особое внимание
  на директивы для php, которые идут в .htaccess из стандартной поставки magento. Nginx 
  не обрабатывает директивы из .htaccess и поэтому их нужно перенести в php.ini. 
  У меня, например, перестала работать загрузка картинок к товарам, пока не добавил suhosin.session.cryptua off в php.ini.
* Предполагается, что в Magento настроены ЧПУ

Ниже привожу свою конфигурацию. Дополнения и комментарии всячески приветствуются.

    server {
    listen 127.0.0.1:80;
    server_name server.com;
    #Включаем сжатие
    gzip on;
    #gzip_comp_level 9;
    gzip_min_length 1000;
    gzip_proxied any;
    gzip_types text/plain application/xml text/html text/css text/js application/x-javascript;
    # Важно!!!! Ниже должна быть указана папка в которой лежит код Magento
    root /home/alex/www/server.com/;

    location / {
    index index.php;
    error_page 404 = @magento;
    }
    # Фикс для js
    location /js/ {
    index index.php;
    error_page 404 = @magento_js;
    }
    # Фикс для случая, когда используется расширение FOOMAN_Speedster.
    location ^~ /minify/ {
    rewrite ^/minify/([^/]+)(/.*.(js|css))$ /lib/minify/m.php?f=$2&d=$1 last;
    break;
    }

    location @magento {
    # Если fastcgi_params лежит по другому пути то заменить на свой
    include /etc/nginx/fastcgi_params; #Важно !!!!
    fastcgi_pass 127.0.0.1:8888;
    fastcgi_param SCRIPT_FILENAME $document_root/index.php; #Важно !!!
    }

    location @magento_js {
    include /etc/nginx/fastcgi_params;
    fastcgi_pass 127.0.0.1:8888;
    fastcgi_param SCRIPT_FILENAME $document_root/js/index.php;
    }
    location ~ .php$ {
    index index.php;
    include /etc/nginx/fastcgi_params;
    fastcgi_pass 127.0.0.12:8888;
    fastcgi_index index.php;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    }

    location ~* \.(jpg|gif|png|css|js|jpeg|ico)$ {
    if (-f $request_filename) {
    access_log off;
    expires 7d;
    }

    }

После такой настройки плагин YSlow дает сайту уровень B по скорости. Если очень постараться и
 вынести всю статику на отдельный поддомен, то можно еще ускориться. 

Источник 

Magento + Nginx

This config currently seems to work for the <1 .4="" p="" versions="">

server {
  server_name example.com;
  root /var/www/vhost/example.com/htdocs;
  access_log /var/log/nginx/example.com.access.log main;
  index index.php;
 
  location / {
    try_files $uri $uri/ /index.php?$args; 
  }
 
  # set a nice expire for assets
  location ~* "^.+\.(jpe?g|gif|css|png|js|ico|pdf|zip|tar|t?gz|mp3|wav|swf)$" {
    expires    max;
    add_header Cache-Control public;
  }
 
  # the downloader has its own index.php that needs to be used
  location ~* ^(/downloader|/js|/404|/report)(.*) {
    include fastcgi_params;
    fastcgi_index index.php;
    fastcgi_param  SCRIPT_FILENAME  $document_root$1/index.php$1;
    fastcgi_read_timeout 600;
    fastcgi_pass  127.0.0.1:9000;
  }
 
  location ~* \.php {
    include fastcgi_params;
    fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
    fastcgi_read_timeout 600;
    fastcgi_pass  127.0.0.1:9000;
  }
 
}

This config works for version 1.7:

server {
  root    /home/magento/web/;
  index    index.php;
  server_name magento.example.com;
  location / {
    index index.html index.php;
    try_files $uri $uri/ @handler;
    expires 30d;
  }
  location ~ ^/(app|includes|lib|media/downloadable|pkginfo|report/config.xml|var)/ { internal; }
  location /var/export/ { internal; }
  location /. { return 404; }
  location @handler { rewrite / /index.php; }
  location ~* .php/ { rewrite ^(.*.php)/ $1 last; }
  location ~* .php$ {
    if (!-e $request_filename) { rewrite / /index.php last; }
    expires off;
    fastcgi_pass 127.0.0.1:9000;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    fastcgi_param MAGE_RUN_CODE default;
    fastcgi_param MAGE_RUN_TYPE store;
    include fastcgi_params;
  }
}

Fooman Speedster is a popular extension that requires editing your server configuration. If you use it add this at the bottom of one of the server configurations above, right before the closing bracket.

 rewrite ^/minify/([0-9]+)(/.*.(js|css))$ /lib/minify/m.php?f=$2&d=$1 last;
 rewrite ^/skin/m/([0-9]+)(/.*.(js|css))$ /lib/minify/m.php?f=$2&d=$1 last;
 
 location /lib/minify/ {
   allow all;
 }

Magento: Magento 1.3.x, 1.4.x, 1.5.x, 1.6.x and 1.7.x update procedure

This is actually the current explanation from the Magento 1.3.x, 1.4.x, 1.5.x, 1.6.x and 1.7.x  x update procedure.It includes step x step directions as well as repair info.

Get ready for Magento update (for 1.3.x, 1.4.x x variations only)

Allows image resolution you have aged Magento 1.3.x – 1.4.x.x shop and you also have to update this in order to most recent Magento 1.7.x edition.To begin with it really is strongly suggested in order to back-up your own reside shop files/database as well as deactivate Magento compiler cache.
After that you want to get SSH accessibility from the web hosting supplier as well as connect with your own machine through SSH process (using Cpanel control covering or even Putty SSH customer with regard to Windows).
Right after link through SSH, visit your own shop document as well as perform these types of instructions:

1 Modify accord upon lib/pear document in order to writable (recursively):

chmod -R 777 lib/PEAR

2 Perform this particular control to get ready Magento with regard to update:

./pear mage-setup

Almost certainly you guys will discover this particular outcome right after control performance: Station “connect.Magento commerce.com/core” has already been initialized

Update through Magento 1.3.x, aged 1.4.x in order to Magento 1.4.2.0

Update in order to 1.4.2.0 is needed, even though you get some new aged Magento 1.3.x shop in order to 1.7.x edition.
1 Perform Magento update control:

./pear upgrade -f magento-core/Mage_All_Latest-stable

Outcome from the control will reveal exactly what primary deals had been improved:
…
upgrade ok: channel://connect.magentocommerce.com/core/Mage_Centinel-1.4.2.0
upgrade ok: channel://connect.magentocommerce.com/core/Interface_Frontend_Base_Default-1.4.2.0
upgrade ok: channel://connect.magentocommerce.com/core/Phoenix_Moneybookers-1.2.3
upgrade ok: channel://connect.magentocommerce.com/core/Find_Feed-1.0.7
upgrade ok: channel://connect.magentocommerce.com/core/Interface_Adminhtml_Default-1.4.2.0

2 Whenever this particular section of the update is going to be total, get into these types of instructions:

chmod 550 ./mage
./mage mage-setup .

People will discover this particular outcome right after control performance:
Effectively additional: http://connect20.magentocommerce.com/community

This means which Magento link 2 .0 station had been put into the actual stations listing effectively.

3 Following, get into this particular control:

./mage sync

The end result is going to be:
…
Successfully added: community/Mage_Locale_en_US-1.4.2.0
Successfully added: community/Interface_Install_Default-1.4.2.0
Successfully added: community/Phoenix_Moneybookers-1.2.3
Successfully added: community/Mage_Downloader-1.5.0.0
Successfully added: community/Lib_Google_Checkout-1.4.2.0

Update in order to Magento 1.4.2.0 is actually total and today you are able to continue along with update in order to Magento 1.7.x edition.

Update through Magento 1.4.x, 1.5.x, 1.6.x in order to Magento 1.7.x

Right now you guys may update the shop in order to edition 1.7.0.2 .
Prior to going forward with this particular portion of Magento update, it is very important notice as to what edition Magento update intrigue will certainly get some new shop.Get into this particular control to check on this particular:

./mage list-upgrades

In case you will discover this particular outcome:
Updates for community:
Mage_All_Latest: 1.4.2.1 => 1.7.0.2
Lib_Js_Mage: 1.4.2.0 => 1.7.0.2
Lib_Varien: 1.4.2.0 => 1.7.0.2

This means that the Magento is going to be improved in order to edition 1.7.0.2. When it is not really the thing you need you are able to modify update station in order to “beta” as well as get some new Magento in order to RC (beta) edition.

1 Get into this particular control to improve the actual update station in order to stable (remember, “stable” station will certainly get some new Magento in order to most recent 1.7.x stable version):

./mage config-set preferred_state stable

Following this the actual “./mage list-upgrades” control will reveal this particular outcome:
Updates for community:
Mage_All_Latest: 1.4.2.1 => 1.7.0.2.
Lib_Js_Mage: 1.4.2.0 => 1.7.0.2.
Lib_Varien: 1.4.2.0 => 1.7.0.2.
Lib_Phpseclib: 1.4.2.0 => 1.7.0.2.
Mage_Core_Adminhtml: 1.4.2.0 => 1.7.0.2.
Mage_Core_Modules: 1.4.2.0 => 1.7.0.2.

2 Right after station choice you are able to get some new Magento in order to Magento 1.7.0.2) employing this control:

./mage upgrade-all --force

In case “./mage upgrade-all -force” will never function, you can test in order to perform this particular control:

./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force

You will notice improved deals on the display screen:
…
Package upgraded: community/Mage_Locale_en_US 1.7.0.2
Package upgraded: community/Lib_Mage 1.7.0.2
Package upgraded: community/Lib_ZF 1.11.1.0
Package upgraded: community/Lib_Js_Prototype 1.7.0.2.
Package upgraded: community/Lib_ZF_Locale 1.11.1.0

Right now the actual update is actually total and you may perform data source update going to your own Magento shop within your internet browser, this method will require a number of moments, therefore have patience.In case every thing had been improved properly, you will notice improved shop within your internet browser.Prior to data source update it is strongly recommended to improve some memory space limitations associated with the PHP motor.

When it is impossible to improve this, you can test in order to perform data source update through SSH, electronic. gary the gadget guy.:

php -f ./index.php

Whenever data source update is going to be completed, you should check edition of the shop within the footer associated with Magento management screen.

Repair

1 Magento update software mistake:

upgrade-all: Booking with regard to adequate create document accord.
Mistake: upgrade-all: Your own Magento document don't have adequate create accord, that downloader needs.
Perform this particular control to correct the actual mistake: 

chmod -R 777 Upgrade

2 Magento update software mistake:

upgrade-all: Incorrect balance within compare Stabilities discussion.
Perform these types of instructions, it is going to repair the problem:

./mage channel-add connect20.magentocommerce.com/community
./mage channel-add connect20.magentocommerce.com/core
./mage sync

Or even like a remedy you are able to operate this particular control:
 

./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force

3 Machine mistake:

“Internal Machine Error” rather than Magento local store web page or even management area webpages.

Almost certainly problem is actually linked to incorrect accord.

Repair this problem using 1 of these recursive instructions:

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;

4 Magento mistake: Various mistakes within Magento data source.

Re-index your own data source within Magento management screen as well as crystal clear Magento cache.

5 Magento mistake:

“Invalid way of clean() method”.

Crystal clear Zend cache (all documents, such as “Backend” folder) within [magento_folder]/app/code/core/Zend/Cache/

6 Magento mistake:

“Call to some associate functionality to Html() on the non-object within …/Layout.php”.

Open [magento_folder]/app/design/frontend/default/[your_theme]/layout/page.xml and replace this line of the code:

With:

7 Magento mistake:

“Maximum crucial dimension should be smaller sized 32″. Crystal clear Magento cache.

8 Pagination is not really displaying upon item real estate:

Open up this particular document: app/code/core/Mage/Catalog/Block/Product/List/Toolbar.php

As well as substitute this particular type of the actual program code
course Mage_Catalog_Block_Product_List_Toolbar stretches Mage_Core_Block_Template
along with:
course Mage_Catalog_Block_Product_List_Toolbar stretches Mage_Page_Block_Html_Pager

9 Magento mistake:

Line not really discovered: 1 054 Not known line ‘custom_use_parent_settings’ within ‘where clause’
Re-index your own data source utilizing Control panel covering.
10 Magento mistake:
Are not able to connect with the actual data source. What is /app/etc/local.xml and ensure there is this kind of program code

{{db_model}}

Источник 

Using Media Image Product Attributes

Posted on: 12th Sep 2011 By: Adam Moss 9 Comments

This is perhaps a bit of a hidden gem with Magento, because it can be extremely useful when needed. Here’s a scenario: your client wants an image on their product page which is detached from the main image gallery. A solution may be a text field or dropdown attribute, which can be used to enter a URL to the chosen image. This won’t help clients who want to add new images though unless they have sufficient FTP privelages – we all know that this can have similar consequences as letting a bull loose in a china shop, then pricking its ass with a needle.
The solution is a media image attribute, this is how to set one up…

Magento модуль для импорта нескольких изображений товара

Magento: Import Multiple Images for Products Module

Posted on October 9, 2009 by Josh Pratt

Update: If you are using Magento 1.5 or higher, please see my Revised Multiple Image Import Module post
I still am confused as to why Magento hasn’t built-in the ability to upload multiple images for each product. After scoping it out, finally, I discovered that the modification was quite simple. I haven’t put the module up on Magento Connect yet (not sure if I will), but here I will lay out how to do it, which for some of you may help you understand how modules work, if you don’t know already.
I’ve seen some solutions out there that modify core code, some that just take a file and move it to your /app/code/local/ retaining the same directory structure, so as to just override the file. I don’t recommend either of these methods (especially the first), as with a true module you are setting up a much better environment over time for this to last. And a module allows you to ONLY override the methods you need to modify, instead of entire classes. Plus, you can easily disable the module right in the admin (Admin >> System >> Configuration >> Advanced).
Be sure you replace all of the “YOURSTUFF” with your name or company name.
I have only tested this with 1.3.2.4

Home » Blogs » Malgorzata Dziedzic's blog

How to use Magento Shipping Table Rates

07/10/2009 - 22:58 / Posted by Malgorzata Dziedzic

Login to post comments

With Magento you can set few kinds of shipping methods: flat rate, table rates or even real-time carrier rates from UPS, FedEx and DHL. You can also use free shipping discounts, that can be created for order amounts, or as part of specific marketing promotions.
To set shipping methods in backoffice go to System -> Configuration and choose from the left navigation "Shipping methods". When you want to use Table rates you can choose one of three conditions avalaible:

• Weight vs. Destination
• Price vs. Destination
• Number of Items vs. Destination