Anyway, if you want to know for sure where Magento is writing the log files, put this in a script:

$var_dir = Mage::getModel('core/config')->getVarDir();
echo $var_dir;

In my case, I discovered it was writing the files /tmp/magento/var. When I logged in via SSH as root, sure enough, there were all my missing log files.

I hope this helps someone.

WordPress gives us the ability to do this with a simple:

get_permalink($page_or_post_id)

To do the same from your Magento template file, do this:

Mage::Helper('cms/page')->getPageUrl($page_id)

I was working on a shopping cart migration to Magento Enterprise 1.10.0.2 and migrating customer reviews and ratings. In the source cart, the reviews and ratings are one in the same. The user writes a review, gives it a title, then associates a star rating of 1-5 with the review. Everything is stored in one database table. In Magento, you can have reviews without star ratings and vice versa. The two are separate. I was able to import the reviews from the source cart, but had more difficulty with the ratings.

In Magento, there are 3 default rating options: Price, Quality, and Value. All three need their “Visible In” attribute set to the store view where you want them to appear. Since the source store only had one rating value of 1-5 associated with the product, I took that value and assigned it to all 3 rating options in Magento so that they all averaged out the same.

Here is the code I use to migrate the reviews. This is inside a loop of reviews from the source cart:

// Invoke the Magento environment
require_once 'app/Mage.php';
Mage::app();
 
// Set up your own loop to to go through the reviews from the source cart.
 
// Logic to look up customer that has already been migrated into magento.
// So you have $_customer holding a Mage_Customer_Model_Customer
 
// IMPORTANT: Set up customer session.
// the rating/option model resource checks the customer session to get the customer ID.
$_session = Mage::getSingleton('customer/session')->setCustomer($_customer)->setCustomerAsLoggedIn($_customer);
 
// Add the review
$_review = Mage::getModel('review/review');
    ->setEntityPkValue($_product->getId())
    ->setStatusId($sc_to_mage_review_status[$row_source_review['Status']])
    ->setTitle($row_source_review['Title'])
    ->setDetail($row_source_review['Review'])
    ->setEntityId(1)
    ->setStoreId($store)
    ->setStores(array($store))
    ->setCustomerId($_customer->getId())
    ->setNickname($_customer->getFirstname())
    ->save();
 
// Map your rating_id to your option_id with an array or something
$rating_options = array(
	1 => array(1,2,3,4,5), // <== Look at your database table `rating_option` for these vals
	2 => array(6,7,8,9,10),
	3 => array(11,12,13,14,15)
);
 
// Now save the ratings
foreach($rating_options as $rating_id => $option_ids):
	try {
		$_rating = Mage::getModel('rating/rating')
			->setRatingId($rating_id)
			->setReviewId($_review->getId())
			->addOptionVote($option_ids[$rating_value-1],$_product->getId());
	} catch (Exception $e) {
		die($e->getMessage());
	}
endforeach;

If you execute this, your reviews will save, but your ratings won’t. There is one more thing you need to do in order for them to save. I don’t advocate modifying core files, but in this case, I had to. It was in my dev environment and I only needed to make the change for the purpose of the migration script. Once, finished, I reverted the file back to it’s default version.

Look on line 84 of this file. This is the model resource for the rating/option model in Magento. This is where all the db inserts/updates happen.

app/code/core/Mage/Rating/Model/Mysql4/Rating/Option.php

You need to replace line 84 with this:

if (1 === 1 || $action instanceof Mage_Core_Controller_Front_Action || $action instanceof Mage_Adminhtml_Controller_Action)

This is a conditional check to make sure that the rating update request came from a Magento controller action. Since they don’t, in this case, I have to force the condition to evaluate as true. Maybe there’s a better way to spoof the request, but I don’t know how to do it.

That’s it. You should be good to go. Happy migration!

When Cart A was imported into Cart B, the orders had products that did not yet exist in Cart B.  The programmer responsible for that move didn’t see it necessary to create the missing products in Cart B, so Cart B ended up with around 6,000 orders with no product line items.  In other words, people called in to the client’s customer service and if that customer inquired about one of the aforementioned orders, then the client couldn’t even see what items were ordered.

I was able to achieve a 1-to-1 migration of all data in Cart B to Magento, but that meant I still had the problem of orders with no product line items.

I still had the legacy orders from Cart A in a 15 mb Excel file.  Each line in the Excel file represented one order.  All of the data on one line, fully de-normalized.  Anyway, after writing a script to parse the Excel file, find the missing products, and insert the missing products into Magento, I was ready to attach those products to their respective orders.  Here’s how that’s done.

// Load the order however you wish. I had the $increment_id already.
$order = Mage::getModel('sales/order')->loadByIncrementId($increment_id);
 
$rowTotal = $product->getPrice() * $qty;
$order_item = Mage::getModel('sales/order_item')
	->setStoreId(NULL)
	->setQuoteItemId(NULL)
	->setQuoteParentItemId(NULL)
	->setProductId($product_id)
	->setProductType($product->getTypeId())
	->setQtyBackordered(NULL)
	->setTotalQtyOrdered($qty)
	->setQtyOrdered($qty)
	->setName($product->getName())
	->setSku($product->getSku())
	->setPrice($product->getPrice())
	->setBasePrice($product->getPrice())
	->setOriginalPrice($product->getPrice())
	->setRowTotal($rowTotal)
	->setBaseRowTotal($rowTotal)
	->setOrder($order);
echo "Saving order item...\n";
$order_item->save();

I had tried at first to use the addItem() method on the $order object itself, but calling $order->save() did nothing. No error was thrown either.  I didn’t look into it much further, but this might be due to something in the Mage core code that prevents data from being saved if the request isn’t of type Front_Controller_Action.  That’s happened to me before when attempting to save product ratings programmatically.

Hope this helps people out there!

There are two fixes you need to apply.

The first fix

The first fixes problems if you’re getting errors like:

PHP Notice: Undefined index TM_PROJECT_FILEPATH
PHP Notice: Undefined index TM_DIRECTORY

You need to alter your /private/etc/php.ini file. If you don’t have one, just copy the /private/etc/php.ini.default file to /private/etc/php.ini. Look for this line:

variables_order = “GPCS”

Change it to:

variables_order = “GPCSE”

The second fix

Snow Leopard ships with PHP 5.3, which, in its default configuration, doesn’t recognize the $_ENV superglobal.  You have to call getenv() instead.  Since the FTP/SSH bundle relies heavily on the $_ENV variable, it breaks under Snow Leopard.  Luckily, there’s an easy fix.

The Solution

Open up TextMate and open the following folder:

/Users/your_username/Library/Application Support/TextMate/Pristine Copy/Bundles/FTP:SSH.tmbundle/

Use shift+cmd+f to do a global find/replace. For find, enter this:

\$_ENV\['([A-Z_]+)'\]

For replace, enter this:

getenv('$1')

Make sure you check the “Regular expression” box and click Find and then Replace All.

That’s it.  The bundle should start working properly.