So in an effort to save myself (and perhaps others) the trouble in the future, I wanted to quickly lay out how I got it working.

Setup

Perhaps one of the most important parts of making this sort of update easy is modifying your migration scripts to use the right model for setup. In this case, I used the setup model included with the RMA module itself — Enterprise_Rma_Model_Resource_Setup. The following example assumes you have your own RMA module in the “namespace” namespace.

config.xml:

<resources>
    <namespace_rma_setup>
        <setup>
            <module>Namespace_Rma</module>
            <class>Enterprise_Rma_Model_Resource_Setup</class>
        </setup>
        <connection>
            <use>core_setup</use>
        </connection>
    </namespace_rma_setup>
</resources>

The Install Script

Now we’re going to delete the old options and then add the new ones. Note how this process is wrapped in a database transaction, just in case. Moreover, look at the highlighted lines. On line 29, you’ll notice that the setup model we’ve chosen allows us to use the addAttributeOption method (as well as various other useful methods), which lets us easily delete the existing options.

Next, on line 43 the setup script also gives us the getDefaultEntities method which returns the array representation of the attribute structure for RMA’s. From this, we can fill in the blanks that Magento expects to be there for our option array. Then on line 53, we merge our arrays together to feed Magento what it needs to complete the deletion of the previous options and to add the new options in the order we give it.

/** @var $installer Enterprise_Rma_Model_Resource_Setup */
$installer = $this;

/** @var $connection Varien_Db_Adapter_Pdo_Mysql */
$connection = $installer->getConnection();

$installer->startSetup();

try {
    $connection->beginTransaction();

    // Delete existing options

    /** @var $rmaItems Enterprise_Rma_Model_Item_Attribute */
    $rmaItems = Mage::getModel('enterprise_rma/item_attribute');

    $reason = $rmaItems->loadByCode('rma_item', 'reason');

    $selectOptions = $reason->getFrontend()->getSelectOptions();
    $optionsDelete = array();

    foreach($selectOptions as $option) {
        if ($option['value'] != "") {
            $optionsDelete['delete'][$option['value']] = true;
            $optionsDelete['value'][$option['value']] = true;
        }
    }

    $installer->addAttributeOption($optionsDelete);

    // Add new options

    $optionsArray = array(
        'Wrong size',
        'Wrong item',
        'Does not fit',
        'Wrong SKU',
        'Warranty Claim',
        'Did not order',
        'Exchange',
    );

    $defaultEntities = $installer->getDefaultEntities();

    $reason = $defaultEntities['rma_item']['attributes']['reason'];
    $reasonOptions = array(
        'option' => array(
            'values' => $optionsArray,
            'delete' => $optionsDelete,
        ),
    );

    $reasonAttribute = array_merge($reason, $reasonOptions);

    $installer->addAttribute('rma_item', 'reason', $reasonAttribute);

    $connection->commit();

} catch (Exception $e) {
    $connection->rollBack();
    Mage::logException($e);
}

$installer->endSetup();

Update:

I uninstalled the app as I didn’t know why I was mindlessly checking into places. Interesting, but a time waster for sure.

Trying out path.com instead!

As it turns out, renaming directories in git isn’t so easy. So to help other people avoid wasting their time like I did, I thought I’d post the workaround.

Normally, you’d think that to rename a directory called ‘FooBar’ to ‘Foobar’ you’d just issue commands like so:

git mv FooBar Foobar
git add -A Foobar
git commit -am "Your message"

But that is not the case. Instead, you would do this:

mv FooBar Sometemporaryname
git add -A Sometemporaryname
git commit -am "Your message here"
mv Sometemporaryname Foobar
git add -A Foobar
git commit -am "Second message here"

Not very intuitive but it gets the job done. Hope it saves someone some time.

So what will I focus on this time around?

• Minimalism and simplicity
• More programming / engineering content
• This blog as opposed to others (time to delete and forget)

Feel free to read about me or contact me.

That is all.