One of my clients recently requested adding any applied coupon codes or gift certificate codes to the invoice printed from Magento.  This is actually a pretty quick and easy change.  Below are the steps required to implement this change in Magento 1.4.1.1.

1. Copy /app/code/core/Mage/Sales/Model/Order/Pdf/Invoice.php to /app/code/local/Mage/Sales/Model/Order/Pdf/Invoice.php
2. Find the line $page = $this->insertTotals($page, $invoice); in the getPdf function.  This was line 107 for me.
3. Add the following:

   /* added by Wright Creative Labs */
   /* print coupon code on invoice */
   if($order->getCouponCode()!=""){
       $this->y -=12;
       $page->drawText('Coupon Used: '.$order->getCouponCode(), 450, $this->y, 'UTF-8');    
   }
   /* print gift certificate code on invoice */
   if($order->getGiftcertCode()!=""){
       $this->y -=12;
       $page->drawText('Coupon Used: '.$order->getGiftcertCode(), 450, $this->y, 'UTF-8');    
   }

4. Save.
5. That's it!  Go to the backend to test it out... Sales > Invoices and then try to print an invoice with a coupon code or gift certificate.

Beanstalk is my latest love. So easy to setup and use, even to a subversion newbie.  Beanstalk allows designers and developers to store source code, track changes, and collaborate with team.  Plus, you can setup multiple deployment environments for each repository to automate the process of deploying changes to your Staging and Production environments. 

In my case, I keep my development environment on my laptop.  I also have setup two branches - staging and production.  The staging branch is setup in Beanstalk to automatically deploy to the Staging server when I perform an svn commit.  The production environment is similarly setup.  I found this article on deployment best practices helpful - http://blog.beanstalkapp.com/post/754555821.

I use Versions, a subversion client for Mac, on my laptop.  I have bookmarks to my Beanstalk repositories and have the project trunk and branches checked out locally.  When I am ready to deploy to Staging, I merge the trunk and staging branch, then commit the changes to staging branch. Here are the steps to merge the changes in the development environment (trunk) to the staging branch:

1. In the terminal, go to the staging branch directory.
   

   cd /Users/myuser/Zend/workspaces/DefaultWorkspace7/myproject-branches/staging

2. Merge changes from the trunk into the staging branch.  E.g.
   

   svn merge /Users/myuser/Zend/workspaces/DefaultWorkspace7/myproject-trunk

3. When you are ready to deploy, go back to Versions and commit the staging branch.  The deployment will be added to Beanstalk's deployment queue. You can view the status of the deployment by logging into Beanstalk, going to the repository, and viewing the Deployments tab.
4. If you get errors from Beanstalk about how a file or folder cannot be created, you may need to update permissions on your server before deployment so that all of the files/directories can be written.  You can switch the permissions back to normal afterwards.

Here are a collection of Linux commands that I frequently use when managing my servers and Magento projects.  Enjoy!

Create a compressed file

Usage: tar -cvxf [filename.tar.gz] [location]

Example:

tar -cvxf myfiles.tar.gz *

Create a MySQL database dump

Usage:  mysqldump -h DBHOST -u DBUSER -pDBPASS DBNAME > data.sql

Example:

mysqldump -h localhost -u mysqlusr -pmypassword mydatabase > mydatabase.sql

Import a MySQL database dump into a database

Usage:  mysql -h DBHOST -u DBUSER -pDBPASS DBNAME < backup/data.sql

Example:

mysql -h localhost -u newdbuser -pnewdbpassword newdatabasename < "/path/to/my/database/dump/mydatabase.sql"

Open permissions for Magento Connect

This example is for PHP running as an Apache module (mod_php, DSO).  First navigate to your root magento directory.

find . -type d -exec chmod 777 {} \;
chmod 666 downloader/config.ini
chmod 777 downloader/pearlib/download/package.xml

If you still get errors, try deleting downloader/pearlib/pear.ini.

Reset Magento permissions

find . -type f -exec chmod 644 {} ;
find . -type d -exec chmod 755 {} ;
chmod o+w var var/.htaccess includes includes/config.php app/etc sitemap/sitemap.xml
chmod 550 pear
chmod -R o+w media

Find recently modified files

Usage:  find /path/to/search -type f -mtime -DAYS -print

Example to find files changed in the last 14 days:

find /home/mysite/public_html -type f -mtime -14 -print

Recursively delete all .svn directories

find /path/to/search -name .svn -print0 | xargs -0 rm -rf

Search for text in files (grep)

Usage:  grep [options] [search phrase] [destination]

Example:

grep -R "*wcltestserver2.us*"

After migrating a Magento store to a new server, an exception stating "Wrong Order Id" followed by the Order Id was showing up in the logs.  The store is using Paypal Website Payments Pro and Magento is version 1.4.1.1. 

I found the lines of code in app/code/core/Mage/Paypal/Model/Ipn.php that generate the error being logged:

    protected function _getOrder()
    {
        if (empty($this->_order)) {
            // get proper order
            $id = $this->_request['invoice'];
            $this->_order = Mage::getModel('sales/order')->loadByIncrementId($id);
            if (!$this->_order->getId()) {
                throw new Exception(sprintf('Wrong order ID: "%s".', $id));
            }
    ...

This code appears to first try and look up the order id by getting the invoice number.  In the case of my store, the invoice number and order number are not the same.  On this hunch however, I reset the invoice number to be in sync with the order number.  This was done by editing the eav_entity_store table, which stores the last id number for the orders and invoices.  I raised the increment_last_id value for the invoice (entity_type 16) to be the same as that for the order (entity_type 11).  Note that the entity types are defined in the eav_entity_type table.  Look there if you are not sure which row to change.

After this change, I placed an order and presto... no more "Wrong Order ID" errors!

Update:

I spoke to soon.  Each time I apply this fix the error does not appear for a while.  But it always pops back up again, I presume as soon as the Order Id and Invoice Id get out of sync.  The error is logged, but does not seem to be causing any other problems, so for now I'm planning to leave it be. I'll post again if I find out more!