So shortly after I tweeted this to Matthias I went on radio silence. I hope you felt the suspense as you've awaited this answer for a couple weeks now.
What I mean by "I do these in a queue" is in direct response to:
Certain observers like enterprise_cms and enterprise_search for the event store_delete_after are defined in the adminhtml area so they won't get executed. The store view deletion won't be handled like a deletion executed in the backend.
Queue Method:
When I know that there are certain events that won't fire in the correct context (mostly for EE, but may apply in other contexts) I typically shove the deletion out to a queue so that it will run in the context that it needs to.
In other words, create a queue table (or queue/topic in RabbitMQ, etc.) that would contain details of the transaction and the event hooks that it should be listening to. This can be as elegant or as simplistic as you want it to be. Here's a basic
$queue = Mage::getModel('yourcompany/queue_job')
->setJobType('delete')
->setEntityType('core/store')
->setEntityId(12)
->setDispatchEvent('store_delete')
->setDispatchEventDataKey('store')
->save();
And then work the queue later in a CRON, where you now have control over which store is "running" (aka you're just running it as if it were the admin, store 0):
foreach(Mage::getModel('yourcompany/queue_job')->getCollection() as $job){
if($job->getJobType()=='delete'){
$model = Mage::getModel($this->getEntityType())->load($this->getEntityId());
if ($model->getId() && $model->isCanDelete()) {
$model->delete();
Mage::dispatchEvent($job->getDispatchEvent(), array($job->setDispatchEventDataKey() => $model));
}
}
}
Obviously if you were getting fancy you wrap in a try/catch and wrap in a transaction. I think you get the gist.
This is feasibly the only way to control the context in which the event fires.
Tandem event method:
You can fire the "adminhtml" method yourself manually - Alan gives a pretty decent explanation of what you would do to affect that, but essentially it's the same as this:
#File: app/code/core/Mage/Adminhtml/controllers/CustomerController.php
public function saveAction()
{
//...
$customer->save();
//...
Mage::dispatchEvent('adminhtml_customer_prepare_save', array(
'customer' => $customer,
'request' => $this->getRequest()
));
//..
}
The admin version of the customer save calls the regular model save and dispatches the adminhtml event afterward. You could do the reverse of this in an observer yourself if you so desired.
Best Answer
Try this
See function definition of
saveConfig()at\app\code\core\Mage\Core\Model\Config.php