Magento_Cms · Magento 2.4.9

cms_block_load_after

Magento 2 event dispatched from Magento_Cms. Observers bound to this event run whenever the code path that dispatches it executes.

Dispatch location(s)

Every place in Magento 2 core where cms_block_load_after is fired. Open the file in your local Magento source to see the event arguments passed alongside the name.

vendor/magento/module-cms/Model/Block.php line 50

vendor/magento/framework/Model/AbstractModel.php line 606

Observer skeleton

Paste into your module's etc/events.xml + create the matching Observer class. Adjust the vendor/module namespace to yours.

1. etc/events.xml

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:framework:Event/etc/events.xsd">
    <event name="cms_block_load_after">
        <observer name="vendor_module_cms_block_load_after"
                  instance="Vendor\Module\Observer\CmsBlockLoadAfter"/>
    </event>
</config>

2. Observer class

<?php
declare(strict_types=1);

namespace Vendor\Module\Observer;

use Magento\Framework\Event\Observer;
use Magento\Framework\Event\ObserverInterface;

class CmsBlockLoadAfter implements ObserverInterface
{
    public function execute(Observer $observer): void
    {
        $event = $observer->getEvent();

        // Read whatever payload this event carries. Check the
        // dispatch() call in core to see the exact keys.
        // Example: $product = $event->getProduct();

        // Your observer logic here.
    }
}

Need the full module scaffolded around this observer? Module Generator wires the events.xml, observer class, and module registration for you.