Turboweb Developer Blog

One of our clients noticed that checking the save shipping address in the magento checkout does not save that address to the customeres addresses.
After some investigation I can confirm this is a 1.4.2.0 bug, but have not seen any solutions on the web, so here is my fix:

You should override the App/Code/Core/Mage/Checkout/Model/Type/Onepage.php class in the usual manner, and override the saveShipping method, to be like:

public function saveShipping($data, $customerAddressId)
{
    if (empty($data)) {
        return array('error' => -1, 'message' => $this->_helper->__('Invalid data.'));
    }
    $address = $this->getQuote()->getShippingAddress();
 
    if (!empty($customerAddressId)) {
       $customerAddress = Mage::getModel('customer/address')->load($customerAddressId);
        if ($customerAddress->getId()) {
             if ($customerAddress->getCustomerId() != $this->getQuote()->getCustomerId()) {
                 return array('error' => 1,
                     'message' => $this->_helper->__('Customer Address is not valid.')
                 );
             }
             $address->importCustomerAddress($customerAddress);
        }
    } else {
        /* @var $addressForm Mage_Customer_Model_Form */
        $addressForm    = Mage::getModel('customer/form'); 
        $addressForm->setFormCode('customer_address_edit')
            ->setEntity($address)
            ->setEntityType('customer_address')
            ->setIsAjaxRequest(Mage::app()->getRequest()->isAjax());
        // emulate request object
        $addressData    = $addressForm->extractData($addressForm->prepareRequest($data));
        $addressErrors  = $addressForm->validateData($addressData);
        if ($addressErrors !== true) {
            return array('error' => 1, 'message' => $addressErrors);
        }
        $addressForm->compactData($addressData);
         //the next 3 lines are the fix!!!
        if (!empty($data['save_in_address_book'])) {
             $address->setSaveInAddressBook(1);
        }
    }
 
    $address->implodeStreetAddress();
    $address->setCollectShippingRates(true);
 
    if (($validateRes = $address->validate())!==true) {
        return array('error' => 1, 'message' => $validateRes);
    }
 
     $this->getQuote()->collectTotals()->save();
 
    $this->getCheckout()
        ->setStepData('shipping', 'complete', true)
        ->setStepData('shipping_method', 'allow', true);
 
    return array();
}

This now follows a similar logic to the saveBilling address, setting a flag to save the address when the order is saved.

We have a system that populates a Magento installation by reading an external database and creating, updating and deleting products and categories. Recently I had been receiving an obscure message when trying to update categories using the Magento API.

The message was simply: Default Product Listing Sort by not exists on Available Product Listing Sort By

After Googling around I hadn’t turned up much, which forced me into the bowels of Magento. This exception is thrown in the file app/code/core/Mage/Model/Category/Attribute/Backend/Sortby.php on line 81 and 85. This file is responsible for checking that the Sort By method specified for a category is valid.

Default Display Settings for a new cateogry

When you create a category in Magento using the Admin UI, the values in the Display Settings tab of the category as set as per this screenshot (click to enlarge).  The default values are:

• Available Product Listing Sort By = Use All Available Attributes
• Default Product Listing Sort By = Use Config Settings

With this category created, I used the following test script to check to see if I could update the category.  This script simply asks for the information about the category (category 4066 in my case) and attempts to update the category with that information.

<?php
 	define('MAGENTO', getcwd() );
 	define('CATEGORY_ID', 4066 );
	require_once MAGENTO . '/app/Mage.php';
	umask(0);
	Mage::app()->setCurrentStore(Mage_Core_Model_App::ADMIN_STORE_ID);
 
	try
	{ 
		$info = Mage::getModel('catalog/category_api')->info( CATEGORY_ID );
		var_dump( $info );
		Mage::getModel('catalog/category_api')->update( CATEGORY_ID, $info );
 
		echo "\n\nSUCCESS\n\n";
	}
	catch( Exception $e )
	{
		var_dump( $e );
	}
?>

When I ran this with the default settings, I received a “data_invalid” exception, however tweaking it to use any of the values in the select box for the Default Product Listing Sort By resulted in the exception “Default Product Listing Sort by not exists on Available Product Listing Sort By” (tip: it was useful to pipe the output of this script to `less’). I then had a test script that I could use to verify when my problem was fixed.

I then fiddled around with the display settings in Magento (which by the way does not suffer from this problem when saving a category) and found that if I set the Available Product Listing Sort By to anything other than using the tick to use all available attributes, and set the Default Product Listing Sort By to anything other than using the tick to use the Config Settings, then things magically started working.

This eventually led to me reworking a bit of code to include specific values for the available_sort_by and default_sort_by attributes when updating the category. Here’s my bit of code – out of context, but you get the idea.

    $result = $api->update
    (
        $category_id,
        array
        (
            'image' => $image_path,
            'description' => $description,
            'meta_description' => $meta_description,
            'meta_keywords' => $meta_keywords,
            'available_sort_by' => array( 'name' ),
            'default_sort_by' => 'name'
        )
    );

Good luck!

As of Magento 1.4.2.0, the loadParentProductIds() method in the product model has been deprecated and is no longer available.

Here’s an example of it being used:
http://www.magentocommerce.com/boards/viewthread/74229

Prior to Magento 1.4.2.0, this would have worked:

list( $parentId ) = $_product->loadParentProductIds()->getData('parent_product_ids');

After Magento 1.4.2.0, this works:

list( $parentId ) = Mage::getModel( 'catalog/product_type_grouped' )->getParentIdsByChild( $_product->getId() );

Note that the above fetched the parent product ID’s for a grouped product – there are also versions for configurable products in the catalog/product_type_configurable model.

Good luck!

As of Magento 1.4.2.0 the customer model now implements eav from attributes, and a new customer form model. For anyone who has existing custom attributes, or are thinking of making some this will pose new issues in accessing and saving this data.

To implement a custom customer attribute, the sql/[module]_setup install file needs to add the new attribute and then add this attribute to several forms (those that deal with a customer). See below, but these are customer_account_edit, customer_account_create, adminhtml_customer and checkout_register.

Here is an example of an existing custom attributes to add a customer type field:
sql/[module]_setup/mysql4-install-0.1.0.php (for example)

function createCustomAttributes()
{
    $attribs = array(
        'customer' => array(
            'customer_type' => array(
                'type' => 'varchar',
                'label' => 'Customer Type',
                'sort_order' => 5,
                'required' => 0
            ),
        )
    );
 
    $setup = new Mage_Eav_Model_Entity_Setup('core_setup');
 
    foreach( $attribs as $entityName => $attributes )
    {
        foreach( $attributes as $attributeName => $attributeData )
        {
            $setup->addAttribute( $entityName, $attributeName, $attributeData );
        }
    }
}
 
createCustomAttributes();

This code will add the customer attribute ‘customer_type’ to the eav attribute table. Now comes the important difference introduced in Magento 1.4.2.0:

sql/[module]_setup/mysql4-install-0.1.0.php (continues)

//add attributes to new forms model attributes
$eavConfig = Mage::getSingleton('eav/config');
$attributeArray = array('customer_type');
 
//I handle this in an array incase several attributes need adding, depending on your needs.
foreach( $attributeArray as $attrib )
{
    $attribute = $eavConfig->getAttribute('customer', $attrib);
    $attribute->setData('used_in_forms',   array
        (
            'customer_account_edit',
            'customer_account_create',
            'adminhtml_customer',
            'checkout_register'
        )
    );
    $attribute->save();
}

This will add a field to all of the customer forms, and also the onepage checkout if using the user chooses to create a new account during checkout method! (although the latter will require adding to the template… in the format: name=”billing[customer_type]” as the other forms use the form model to generate the HTML fields)

If you are using the registration page, the attribute also needs to be added to the sales_flat_quote table: (in the same file..

$installer->getConnection()->addColumn(
    $installer->getTable('sales_flat_quote'),
    'customer_type',
    'text  NULL  DEFAULT  NULL  AFTER `customer_taxvat`'
);

And you will need to edit the module’s etc file:

<global>
        <fieldsets>
            <customer_account>
                <customer_type>
                    <create>1</create>
                    <update>1</update>
                    <name>1</name>
                    <to_quote>customer_type</to_quote>
                </customer_type>
            </customer_account>
            <checkout_onepage_quote>
                <customer_type>
                    <name>1</name>
                    <to_customer>customer_type</to_customer>
                </customer_type>
            </checkout_onepage_quote>
        </fieldsets>
</global>