Static block not visible under admin panel->cms->static blocks

Question

I want to add a static block programmatically. The way I'm trying to do that is next:

• I created file data-upgrade-1.0.0-1.0.1.php (there were none other files except data-install...) inside setup directory app\code\local\[theme]\Customizations\data\[theme]​_customizations_setup
• Added this code:

  $stores = Mage::getModel('core/store')->getCollection()
      ->addFieldToFilter('store_id', array('gt' => 0))->getAllIds();
  
  foreach ($stores as $storeId) {
      $block = Mage::getModel('cms/block')
          ->setIsActive(1)
          ->setTitle('Test CMS Static Block')
          ->setIdentifier('cms_block_test')
          ->setContent('<!-- edit me -->')
          ->setStores(array($storeId))
          ->save();
  }
  

• After that, I changed config.xml version 1.0.1
• Cleared all Magento cache

But my static block won't show under CMS > Static Blocks.
Am I missing something?

Answer 1

All Cms blocks are linked to one or more stores. Perhaps setting the store ID's will help:

->setStores(array($storeId))

Normally I build the code like this in my install/upgrade scripts:

$stores = Mage::getModel('core/store')->getCollection()
    ->addFieldToFilter('store_id', array('gt' => 0))->getAllIds();

foreach ($stores as $storeId) {
    // Block creation code goes here
}

Was the block even added to the database? If it was, try to find the differences between the records to a block that you have added through the admin interface.

If not, then your script has probably not even run. You could add a log line somewhere (Mage::log('Data upgrade @ ' . __FILE__)) and see if it has appeared in your var/log/system.log.

Also check if the version of your module isn't yet at "1.0.1" by checking the version in the core_resource table.

If the version in the core_resource table is "1.0.1" or higher you could do two things

• Update the record in the core_resource table to "1.0.0" version (don't know what the side effects might be)
• Update your script and the config.xml to be version "1.0.3" so that Magento sees a newer version of the module and kicks off the upgrade