When Blade compiles a template it writes a .php file on disk. However, if opcode caching is enabled and we are overwriting an existing compiled template PHP will cache the contents of the previous incarnation of the view template, potentially leading to hard to identify problems.
The solution is to bust the opcode cache as soon as we write the template file, forcing PHP to read the compiled template afresh right away.
When Blade compiles a template it writes a .php file on disk. However, if opcode caching is enabled and we are overwriting an existing compiled template PHP will cache the contents of the previous incarnation of the view template, potentially leading to hard to identify problems.
The solution is to bust the opcode cache as soon as we write the template file, forcing PHP to read the compiled template afresh right away.