-
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
Function defined in subtemplate is no longer defined #301
Comments
Template function processing has been update in the master branch today . |
Finally was able to set up a test for this and it seems to work in |
I spoke too soon. Not sure why, but it's throwing that error again. Why it didn't fail on my Dev is still a mystery. But -34 didn't fix it after all The line has changed from 56 to 49 |
You say it does run on your DEV system but not on other installation. |
I don't think that's the issue. We use DevOps to release our code, and when we do a new release it creates a new cache directory. I did a release today and confirmed there's no cache in there afterward. |
Could you please send me all templates source of a page which does fail (private uwe.tews@googlemail.com) |
I don't think it would help unfortunately. I've tried to mock something up internally that emulates what's going on here in a simpler way, but I can't get it to fail at all outside this one script. The frontend controller is also very complex, so just getting data back into it that causes this failure has been a pain (and it's a cron job so mocking it into Apache for easier execution has been another pain). I have finally gotten this script to reliably fail on my Dev server and here's what I've found in back tracing this so far.
Here's the backtrace I got from the Exception Smarty throws, if that helps
I'm still digging into this to narrow it down. This is all I have thus far |
Which CMS system is it? Where can I find the code? |
From your dump I can see that the CMS is calling a lot of templates by fetch(). The master branch is now updated with some improvement that may have solved also your problems. |
This is a custom CMS we've written in-house. I emailed you the templates in question. I've reached the end of my rope. |
…een Smarty::fetch() and Smarty::display() calls #301
Finally found the bug. |
Yep, confirmed fixed. Thanks a ton! |
I've pretty much run out of issues on my end to explain this so I'm starting to think it's the migration to 3.1.30 that's causing this. It's my only Smarty migration issue thus far
I have a template that loads some subtemplates to generate HTML for an email. One of them defines a function
{function name="email_button"}Some HTML{/function}
The master template includes it first
{include file="./shared_functions.tpl"}
After the 3.1.30 upgrade it fails
I'm still trying to narrow down where in Smarty it does this but I was able to get it to do it for my development environment and doing a pull of everything in Smarty master doesn't fix it.
The text was updated successfully, but these errors were encountered: