Smarty Forum Index Smarty
WARNING: All discussion is moving to https://reddit.com/r/smarty, please go there! This forum will be closing soon.

Search found 75 matches
Smarty Forum Index
Author Message
  Topic: Smarty 3.0 Alpha 1: Proof of Concept
c960657

Replies: 93
Views: 250352

PostForum: Smarty 3   Posted: Mon Feb 16, 2009 10:06 pm   Subject: Smarty 3.0 Alpha 1: Proof of Concept
Perhaps I am joining the discussion a bit late, but hopefully not too late Smile I have not studied Smarty3 closely yet, so my comments are mostly based on experiences with Smarty2.

It would be conve ...
  Topic: Variable scope with multiple fetch() calls
c960657

Replies: 2
Views: 7738

PostForum: General   Posted: Thu Feb 28, 2008 12:40 pm   Subject: Variable scope with multiple fetch() calls
Ok, thanks Smile
  Topic: Variable scope with multiple fetch() calls
c960657

Replies: 2
Views: 7738

PostForum: General   Posted: Thu Feb 28, 2008 11:33 am   Subject: Variable scope with multiple fetch() calls
When including a template using {include file="foo.tpl"}, variables assigned inside foo.tpl using {assign var="foobar" value=...} have their own scope and does not affect the varia ...
  Topic: literal
c960657

Replies: 20
Views: 42487

PostForum: Bugs   Posted: Wed Feb 13, 2008 5:55 pm   Subject: literal
Hmm, problems Crying or Very sad The patched version no longer allows {$foo/$bar->baz()}.

We are now testing only optimization #1.
  Topic: literal
c960657

Replies: 20
Views: 42487

PostForum: Bugs   Posted: Tue Nov 20, 2007 6:32 pm   Subject: literal
So far we haven't had any problems.
Still no problems Smile
  Topic: literal
c960657

Replies: 20
Views: 42487

PostForum: Bugs   Posted: Wed Aug 08, 2007 4:06 pm   Subject: literal
With some additional testing, I think this could be recommended for cvs.
So far we haven't had any problems.
  Topic: literal
c960657

Replies: 20
Views: 42487

PostForum: Bugs   Posted: Wed Jul 25, 2007 6:44 pm   Subject: literal
I assume that this doesn't break registered objects?
I doesn't look like it (I don't use registered objects, but a small test appears to work). I expect these to be handled by _reg_obj_regexp.
  Topic: literal
c960657

Replies: 20
Views: 42487

PostForum: Bugs   Posted: Wed Jul 25, 2007 3:01 pm   Subject: literal
Good ideas are very much welcome.
I think I have found two possible optimizations.

_obj_start_regexp currently allows mathematical expressions before the ->, e.g. strings like $foo+123->abc. ...
  Topic: literal
c960657

Replies: 20
Views: 42487

PostForum: Bugs   Posted: Tue Jul 24, 2007 7:55 am   Subject: literal
Good ideas are very much welcome. Without them, I'm personally still WNF on this.
I understand that.

It is my impression that the default limit in PHP 5.2 is just lower than in previous versions ( ...
  Topic: literal
c960657

Replies: 20
Views: 42487

PostForum: Bugs   Posted: Mon Jul 23, 2007 12:25 pm   Subject: literal
BTW, I also get the error with simple expressions like this:
{$byteCount/1024/1024/1024}
  Topic: literal
c960657

Replies: 20
Views: 42487

PostForum: Bugs   Posted: Mon Jul 23, 2007 12:23 pm   Subject: literal
I was just about to file a bug report when I found this thread that looks like the same issue. FWIW I will post what I have already written in case it may be useful to someone. Here goes

---

The ...
  Topic: Access current resource name in postfilter
c960657

Replies: 3
Views: 6223

PostForum: General   Posted: Tue Feb 13, 2007 1:49 pm   Subject: Access current resource name in postfilter
ugly, but better than nothing - you can use some of smarty's internals:
I already tried that, but $params['resource_type'] is always "file" inside the postfilter. The is because that $compi ...
  Topic: Access current resource name in postfilter
c960657

Replies: 3
Views: 6223

PostForum: General   Posted: Mon Feb 12, 2007 12:16 pm   Subject: Access current resource name in postfilter
I am looking for a way to get the name of the resouce being compiled in my postfilter.

I can use $smarty->_current_file to get the resource name, but don't know how to find the resource type whe ...
  Topic: Warning: filemtime($compile_path): Stat failed
c960657

Replies: 24
Views: 57777

PostForum: Bugs   Posted: Mon Nov 20, 2006 9:02 pm   Subject: Warning: filemtime($compile_path): Stat failed
Can anyone add any testing feedback here?
I have been using this on production servers since 8 November. So far no problems here.
  Topic: Warning: filemtime($compile_path): Stat failed
c960657

Replies: 24
Views: 57777

PostForum: Bugs   Posted: Mon Nov 06, 2006 10:23 pm   Subject: Warning: filemtime($compile_path): Stat failed
Can you give some commentary? I'm not sure how that will help anything. In fact, it looks like it merely makes the windows issue worse by making it less performant (since it will eventually do two att ...
 
Page 1 of 5 Goto page 1, 2, 3, 4, 5  Next
All times are GMT
Jump to:  


Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP