Thread: [htmltmpl] "Bad file descriptor" while parameter substituting
Brought to you by:
samtregar
From: Petrov D. <el...@ne...> - 2005-10-14 15:58:53
|
Hi, all! I gets subj error while substitute parameters for simple template. $tmpl->param({'NEWS' => [{'created' => '2005-10-15', 'text' => 'sdadsdsdsdw1re32fqr'}]}); Template is: <table> <TMPL_LOOP name="NEWS"><tr> <td> <b><TMPL_VAR name="created"></b><br> <pre><TMPL_VAR name="text"></pre> </td> </tr></TMPL_LOOP> </table> Can anybody help me? |
From: Roger B. W. <ro...@fi...> - 2005-10-14 16:08:50
|
On Fri, Oct 14, 2005 at 07:58:44PM +0400, Petrov Dmithriy wrote: >Hi, all! >I gets subj error while substitute parameters for simple template. >$tmpl->param({'NEWS' => [{'created' => '2005-10-15', 'text' => >'sdadsdsdsdw1re32fqr'}]}); You're passing a hashref to param(). Try: $tmpl->param('NEWS' => [{'created' => '2005-10-15', 'text' => 'sdadsdsdsdw1re32fqr'}]); Roger |
From: Petrov D. <el...@ne...> - 2005-10-14 16:26:22
|
On Friday 14 October 2005 20:08, Roger Burton West wrote: > You're passing a hashref to param(). Try: > > $tmpl->param('NEWS' => [{'created' => '2005-10-15', 'text' => > 'sdadsdsdsdw1re32fqr'}]); > > Roger > Bad file descriptor :( |
From: Roger B. W. <ro...@fi...> - 2005-10-14 16:39:18
|
On Fri, Oct 14, 2005 at 08:26:05PM +0400, Petrov Dmithriy wrote: >Bad file descriptor :( Switch it to lower-case news? Templates aren't case-sensitive, by default at least. |
From: Petrov D. <el...@ne...> - 2005-10-14 16:51:36
|
On Friday 14 October 2005 20:39, Roger Burton West wrote: > On Fri, Oct 14, 2005 at 08:26:05PM +0400, Petrov Dmithriy wrote: > >Bad file descriptor :( > > Switch it to lower-case news? Templates aren't case-sensitive, by > default at least. > I have upper-case letters both in template and script... Damn, is's very simple template! What the [censored] "file descriptor" can be in param()? |
From: Karen <kar...@gm...> - 2005-10-14 18:52:49
|
On 10/14/05, Petrov Dmithriy <el...@ne...> wrote: > Damn! Big thanks!!! :) I just noticed I've been hitting "reply" instead of "reply to all" (I vastly prefer lists that have reply-to set to the list, and yes, I'm aware of the arguments against it), so I'll executive-summarize for the list at large: turns out calling "$template->param(blahblahblah...) or die" isn't always a good thing since param doesn't always return true even when successful. Problem solved. Sam, any particular pattern to param's return value when setting it? |
From: Sam T. <sa...@tr...> - 2005-10-14 19:48:58
|
On Fri, 14 Oct 2005, Karen wrote: > Problem solved. Sam, any particular pattern to param's return value > when setting it? Nope, and I hope the documentation didn't promise any. I'm firmly in favor of exclusively using exceptions for errors, rather than C-style boolean returns. -sam |
From: Karen <kar...@gm...> - 2005-10-14 19:58:54
|
On 10/14/05, Sam Tregar <sa...@tr...> wrote: > Nope, and I hope the documentation didn't promise any. I'm firmly in > favor of exclusively using exceptions for errors, rather than C-style > boolean returns. Didn't say one way or t'other, hence my question. It might be worth putting that in the docco, though, since boolean returns are popular enough to be considered the unwritten default. |