-
Notifications
You must be signed in to change notification settings - Fork 715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smarty Errors #308
Comments
What is the setting of Smarty::$compile_check? As last test install the master branch version because a couple of bug fixes. |
Hi @uwetews, $compile_check is set to true. No time change in my system. Investigating further more I realized the following: 1- Create a tpl with "blah blah" Looks like if there was a "touch" on the compiled template. The header of the compiled template is:
While the stat of the file is:
If I fix the syntax error, it will re-compile the tpl and everything works and the header of the compiled template is now:
This is driving me mad. Any hints ? |
…as not restored on compilation error #308
It was indeed a bug. |
I'm glad it is fixed now! |
I'n glad it's fixed! Later! El Thursday, October 20, 2016, uwetews notifications@github.com escribió:
[image: Solcre Technology Solutions] Matias Fuster Coll |
Hi, we have been using smarty for about 9 years, and when we had errors on a tpl smarty usually raised an fatal error indicating the problem. Now we updated to latest version and when an error is found, smarty renders the last working version for that tpl from cache (templates_c).
How can we get the old behavior?
Steps to reproduce:
1- Create a tpl with "blah blah"
2- Render the tpl
3- Make a change on the tpl with a syntax error.
4- Try to render de tpl and you will see that it is rendering: "blah blah".
The text was updated successfully, but these errors were encountered: