Smarty

We worked around it for now by using calls like {$_noPrint=functionCall()}

but I definitely think your flag idea is a more elegant solution Smile

I will keep an eye out for when that makes it in.

It's been a while but we ran into this again when a slightly older project showed a couple of bugs. We decided not to override the noprint modifier because we really expected that this would be fixed ...

Hi,

Today I was working on a template and it kept throwing a fatal error and I had an idea for how to get more accurate information about the actual template file causing the problem, instead of se ...

Namespaces will become more and more prevalent in PHP code. In essence, they are little more than a "grouping" mechanism for classes that is replacing the older workaround of a project name ...

Thanks,

I will probably try overriding the core modifier with my own... at the moment I just removed the modifier compiler version and replaced with with the RC3 version of the plugin.

I will ...

We often call functions and class methods directly from the templates. Many times those calls return a value such as true/false or an integer or some other value that we don't actually want to have re ...

Thanks,

That worked well but definitely feels hackish since it involves modifying a file in a stable release of software.

Is there any way to set up the new modifiercompiler plugins to handle PH ...

Hi,

I finally got a chance to try out Smarty 3.0.4 and 3.0.5 after having used RC3 since the day it was released.

It appears that modifiers no longer compile the way they did in RC3 and earlier ...

I would say that the parenthetical syntax would be nice to support, but should not be required since one goal is backwards compatibility with Smarty 2 templates.

This error is present in many of our templates. However, I think that being able to drop {literal} is such a bonus that we'll just fix the templates.

I went in an stripped out the excess code inserted within the while() loop that makes up the block in the compiled templates (both Smarty 3 and Smarty 2).

I see now that they are logically identica ...

hmmm....

I can accept that it is not designed for what I want it to do. Smile

I was trying to reduce the amount of template code required to do a permissions check and run different code dependin ...

It is possible that my understanding of block function behavior is off but I have a feeling there is a bug in the block function handling in the compiler.

Here is the behavior that currently happen ...

Currently I have not found a way to set a new value for an object property when working in a Smarty template file.

I was hoping something like the following would be possible:

{$myobj->t ...

In the version of Smarty 3 Beta (Smarty-3.0-b1) released on Oct. 31st (the download link on the downloads page - not in SVN) the Smarty.class.php script has the following on line 95:

spl_autoload ...