On 13 Jul 2009, at 01:05, Wallace McGee wrote:
1) The xml parser stops completely if it finds a doubly defined
attribute like class="" and style="". Previously it would use just
the last one defined.
That is intended (XML requires it) and will not change. You have to
fix syntax of your
Hi guys,
A while back I tried PHPTAL 1.2.0 alpha.
I found most of it worked apart from a few things listed below.
I posted this a back in March but have not seen any comments in relation
to these as yet.
Have others noticed these and/or have any of them been addresses?
1) The xml parser s
On 11.07.2009, at 08:14, Stojce Slavkovski wrote:
Where can I report bug?
PHPTAL ver.1.2.0
/PHPTAL/Dom/Element.php: line259:
foreach($this->childNodes as $node) { => foreach($this->childNodes
as $child) {
Thanks. It's fixed in SVN.
--
regards, Kornel
_
Where can I report bug?
PHPTAL ver.1.2.0
/PHPTAL/Dom/Element.php: line259:
foreach($this->childNodes as $node) { => foreach($this->childNodes as
$child) {
regards,
stojce
On Jul 8, 2009, at 5:20 PM, Kornel Lesinski wrote:
PHPTAL@lists.motion-twin.com
__
Kornel already gives you the ability to add your own custom extensions
(via -e).
This is a very useful tool.
Nick Pack wrote:
> Can .phtml be added to the extensions list, for all us ZF users ;)
>
> Thanks
>
>
> On 08/07/2009 16:20, "Kornel Lesinski" wrote:
>
>
>> I'm going to release 1.2.0
Can .phtml be added to the extensions list, for all us ZF users ;)
Thanks
On 08/07/2009 16:20, "Kornel Lesinski" wrote:
>
> I'm going to release 1.2.0 soon.
>
> I've created tool that can scan all PHPTAL templates and look for
> errors:
> https://svn.motion-twin.com/phptal/trunk/tools/phptal
I'm going to release 1.2.0 soon.
I've created tool that can scan all PHPTAL templates and look for
errors:
https://svn.motion-twin.com/phptal/trunk/tools/phptal_lint.php
1. Install latest PHPTAL beta (or check it out from SVN)
2. Run from command line:
php phptal_lint.php /path/to/your/temp
Billiant! All fixed :)
Think I went a bit slot-crazy ;)
Cheers,
-Alister
2009/5/15 Kornel Lesiński
> It seems that you've used slots where macros would have been more
> appropriate.
>
>
> This just defines the same slot many times:
>
>
>
>
>
>
> and the code below it, outside the loo
It seems that you've used slots where macros would have been more appropriate.
This just defines the same slot many times:
and the code below it, outside the loop:
is run unconditionally, once, after the loop finishes. That's why you're
getting error about entry varia
Thanks Werner and Kornel...
I'll fix the omit-tag thing. A silly oversight.
Now, I've uploaded the raw and unprocessed template file to:
http://www.alistercameron.com/tal.tpl.txt
To clarify, this is a file that is compiled in a rather complex way which
has to do with how my WordPress theme is bu
On 14-05-2009 at 06:34:11 Alister Cameron
wrote:
> Could I bother someone to have a look at the processed cache file and
> diagnose?
>
> http://www.alistercameron.com/tal.src.txt
This code uses entry variable _after_ the loop (e.g. in
id="post-${entry/the_ID}"). Do you have such code in your t
Hi Alister
Can you please post the code that assigns the variables to the template
object?
E.g, If you did the var_dump on $data and $data['entries'] is defined,
and you assigned $data to $template like
$template->data = $data;
...then I would expect the loop to look like:
...Or did yo
Gents,
Perhaps I should stick to the production version but I hoped to help test
the latest alpha.
I've encountered an issue where it's not iterating thru a repeat, but I
don't see what I'm doing wrong.
Could I bother someone to have a look at the processed cache file and
diagnose?
http://www.al
On 29-04-2009 at 19:07:27 Tjerk Meesters wrote:
Guess the __DIR__ constant came a bit too late then ;-)
I had PHP_DIR there previously, but that had a mysterious side-effect of
slowing down includes in APC.
--
regards, Kornel
___
PHPTAL mailing
Guess the __DIR__ constant came a bit too late then ;-)
On 4/29/09, Kornel Lesiński wrote:
> On 29-04-2009 at 00:53:41 romtek wrote:
>
>>> OK, I've given up on require() and changed it all to require_once().
>>
>> Is there ever a reason to use require() to include code (not text)?
>
> I hoped it
On 29-04-2009 at 00:53:41 romtek wrote:
OK, I've given up on require() and changed it all to require_once().
Is there ever a reason to use require() to include code (not text)?
I hoped it would be faster than require_once, but it turned out that with
relative paths the difference is insign
2009/4/28 Kornel Lesiński
> OK, I've given up on require() and changed it all to require_once().
>
Is there ever a reason to use require() to include code (not text)?
___
PHPTAL mailing list
PHPTAL@lists.motion-twin.com
http://lists.motion-twin.com/mai
Am Dienstag 28 April 2009 schrieb Kornel Lesiński:
> OK, I've given up on require() and changed it all to require_once().
This solved the problem with the double definition of PHPTAL_Tales.
Nice!
> I've also accidentally found workaround for the other (string:$var) bug
> you've reported.
This i
On 27-04-2009 at 16:51:32 Christian Welzel wrote:
Hi there,
today i upgraded my test system from 1.1.15 to 1.2-alpha-10 and now
im hitting this error:
Fatal error: Cannot redeclare class PHPTAL_Tales in
/usr/share/php/PHPTAL/TalesRegistry.php on line 23
I'm using the zend framework with the ze
Am Montag 23 März 2009 schrieb Kornel Lesinski:
> Some of those changes could break your templates, triggers, custom
> attributes, etc., so please test it, break it and report any bugs and
> incompatibilities!
Hi there,
today i upgraded my test system from 1.1.15 to 1.2-alpha-10 and now
im hittin
I have had a quick test and found a lot of it is working fine.. great work!
I did find my code breaks at these points:
1) The xml parser stops completely if it finds a doubly defined
attribute like class="" and style="". Previously it would use just the
last one defined.
The error reportin
This sounds great, I can't wait to try it out.
Thanks for all your efforts, Kornel!
Kind Regards,
Werner
Kornel Lesinski wrote:
I've worked on PHPTAL's internals: fixed loads of bugs, and cleaned up
the code.
Some of those changes could break your templates, triggers, custom
attributes, etc
I've worked on PHPTAL's internals: fixed loads of bugs, and cleaned up
the code.
Some of those changes could break your templates, triggers, custom
attributes, etc., so please test it, break it and report any bugs and
incompatibilities!
http://phptal.motion-twin.com/files/PHPTAL-1.2.0a1.t
23 matches
Mail list logo
