Re: [Phpwebsite-developers] Floating menus and new functions - Matt's 2 cents

[Eloi G. <el...@re...>]

+1  -- I like the idea, Matt!

You should go with the first option though (having a set template name).
It'll cut down on the code involved and any misunderstanding on how to work
with this feature.  I haven't really looked at your templating caching
system yet, but is there a way to cache this as well?

I don't think the layout option NOT to load includes is necessary.  It
really is up to the siteop to review all template code before they use it.
Or failing that, d/l templates and modules only from trusted developers or
archives.

Eloi George (aDarkling)


----- Original Message -----
From: "Matthew McNaney" <ma...@tu...>
> Along these same lines I was thinking of something many people have asked
> for but I wish discussion before putting it in the rewrite.
>
> Layout could look for a php include file. The theme developer could then
> put special code in it if they want. For example
>
> File: themes/mytheme/runme.php
> <?php
>
> $runmeTemplate["DATE"] = date("Ymd");
>
> ?>
>
> The admin could then put {DATE} in their theme and the date would appear.
>
> This could work a couple of different ways. There could be a set template
> name they have to use. Or there might be specific layout functions they
> could call to place their data in the theme box queue.
>
> We could also have a layout option NOT to load includes until the user has
> a chance to read what is in there. I realize this could be sketchy
> security wise, but a bogus module could do just as much damage.
>
> :Matt
>
> Oh and if you want me to write those functions let me know. Layout was
> supposed to have a way to overwrite or append the metatags set in the
> module but I never got around to it.