Magento Shiksha

Controller vs Block in Magento 2

What is a Controller in Magento 2?

A Controller in Magento 2 is responsible for handling HTTP requests and returning the appropriate response. It acts as the entry point of the application when a user accesses a specific route.

Controllers process incoming requests, interact with models or services if required, and determine which result type should be returned (page, JSON, redirect, or raw response).

Key Responsibilities of a Controller

  • Handle HTTP requests from the browser.
  • Process request parameters.
  • Execute application logic or call services.
  • Return an appropriate response type.

Example: Create a Controller

Suppose we want to create a custom frontend page accessible through a route.

1. Create routes.xml

(File: app/code/VendorName/ModuleName/etc/frontend/routes.xml)

2. Create Controller File

(File: app/code/VendorName/ModuleName/Controller/Index/Index.php)

What is a Block in Magento 2?

A Block in Magento 2 is responsible for preparing data that will be displayed in templates (PHTML files). It acts as a bridge between backend logic and the view layer.

Blocks contain presentation logic and helper methods used by templates to render dynamic data.

Key Responsibilities of a Block

  • Provide data to templates.
  • Interact with models or services to fetch data.
  • Contain presentation-related logic.
  • Expose methods used inside PHTML templates.

Example: Create a Block

Suppose we want to pass custom data from the backend to a template.

1. Create Block Class

(File: app/code/VendorName/ModuleName/Block/Test.php)

2. Use Block in Layout XML

(File: app/code/VendorName/ModuleName/view/frontend/layout/customroute_index_index.xml)

3. Create Template File

(File: app/code/VendorName/ModuleName/view/frontend/templates/test.phtml)

How Controller and Block Work Together

When a user visits a Magento page, the request follows the MVC pattern.

  1. The controller receives the HTTP request.
  2. The controller returns a page result.
  3. The layout XML defines blocks.
  4. Blocks prepare the required data.
  5. PHTML templates render the final HTML output.

Main Differences Between Controller and Block

  • Controller: Handles HTTP requests and responses.
  • Block: Prepares data for templates.
  • Controller: Part of the application flow.
  • Block: Part of the presentation layer.
  • Controller: Executes when a route is accessed.
  • Block: Executes during page rendering.

Best Practice

Controllers should remain lightweight and only manage request flow. Business logic should be implemented in service classes or models, while presentation logic should remain in blocks.

This separation ensures better maintainability, scalability, and adherence to Magento’s architecture.