It looks like this block directly flushes the output.
What’s the practical use of this block?
How can I use it?
Did anybody ever use it?
It looks like this block directly flushes the output. What’s the practical use of
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It looks like this block directly flushes the output.
What’s the practical use of this block?
How can I use it?
Did anybody ever use it?
It’s not used by the core (afaik). It turns off output buffering, so the rendered output would be sent immediately. The only block where it would kind of work would be the root block, otherwise the nested
core/flushblock and all following blocks would be rendered before the containing outer blocks.I can’t think of a sensible use case. Since the front controller is responsible for sending the output to the client, the
core/flushblock breaks his process. In the worst case it could lead to PHP Headers already sent notices.I don’t know, but my guess is it is a relict from the pre-release days of Magento, where the whole rendering system wasn’t finalized yet. Probably seemed like a good idea at the time.
Maybe someone who was with the core team at the time can enlighten us about the history.