Re: HTML/IT
| From: | Wodzu | Date: | Sat, 24 Aug 2002 20:31:00 +0000 |
| Subject: | Re: HTML/IT | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-8637@lists.php.net to get a copy of this message | ||
Markus Wolff wrote:
On Sat, 24 Aug 2002 22:02:48 +0200 Wodzu <wodzu@tonet.pl> wrote:I also have some question. I'm rewriting forum to pear standards. In this forum templates are in pear/forum/lib/skins directory. But when I'm trying to make this templates in IT standard get error because IT can't find these template files. This is because skins are only in include directory. So what should i do? 1. move skins to local directory (every user should have own copy of skins)That´s probably not a bad idea, as a potential user will most likely use a modified version of the templates anyway, to match his personal taste or corporate design. Also, you´ll need image files in local directories so that they can be accessed by the webserver. Yess I just thought about images. And indeed users want to change templates. 1 + 1 = 2 and I'm moving skins to local frontend directory :)
i can do them if users may not have access to pear directory :( Plugins is generally horrible idea. Best regards, Chief2. change path to absolute to get these skins from pear/forum/lib/skins - I'm not sure they can be achieved if pear directoryNot a good idea. The PEAR installation path may vary on different systems.is in somewhere outside location3. change IT for finding files also in include directories - the worse imo ideaWell I don´t particularly like the thought, either :-)4. don't use IT :)You´d have the same problem with any other template class. Another alternative to the first solution might be adding a new method to the PEAR base class that determines the include directory that is actually used for PEAR. This could look like this: function getPearDirectory() { return dirname(__FILE__); } You could then set the template directory by doing something like this: $templateDir = PEAR::getPearDirectory().'/forum/lib/skins'; Just an idea... Thanks for help :) I also have the same problem with plugins. And i really don't have any idea how