I second Fred. Making a module is always a good idea. The code gets compiled before whereas in case of block, only while execution does the code get loaded from db and then is compiled and executed. I think the php accelerators like eaccelerator and stuff will not be able to cache the op code from the code which is saved in db. <br>
<br><div class="gmail_quote">On Wed, Jan 19, 2011 at 4:31 AM, Fred Jones <span dir="ltr"><<a href="mailto:fredthejonester@gmail.com">fredthejonester@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">>> In general tho mate, this is bad practice. Put it in code somewhere,<br>
>> not in a block. (like page.tpl.php or node.tpl.php).<br>
><br>
> But where? And how can I have it displayed where I want,<br>
> like blocks? I'm quite new to drupal...<br>
<br>
</div>Make a module and use:<br>
<a href="http://api.drupal.org/api/drupal/developer--hooks--core.php/function/hook_block/6" target="_blank">http://api.drupal.org/api/drupal/developer--hooks--core.php/function/hook_block/6</a><br>
<br>
Google for how to make your first custom Drupal module<br>
<br>
HTH<br>
<div><div></div><div class="h5">--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Cheers,<div>Mukesh Agarwal</div><br>