From: Geoff S. <ge...@ho...> - 2003-02-16 20:10:54
|
I've been looking at the directory structure and I have a major concern.=20 The theme and template files are distributed into numerous directories and = reside in places like mod subdirectories. I perceive this to be a maintenance = nightmare. As we all know, the most time consuming aspect of setting up a = phpWebsite installation is creating or customizing the theme. Assume for a = moment that I customize the clean theme for a website I'm doing. Then along = comes an upgrade. How do I load the updated code without overwriting theme and = template modules distributed accross the system - thereby frying the website? Maybe you guys have thought about this? Geoff Staples Hostricity Web Hosting www.Hostricity.com 214.599.0260 ge...@ho... 3883 Turtle Creek Blvd., Suite 1812 Dallas, Texas 75219 |
From: Geoff S. <ge...@ho...> - 2003-02-16 22:12:45
|
I've been looking at the directory structure and I have a major concern.=20 The theme and template files are distributed into numerous directories and = reside in places like mod subdirectories. I perceive this to be a maintenance = nightmare. As we all know, the most time consuming aspect of setting up a = phpWebsite installation is creating or customizing the theme. Assume for a = moment that I customize the clean theme for a website I'm doing. Then along = comes an upgrade. How do I load the updated code without overwriting theme and = template modules distributed accross the system - thereby frying the website? Maybe you guys have thought about this? Geoff Staples Hostricity Web Hosting www.Hostricity.com 214.599.0260 ge...@ho... 3883 Turtle Creek Blvd., Suite 1812 Dallas, Texas 75219 |
From: Matthew M. <ma...@tu...> - 2003-02-17 16:46:30
|
> Then along comes an upgrade. How do I load the > updated code without overwriting theme and template modules distributed > accross the system - thereby frying the website? As Eloi stated, you would just change your theme. The templates are fairly standard. If anything, we would just be adding new tags to the defaults. Then your would place the defaults in your theme's templates as well. In many cases, you won't need a copy of the template in your theme directory. Many admin menus and such are fine as is. But if you want to improve upon an existing display template for your theme, the option is there. However, any change in templates should not fry your system. What we as developers need to watch out for is when we completely change the functionality of a particular template. For example, let's say we have a template named "myHomies.tpl" that lists a bunch of users. We should not alter the template structure (say by spliting the display into 3 new templates) and then to continue using that file name in the process. myHomies.tpl may be set in someone's theme, which we have no control over. If we totally revamp the templates, we should exclude that file name so that it is not picked up during processing of the new structure. Hope that helps. Please respond if you have more concerns. Matt Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
From: Geoff S. <ge...@ho...> - 2003-02-16 19:38:45
Attachments:
GEOFF.vcf
|
I've been looking at the directory structure and I have a major concern.=20 The theme and template files are distributed into numerous directories and = reside in places like mod subdirectories. I perceive this to be a maintenance = nightmare. As we all know, the most time consuming aspect of setting up a = phpWebsite installation is creating or customizing the theme. Assume for a = moment that I customize the clean theme for a website I'm doing. Then along = comes an upgrade. How do I load the updated code without overwriting theme and = template modules distributed accross the system - thereby frying the website? Maybe you guys have thought about this? Geoff Staples Hostricity Web Hosting www.Hostricity.com 214.599.0260 ge...@ho... 3883 Turtle Creek Blvd., Suite 1812 Dallas, Texas 75219 |
From: Eloi G. <el...@re...> - 2003-02-17 14:58:19
|
The theme & template files that you see in the mod directories are "default" files. When phpWS looks for a template, it first looks under the current /theme/xxxx/template directory. If it can't find the requested file there it falls back on the one in the /mod/xxxx/template directory. The only reason you'd change the base templates is if you wanted to make a change that automatically affects all themes. For the maintenance reasons you specified I'd suggest you take the long way around and make the changes in each individual theme. >Assume for a moment that I customize the clean theme for a website I'm doing. Then it's not the clean theme anymore, is it? <grin> Go ahead & rename it. If you want to make any changes to standard themes, you should always modify a copy instead. -Eloi George- |