Smarty

[micha80]

no, i'am not kidding. but when i echo the variable $file_name, i get only the name of the file but not the path where it has to be stored.

in my example the echo tag gives to me the following:

[boots]

Correct. It actually wants to write to the same location as the calling script which would have been expected to be both a writable location and a template dir. Heh, I really only ever tested this from the command line

It is actually a bit of a PITA to write to a specific directory as it is difficult to pass new setup information to the compiler due to the way the main smarty object interacts with the compiler object.

Never-the-less, I have added a slight hack and have correspondingly updated the code to v0.1.4 (back in the previous post). It should work a lot better now (but not perfect--see below). Basically, it now writes template fragments to a required subdirectory (which must be named 'clipcache') in your compiled directory. You must ensure the directory exists and is writable. Use the extended class method register_clipcache() to make sure that the compile/clipcache directory is also registered as a template directory or do so manually. BTW, if you want to try this, only the prefilter and the extended class need updating.

Unfortunately, this is likely to break for templates in subdirectories (eg: foo/bar.tpl) but I am a bit short on time at the moment so this is still beta. It should be fairly easy to fix that so I'll try to post another update soon. Even then it will probably remain in beta status since there are a few other outstanding issues.

[micha80]

thanks a lot,

i'll try this new version and maybe it can fix my new problem . everything works fine but now i got a bad issue with the "is_cached" feature (a logical mistake of myself is also possible). to catch some different php/mysql function, i try to use the "is_cached" feature but i can't get the right file for comparing.

PHP-File:

[boots]

I never tested this functionality but in theory it should work; however, you have to mention the id of the clipcache:

[php:1:b6ef9acb01]$smarty->is_cached('test.tpl#test', "foo");[/php:1:b6ef9acb01]

[boots]

Another little update. I've abandoned file_put_contents and now use Smarty's internal file writing function which has the benefit of working with PHP4 (naturally) and also supports safe directory creation. Now you needn't explicitly create the clipcache directory in your compile directory -- it will be done for you. This implicitly assumes that use_sub_dir = true. This also means that template subdirectories (foo/bar.tpl) should work now.

Still beta -- there are some outstanding issues:

the following smarty features will probably cause problems as there is no explicit support for them and they have not been tested:
- resources
- compile_id

the {clipcache} close tag is still wonky. It needs a better regex to both use a simpler (and typical) {/clipcache} closing tag and support nesting. I haven't needed it yet (in fact, I haven't needed any of this ).

nesting isn't completely tested, so please report issues.

There is also an additional feature I am considering which I would personally find useful: allowing for alternate tags to be defined. The idea is:

[micha80]

hi,

i've found the right condition to check with the is_cached function. you have to send the path (where the file is stored) and the filename to the function:

[micha80]

i get an error with the new version. the closing tag isn't recognized. i have modified the search string in the prefilter.clicache.php file to this:

prefilter.clipcache.php:

[boots]

[jason_ng]

From PHP Manual:

[boots]

@jason_ng:

Nice catch, thanks! The rtrim() method seems like the nicest way to do it as well. Good stuff.

[OpenMacNews]

hi all.

i'm just migrating to a new server setup AND back to smarty after using a non-smarty CMS ...

i've been following along here, reading thru this thread, and am stuck on something probably something obvious /simple ...

fwiw, my env is:

apache 220/worker
php 512
eaccelerator trunk/r204
smarty 2.6.13
osx 10.4.6


now, after the requisite:

require('Smarty_ClipCache.class.php');
$smarty = new Smarty_ClipCache();

the presence of:

$smarty->register_clipcache();

fires the following error:

Fatal error: Smarty_ClipCache::require_once() [function.require]: Failed opening required ''
(include_path='/path/to/resources/includes:./:/usr/local/php_libs:blahblahblah') in /path/to/resources/includes/Smarty_ClipCache.class.php on line 30

checking,
ls -al resources/includes/Smarty_ClipCache.class.php
-rw-rw---- 1 www www 1434 2006-05-02 21:06 resources/includes/Smarty_ClipCache.class.php

& @ line 30:


27: function register_clipcache()
28: {
29: $this->load_filter('pre', 'clipcache');
30: require_once $this->_get_plugin_filepath('function', 'include_clipcache');
31: $this->register_function('include_clipcache', 'smarty_function_include_clipcache', false);
42: $write_path = $this->compile_dir;

i'm fairly sure i've got all my path-ing right, as my *own* plugins *are* found in resources/plugins/

any suggestion as to what i might be missing?

thx!

richard

[boots]

Hi. Is that the exact error message? Smarty_ClipCache::require_once() isn't a method of that class... Anyways, the code is known to work when you have the two included plugins (eg: function.include_clipcache.php) in your plugins directory as shown in the code listing. I can't really tell why it isn't for you -- sorry!

[OpenMacNews]

hi boots

[boots]

@OpenMacNews: I updated the code (I replaced the code shown in the previous page's post) to version 0.1.6. It is not well tested but should work as it mainly only contains small bug fixes. Let me know how it works out for you.

[OpenMacNews]