Include or not to include (I was thinking (oh no, not again))

Hello Y'all,

I am slowly working up a quite complex tbs infrastructure with a lot of
These different files have between 2-4 more and less complicated  blocks.
I of course use the cache module in tbs which is great.
But it does have some limitations. For instance if when a user is logged in and is handling his user data.
What I was thinking was to make a lot of
This is a crude example but I hope you understand.
Are anyone doing this already?
What are the pro/con's?

Thanks in advance.
mgb

In a sense, it's just a matter of doing it with template or with PHP.

The only meaningful difference I can think of is putting it in html make the template clearer, since you mark the include right there.  Easier for designers to work with.  While putting it in PHP allows more control - fallback template, customised error message, common template pre-conditioning, etc.

I personally tend to put it in template, esp. if there are no other needs.  Speed different is too minor to be considered.

Hope this will help.

Hi sheepy,
And thanks for the input. I wasn't too concerned about speed.
My site gets 30/s hits so this should not be a problem. Especially if I use caching.
I use a lot of includes is because we have a lot of repeating content on the site - menu's and such.
What I was thinking was for instance:
Our main menu is quite complex with submerges, bells and whistles :)
What I was suggesting was to cache the menu template one separately. So that it would always look the same on all sites (no matter when the page is cached) and also would not need to be merged every time a non-cached page gets hit.
In that way I could have cached elements on the site together with on the fly merges.
I don't know if this makes sense to you, but at the moment it does to me :)

Maybe a feature request could be to have something like:
so that if cache is set to false the merge would be done, but the cached file would still include the tbs block and need to be merged on future hits.
I don't know if this would be to complex to do, I might very well be.
Maybe it would be best to separate it out into its own plug-in?

Just some thoughts, feel free to flame :)

hi Mgb,

Such a feature was in study. In fact it can be done by a plug-in but it has to be done.

You can also do another way : use sub-script for caching sub-templates.
Example: And then you sub-script manage the merging and the caching. action=menu is a custom parameter that you can retrieve inside your subscript in order to decide which content to merge.

Hi Skrol29,
Thats a nifty work-around, I hadn't thought of using script like that at all :)

About the plug-in I think I will devote some of my Christmas spirit/time to understanding how they work. Who knows, maybe I can actually do something productive for the tbs community other than ask questions :)