Smarty

You may also be right about bbb being a valid host. Most regex take into account that bbb part could be an IP address so it's only conceivable that any string that's a valid host name is allowed.

N ...

Thank you mohrt, for tackling the problem

I got the code from CVS

// regex taken from Jeffrey Freidl e-mail validation example
// http://public.yahoo.com/~jfriedl/regex/email-op ...

The code (snippet from Smarty Validate below) that checks email addresses is pretty good but if fails to detect that foo:bar@xxx.com is not valid email address. Well, at least qmail fails to deliver t ...

Notice that simply loading (not evaluating) also doesn't work in the following case:

{$smarty.config.$my_var.x.y}

But it compiles with associative arrays of less dimensions, such as

{$smarty. ...

mohrt

Of the alternatives you mentioned:

1-Not my favorite, having to load config file et al in form validation code seems like a way to get into trouble down the line, and make for some unreada ...

Not sure what you meant by needing full template functionality inside the error message. All I need to do is to be able to evaluate a config entry (aka) a specific error message. Note that entries tha ...

Well, if it makes sense to you guys, I would put it as a feature request.

I'm surprised that nobody needs (or has asked) for such things. Perhaps my usage pattern is a bit odd.

Anyhow, here is ...

I wonder if my question isn't clear enogh, since nobody has responded.

In a nutshell, {$smarty.config.foo} is equivalent to {#foo#}. Q:/ Is there a {$smarty.config.???} equivalente to {eval var=#f ...

Here is what the docs says:

{$smarty} variable can be used to refer to loaded config variables. {$smarty.config.foo} is a synonym for {#foo#}. See the section on con ...

I'm migrating to 2.6.1 today (from 2.5) and must say that triple quote parsing has been a royal pain.

I hit the comment bug plus another more difficult to track. For example, when the """" is place ...

simply put a "$smarty =& $this" before
require_once $this->_get_plugin_filepath('modifier', 'date_format');

I had already hacked my code in the same way to move on on my upgrade. It defin ...

i never knew, that the former syntax was supported.

Well, I'm not implying that it must be supported or that it was supported, I simply used to have it like that (sometimes) for no particular reaso ...

Continuing my findings/woes with my upgrade I'd like to mention that in conf files one could have had

my_var=
""""
a multi
line value
""""

But it no longer works, the parser won't like it a ...

Another, unrelated isssue, is that in the process of converting some of my {insert} to regiter_function with cacheability set to false, I see something that appears to be debug information in the gene ...

Today I decided to upgrade to 2.6. Here is my first road block

In 2.5+ I had a modifier function registered as member function

$this->register_modifier("my_mod", array(&$this, "my_modifier_fu ...