Take your time and think about it. No rush for me. > Thiis is because the template finder code looks on the current page, > which is the page doing the including, not the page that is included. > I rewrote the code to accomplish what we want, but not sure whether or > not we want this to be the universal behavior or just an option. For > example, if someone had a standard search function used in several > different hierarchies, it might be valuable to have that included > search function use the parameters of the current hierarchy. > Hmmm. That sounds like a good thing to look on current page first. So if template not found in current page or template file of current heirarchy does not exist, then it could use the template embedded in the included file if it exists. I am OK if it works this way without any basepage flags.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
