[development] special filter behavior for teaser

Bèr Kessels ber at webschuur.com
Tue Feb 6 11:55:10 UTC 2007

Op dinsdag 6 februari 2007 08:19, schreef Rob Barreca:
> The best way IMO is to use CCK and imagefield/imagecache. Then you have
> an "image" field and can call a different imagecache preset in your
> node-content_whatever.tpl.php file when $teaser is true/false. This is
> what I have used in the past for this functionality and works quite well.

No. We have two ways in general: inline, and metadata. What you propose is 
metadata, what Dave wants/needs is inline. Lets not confuse the two.

The camp that want the node/comment/foobar objects to be passed to the filter 
have so far lost the battle (see Stevens comment) for good reasons (IMO). 


Right now, you see all the more advanced filters being implemented as 
_nodeapi, and not as filters. A bad, bad result, IMO. Much worse then the 
argument of 'clean implementation'. 

We see (rather popular) modules such as inline.module being real performance 
drainers on your site. Also the filter tips can no longer be used properly, 
and you don't ave the filter available in filter settings. 

I think that Dave is best off using that method too, here. Its unfortunate, 
its a performance problemn, and the interface becomes clumsy (filter tips 
cannot be reused etc) but at least it works. ;)
Look for an example at inline module. http://drupal.org/project/inline

Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.drupal.org/pipermail/development/attachments/20070206/577bb9c9/attachment.pgp 

More information about the development mailing list