{"id":80,"date":"2024-10-03T12:35:55","date_gmt":"2024-10-03T16:35:55","guid":{"rendered":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/?page_id=80"},"modified":"2025-10-20T14:23:12","modified_gmt":"2025-10-20T18:23:12","slug":"render","status":"publish","type":"page","link":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/handbook\/wp-core\/block-architecture\/render\/","title":{"rendered":"render.php (Frontend Template)"},"content":{"rendered":"\n

The render.php<\/code> file (or any other file defined in the render<\/code><\/a> property of block.json<\/code>) defines the server-side process that returns the markup for the block when there is a request from the front end. If defined, this file will take precedence over other ways to render the block\u2019s markup on the front end.<\/p>\n\n\n\n

Note: render.php<\/code> is only used by Dynamic Blocks. None of the block\u2019s markup is saved to the database. Instead, its attributes are written inside the block indicator comment. The render method is called to create the block\u2019s markup whenever a front-end user visits the page. This differs from Static Blocks, who store their entire markup in the database.<\/p>\n\n\n\n

These render methods automatically receive attribute and inner content information. They can also get additional required dynamic site information \u2013 post lists, comments, taxonomy information, etc.<\/p>\n\n\n\n

Alternatively, the block registration function<\/a> includes a render_callback argument. As the recommended practice is to register a block type using the metadata stored in the block.json<\/code> file, we will not cover this method.<\/p>\n\n\n\n

Example<\/h2>\n\n\n
\n\tError: Unable to fetch https:\/\/raw.githubusercontent.com\/bu-ist\/r3-id-documentation\/refs\/heads\/develop\/src\/blocks\/tutorial-01\/render.php<\/article>\n\n\n\n

Overriding<\/h2>\n\n\n\n

The output of a block can be modified with php<\/code> using either the render_block_{$this->name}<\/a><\/code> or render_block<\/a><\/code> filters. <\/p>\n\n\n\n

@todo embed an example<\/p>\n\n\n\n

Further Reading<\/h3>\n\n\n\n