Home > Archive > PHP Smarty Templates > August 2005 > RE: [SMARTY] Dreamweaver Users - How do you manage sites?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
RE: [SMARTY] Dreamweaver Users - How do you manage sites?
|
|
| Andras Kende 2005-07-28, 4:03 am |
|
-----Original Message-----
From: Gary Smith [mailto:gts@tsu.biz]
Sent: Wednesday, July 27, 2005 7:34 PM
To: smarty-general@lists.php.net
Subject: [SMARTY] Dreamweaver Users - How do you manage sites?
Aloha All,
My smarty configuration has my templates outside of web root. What is the
best way to configure your sites so you can use Dreamweaver to create/edit
templates?
Thanks,
Gary
Hello Gary,
I use Dreamweaver MX 2004 in FTP mode (no local copies of files..)
but templates are in the webfolder and named .htm not .tpl for the
easiest opening with Dreamweaver..
I guess Dreamveaver needs to access your templates with FTP so it
needs a ftp user account which has access outside of your webfolder...
FTP:
/home/gary/
/home/gary/templates/ smarty template files
/home/gary/public_html/ smarty php files
APACHE document root:
/home/gary/public_html/
Andras Kende
http://www.kende.com
| |
| Cameron Perry 2005-07-28, 4:03 am |
| Why not develop with the templates within the site root just to make
it easiest with DW?
Instead of writing
> $smarty = new Smarty();
> $smarty->template_dir='/path...';
> etc
in each file, why not put it in an include so that on your
development machine you can have one path - pointing to templates
within the web root, and on the server change the template path so it
points to the templates outside the web root?
~Cameron
On Jul 27, 2005, at 9:18 PM, Andras Kende wrote:
>
>
> -----Original Message-----
> From: Gary Smith [mailto:gts@tsu.biz]
> Sent: Wednesday, July 27, 2005 7:34 PM
> To: smarty-general@lists.php.net
> Subject: [SMARTY] Dreamweaver Users - How do you manage sites?
>
> Aloha All,
>
> My smarty configuration has my templates outside of web root. What
> is the
> best way to configure your sites so you can use Dreamweaver to
> create/edit
> templates?
>
> Thanks,
> Gary
>
>
>
> Hello Gary,
>
> I use Dreamweaver MX 2004 in FTP mode (no local copies of files..)
> but templates are in the webfolder and named .htm not .tpl for the
> easiest opening with Dreamweaver..
>
> I guess Dreamveaver needs to access your templates with FTP so it
> needs a ftp user account which has access outside of your webfolder...
>
> FTP:
> /home/gary/
> /home/gary/templates/ smarty template files
> /home/gary/public_html/ smarty php files
>
> apache document root:
> /home/gary/public_html/
>
> Andras Kende
> http://www.kende.com
>
> --
> Smarty General Mailing List (http://smarty.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
| |
| Gary Smith 2005-07-28, 5:03 pm |
| Hi Andras,
So you have your htm files and your php files in the same folder?
Gary
in article A8.91.58254.FAC58E24@pb1.pair.com, "Andras Kende" at
andras@kende.com wrote on 7/27/05 6:18 PM:
>
>
> -----Original Message-----
> From: Gary Smith [mailto:gts@tsu.biz]
> Sent: Wednesday, July 27, 2005 7:34 PM
> To: smarty-general@lists.php.net
> Subject: [SMARTY] Dreamweaver Users - How do you manage sites?
>
> Aloha All,
>
> My smarty configuration has my templates outside of web root. What is the
> best way to configure your sites so you can use Dreamweaver to create/edit
> templates?
>
> Thanks,
> Gary
>
>
>
> Hello Gary,
>
> I use Dreamweaver MX 2004 in FTP mode (no local copies of files..)
> but templates are in the webfolder and named .htm not .tpl for the
> easiest opening with Dreamweaver..
>
> I guess Dreamveaver needs to access your templates with FTP so it
> needs a ftp user account which has access outside of your webfolder...
>
> FTP:
> /home/gary/
> /home/gary/templates/ smarty template files
> /home/gary/public_html/ smarty php files
>
> apache document root:
> /home/gary/public_html/
>
> Andras Kende
> http://www.kende.com
| |
| Gary Smith 2005-07-28, 5:03 pm |
| Hi Cameron,
So have a templates folder inside the web root on the local machine and
outside on the remote machine? Would I then have to use another ftp program
to keep the files in different places for the local and remote machines?
Gary
in article 1660FFAC-1D3C-4265-995E-3ED6751E178C@filled.us, Cameron Perry at
lists@filled.us wrote on 7/27/05 8:40 PM:
[color=darkred]
> Why not develop with the templates within the site root just to make
> it easiest with DW?
> Instead of writing
> in each file, why not put it in an include so that on your
> development machine you can have one path - pointing to templates
> within the web root, and on the server change the template path so it
> points to the templates outside the web root?
>
> ~Cameron
>
>
> On Jul 27, 2005, at 9:18 PM, Andras Kende wrote:
>
| |
| Cameron Perry 2005-07-28, 5:03 pm |
| Hi Gary,
It would be most convenient to let dreamweaver upload the new
template files via FTP, though it probably won't allow you to have
the path disparity. What you can do, as you mentioned, is use some
other FTP program to manually upload the directory once you've saved
the changes.
From my experiences with DW (I'm not an expert, just a user), there
really is no easy way to develop any web content stored outside the
web root.
~Cameron
On Jul 28, 2005, at 11:28 AM, Gary Smith wrote:
> Hi Cameron,
>
> So have a templates folder inside the web root on the local machine
> and
> outside on the remote machine? Would I then have to use another ftp
> program
> to keep the files in different places for the local and remote
> machines?
>
> Gary
>
>
> in article 1660FFAC-1D3C-4265-995E-3ED6751E178C@filled.us, Cameron
> Perry at
> lists@filled.us wrote on 7/27/05 8:40 PM:
>
>
>
> --
> Smarty General Mailing List (http://smarty.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
| |
| Gary Smith 2005-07-28, 5:03 pm |
| Thanks Cameron,
What if I move my templates to a folder inside web root? How would I preview
them locally and remote? I have separate templates for headers and footers
so my content template doesn't display right in design view because of
missing stylesheets and javascript. How do you work with nested templates?
Should I name my templates .htm or something?
Any Advice?
Gary
in article B7EDA209-781D-4DC1-A94D-55FA32CAFFCA@filled.us, Cameron Perry at
lists@filled.us wrote on 7/28/05 9:13 AM:
[color=darkred]
> Hi Gary,
>
> It would be most convenient to let dreamweaver upload the new
> template files via FTP, though it probably won't allow you to have
> the path disparity. What you can do, as you mentioned, is use some
> other FTP program to manually upload the directory once you've saved
> the changes.
>
> From my experiences with DW (I'm not an expert, just a user), there
> really is no easy way to develop any web content stored outside the
> web root.
>
> ~Cameron
>
>
> On Jul 28, 2005, at 11:28 AM, Gary Smith wrote:
>
| |
| Cameron Perry 2005-07-28, 10:01 pm |
| Honestly, I have not done *that* much with Smarty. The first Smarty-
based site I was working on a few months ago for work go scrapped
pretty early on, but looking at the directory structure, it looks
like I simply left the templates within the site root. From what I
remember, it was the only way to get dreamweaver to work correctly.
Have you tried using symlinks and relative paths in your templates/
scripts to trick DW?
~C
On Jul 28, 2005, at 3:05 PM, Gary Smith wrote:
> Thanks Cameron,
>
> What if I move my templates to a folder inside web root? How would
> I preview
> them locally and remote? I have separate templates for headers and
> footers
> so my content template doesn't display right in design view because of
> missing stylesheets and javascript. How do you work with nested
> templates?
> Should I name my templates .htm or something?
>
> Any Advice?
> Gary
>
>
> in article B7EDA209-781D-4DC1-A94D-55FA32CAFFCA@filled.us, Cameron
> Perry at
> lists@filled.us wrote on 7/28/05 9:13 AM:
>
>
>
> --
> Smarty General Mailing List (http://smarty.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
| |
| Gary Smith 2005-07-28, 10:01 pm |
| Hmmm...
I was hoping I could come up with a configuration that would allow my
designers to work with the templates in dreamweaver but it looks like there
are too many obstacles (paths, file types and names, nested templates) that
would make it too hard (ftp, previewing, etc.) for them to use. I've
downloaded all the extensions I could find for Smarty and Dreamweaver but it
looks like there is no way to get a good development environment configured
to allow this. Too bad, Dreamweaver and Smarty seemed like the perfect
solution for me. I was hoping that this would be a common setup for
smarty-dreamweaver users. Anybody else have this setup?
Thanks,
Gary
in article 3768ED8F-1B58-4557-AA83-BCDE8177BD8C@filled.us, Cameron Perry at
lists@filled.us wrote on 7/28/05 12:59 PM:
[color=darkred]
> Honestly, I have not done *that* much with Smarty. The first Smarty-
> based site I was working on a few months ago for work go scrapped
> pretty early on, but looking at the directory structure, it looks
> like I simply left the templates within the site root. From what I
> remember, it was the only way to get dreamweaver to work correctly.
> Have you tried using symlinks and relative paths in your templates/
> scripts to trick DW?
>
>
>
> ~C
>
> On Jul 28, 2005, at 3:05 PM, Gary Smith wrote:
>
| |
| Joe Evans 2005-07-28, 10:01 pm |
| I am a web designer that is very fond of both Dreamweaver and Smarty. They
have done everything I have ever asked. However, the two don't generally
pay nice together in all the ways we would like.
There was a real nice post about text coloring o the smarty site FAQ's. It
may still be there. Other than that, it is really a crap shoot.
Dreamweaver won't show Smarty templates in the same way that that it will
show its own templates together.
I generally compose the folder structure locally the same way it is
recommended on the Smarty quick start and simply upload the same way.
I keep the configuration files and the "Smarty" folder with the 4 required
folders outside of root. All others are obviously inside root.
I would love to see Dreamweaver work more with Smarty templates in the next
versions, but for now it seems to work best with Cold Fusion, ASP, and the
like.
Hope I can be of help...
Joe
UpFront Technology
-----Original Message-----
From: Gary Smith [mailto:gts@tsu.biz]
Sent: Thursday, July 28, 2005 8:07 PM
To: smarty-general@lists.php.net
Subject: Re: [SMARTY] Dreamweaver Users - How do you manage sites?
Hmmm...
I was hoping I could come up with a configuration that would allow my
designers to work with the templates in dreamweaver but it looks like there
are too many obstacles (paths, file types and names, nested templates) that
would make it too hard (ftp, previewing, etc.) for them to use. I've
downloaded all the extensions I could find for Smarty and Dreamweaver but it
looks like there is no way to get a good development environment configured
to allow this. Too bad, Dreamweaver and Smarty seemed like the perfect
solution for me. I was hoping that this would be a common setup for
smarty-dreamweaver users. Anybody else have this setup?
Thanks,
Gary
in article 3768ED8F-1B58-4557-AA83-BCDE8177BD8C@filled.us, Cameron Perry at
lists@filled.us wrote on 7/28/05 12:59 PM:
[color=darkred]
> Honestly, I have not done *that* much with Smarty. The first Smarty-
> based site I was working on a few months ago for work go scrapped
> pretty early on, but looking at the directory structure, it looks
> like I simply left the templates within the site root. From what I
> remember, it was the only way to get dreamweaver to work correctly.
> Have you tried using symlinks and relative paths in your templates/
> scripts to trick DW?
>
>
>
> ~C
>
> On Jul 28, 2005, at 3:05 PM, Gary Smith wrote:
>
--
Smarty General Mailing List (http://smarty.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
| |
| Mark Rogers 2005-07-29, 9:05 am |
| Gary Smith wrote:
> What if I move my templates to a folder inside web root? How would I
> preview them locally and remote?
For what its worth, this is how I've handled similar situations:
~\htdocs <- Apache's document root
~\htdocs\index.php <- This is PHP
~\templates <- Dreamweaver's document root
~\templates\index.html <- This is HTML template
~\templates\img\ <- This is where I put images
~\templates\css\ <- This is where I put stylesheets
~\templates\js\ <- This is where I put javascript
(~ is just some directory on my web server under which all the site's files
are stored.)
This means that using ~\templates as the document root the templates work
fine in (eg) Dreamweaver - image paths etc are fine.
I then use aliases in the apache config to map /img/ to ~\templates\img\,
etc, so that the site works when the PHP code is run (from Apache's document
root of ~\htdocs).
Advantages: All the design stuff is separate from the code logic, so the
designer has complete control over the ~\templates directory. But it is all
outside document root, except for the specific img/js/css stuff which is
mapped back inside document root by Apache.
On the occasions where I need dynamic css/js/img files (eg a stylesheet
which is generated through PHP and likely also through Smarty) I create
additional directories:
~\htdocs\dyncss <- Dynamic CSS (ie PHP code)
~\templates\dyncss <- Templates for dynamic CSS
... etc. Therefore again there is separation between the work of the coder
and the designer.
A general point: be VERY careful if you move your templates under document
root (by which I really mean don't do it).
Consider:
~\htdocs\index.php
~\htdocs\templates\index.tpl
It's obvious what http://example.com/index.php will show (ie your webpage,
presumably based on the index.tpl tenplate), but you must also recognise
that http://example.com/templates/index.tpl will allow the site visitor to
see your raw (unprocessed by Smarty or PHP) template code, which may well
include things you do not want made available. You can fix this through
appropriate apache configuration, but in my view it's safer to avoid
altogether.
[If you use a Linux/Unix server, as I do, then of-course all the 's should
be /'s. However I think it's easier to distinguish between the file
structure and the URL's when they're written this way.]
Mark Rogers,
More Solutions Ltd
| |
| Ognyan Bankov 2005-07-29, 9:05 am |
| Gary Smith wrote:
> Hmmm...
>
> I was hoping I could come up with a configuration that would allow my
> designers to work with the templates in dreamweaver but it looks like there
> are too many obstacles (paths, file types and names, nested templates) that
> would make it too hard (ftp, previewing, etc.) for them to use. I've
> downloaded all the extensions I could find for Smarty and Dreamweaver but it
> looks like there is no way to get a good development environment configured
> to allow this. Too bad, Dreamweaver and Smarty seemed like the perfect
> solution for me. I was hoping that this would be a common setup for
> smarty-dreamweaver users. Anybody else have this setup?
>
> Thanks,
> Gary
>
yep, we use smarty-dreamweaver combination and smarty files are outside
of docroot.
About the obstacles:
There is not any real obstacles, designers tend to complain if they are
smarty unexpirienced.
We have organized our work in folloing manner:
1. Designer creates psd or png layout.
1.1. Layout is shown to the client and changed until acceptance.
2. Designer/slicer slices layout to jpg/gifs and creates html files for
index.html and internal_page.html (for example). At that point you have
html files visualy identical to psd/png layout (sample static
text/data is used where dynamicly generated content will be placed).
Those files are temporary and used for convenience (can do preview in
DW, etc.). Optionaly, you can show html (previewed in browser, of
course) to the client to verify that some fluffy things as rollover
images, animated gifs (!), js/dhtml menus, etc. are acceptable.
3. Designer/slicer/programmer creates index.tpl, header.tpl, footer.tpl,
index_content.tpl, etc. and puts in appropriate parts of index.html html
code.
4. Programmer creates index.php that uses index.tpl.
5. From that point on, desiner uses preview ONLY in real browser.
6. Programmer adds functionality to index.php (loading from db, etc).
7. Designer/programmer modifies *.tpl files and places smarty tags
8. Page is previewed
9. Corrections are made (if needed)
10. Iterating 7-10 until done...
Of course in the reality thing tend to get much more complicated,
especially with large sites.
Key point are:
- designers must feel confortable with smarty. That is achieved by training
- programmers have to be cooperative and responsive to "stupid"
questions from designers about smarty
- you have to have some kind of "visual freeze". Without it the project
may cycle endlessly between 1-10, causing tension between designers,
programmers, managers, clients...
--
Ognyan Bankov
metatotem.com
| |
| Gary Smith 2005-08-04, 10:02 pm |
| Aloha All,
Thanks to everyone for their replies. Here is what I ended up doing.
~\htdocs <- Apache's document root
~\htdocs\index.html <- This is PHP
~\htdocs\assets\images <- This is where I put images
~\htdocs\assets\css\ <- This is where I put stylesheets
~\htdocs\assets\js\ <- This is where I put javascript
~\templates <- Dreamweaver's document root
~\templates\index.tpl <- This is my smarty template
~\templates\assets <- Symlink to ~\htdocs\assets
I configure my testing server to parse .tpl files as SSI. Then I use SSI
includes in my templates for template pieces such as header.tpl and
footer.tpl. I then use ftp to upload my files to the remote server.
Great combination!
Gary
in article 231b01c59429$4bfd0410$1fc70005@mark, "Mark Rogers" at
mark@quarella.co.uk wrote on 7/29/05 12:35 AM:
> Gary Smith wrote:
>
> For what its worth, this is how I've handled similar situations:
>
> ~\htdocs <- Apache's document root
> ~\htdocs\index.php <- This is PHP
> ~\templates <- Dreamweaver's document root
> ~\templates\index.html <- This is HTML template
> ~\templates\img\ <- This is where I put images
> ~\templates\css\ <- This is where I put stylesheets
> ~\templates\js\ <- This is where I put javascript
>
> (~ is just some directory on my web server under which all the site's files
> are stored.)
>
> This means that using ~\templates as the document root the templates work
> fine in (eg) Dreamweaver - image paths etc are fine.
>
> I then use aliases in the apache config to map /img/ to ~\templates\img\,
> etc, so that the site works when the PHP code is run (from Apache's document
> root of ~\htdocs).
>
> Advantages: All the design stuff is separate from the code logic, so the
> designer has complete control over the ~\templates directory. But it is all
> outside document root, except for the specific img/js/css stuff which is
> mapped back inside document root by Apache.
>
> On the occasions where I need dynamic css/js/img files (eg a stylesheet
> which is generated through PHP and likely also through Smarty) I create
> additional directories:
>
> ~\htdocs\dyncss <- Dynamic CSS (ie PHP code)
> ~\templates\dyncss <- Templates for dynamic CSS
>
> .. etc. Therefore again there is separation between the work of the coder
> and the designer.
>
> A general point: be VERY careful if you move your templates under document
> root (by which I really mean don't do it).
>
> Consider:
> ~\htdocs\index.php
> ~\htdocs\templates\index.tpl
>
> It's obvious what http://example.com/index.php will show (ie your webpage,
> presumably based on the index.tpl tenplate), but you must also recognise
> that http://example.com/templates/index.tpl will allow the site visitor to
> see your raw (unprocessed by Smarty or PHP) template code, which may well
> include things you do not want made available. You can fix this through
> appropriate apache configuration, but in my view it's safer to avoid
> altogether.
>
> [If you use a Linux/Unix server, as I do, then of-course all the 's should
> be /'s. However I think it's easier to distinguish between the file
> structure and the URL's when they're written this way.]
>
> Mark Rogers,
> More Solutions Ltd
| |
| Jonathan Chum 2005-08-05, 9:02 am |
| Hi Guys,
I had the same problem and thought about doing a symlink just like you
described below. The only problem was that I develop software that may need
to run on other servers where there might not be a telnet interface to
create a symlink. So, what I did was a write a postfilter function for
Smarty that rewrites all the URLs in the HTML template to point to any
location.
In Dreamweaver MX, I use relative pathing from the site root. So everything
points to /templates/images/etc/
Since my Smarty scripts are in a directory above the templates folder, I run
this postfilter function which rewrites most of the common paths for a
href=", img src=", css, and JS alright. I'm sure someone could probably
write a more complete search/replace for all the combinations.
$sm-> register_postfilter(array(TemplateManage
r, 'change_path'));
function change_path($tpl_source, &$smarty)
{
$url = "/presencegiftshop";
$search = array( "=\"/", "='/",
"location=/", "'/" );
$replace = array( "=\"$url/", "='$url/",
"location='$url/", "'$url/");
return str_replace($search,$replace,$tpl_source
);
}
As for header/footer was concern, I merge the header/footer into one file
which I called main.htm. I have written an extension to Smarty which I call
the TemplateManager which allows me to call a function like:
$sm->Display('index');
What this would do is perform a Smarty fetch on the file index.htm, parse
it, return it back into a string, assign it to the variable 'body', and then
display main.htm. main.htm would have a variable called 'body' which the
contents of index.htm would be replaced into it.
Sometimes, my templates are organic which means if I chop an enclosed table
into a header/footer, it's tough tweaking it without munging it back
together in a temporary HTML document. Having a file main.htm that is my
wrapper built around a variable called 'body' allows me to tweak the
header/footer without chopping it up later.
So my site structure ends up looking like this:
~jchum/index.php <- Instantiates a copy of
DBManager and TemplateManager
~jchum/libs <- All of my libs lives here
~jchum/libs/dbi
~jchum/libs/phpmailer
~jchum/libs/smarty
~jchum/libs/TemplateManager.php
~jchum/libs/DBManager.php
~jchum/templates
~jchum/templates/images
~jchum/templates/js
~jchum/templates/css
~jchum/templates/main.htm
~jchum/templates/index.htm
The templates folder contained all of my assets. The main.htm was my
template wrapper which wraps around any other template. I also used .htm
extension instead of .tpl because I could load into Dreamweaver MX much more
easily. I also change the left/right delimiters to use <!--- ---> such that
the Smarty tags appears as comments instead of text in design view.
This setup made it easy for me to drop this package each time I begin
working on a new project. I change the DB connection settings in
DBManager.php, edit the path for the asset rewrites, and I'm ready to rock
and roll :)
-----Original Message-----
From: Gary Smith [mailto:gts@tsu.biz]
Sent: Thursday, August 04, 2005 6:11 PM
To: smarty-general@lists.php.net
Subject: Re: [SMARTY] Dreamweaver Users - How do you manage sites?
Aloha All,
Thanks to everyone for their replies. Here is what I ended up doing.
~\htdocs <- Apache's document root
~\htdocs\index.html <- This is PHP
~\htdocs\assets\images <- This is where I put images
~\htdocs\assets\css\ <- This is where I put stylesheets
~\htdocs\assets\js\ <- This is where I put javascript
~\templates <- Dreamweaver's document root
~\templates\index.tpl <- This is my smarty template
~\templates\assets <- Symlink to ~\htdocs\assets
I configure my testing server to parse .tpl files as SSI. Then I use SSI
includes in my templates for template pieces such as header.tpl and
footer.tpl. I then use ftp to upload my files to the remote server.
Great combination!
Gary
in article 231b01c59429$4bfd0410$1fc70005@mark, "Mark Rogers" at
mark@quarella.co.uk wrote on 7/29/05 12:35 AM:
> Gary Smith wrote:
>
> For what its worth, this is how I've handled similar situations:
>
> ~\htdocs <- Apache's document root
> ~\htdocs\index.php <- This is PHP
> ~\templates <- Dreamweaver's document root
> ~\templates\index.html <- This is HTML template
> ~\templates\img\ <- This is where I put images
> ~\templates\css\ <- This is where I put stylesheets
> ~\templates\js\ <- This is where I put javascript
>
> (~ is just some directory on my web server under which all the site's
files
> are stored.)
>
> This means that using ~\templates as the document root the templates work
> fine in (eg) Dreamweaver - image paths etc are fine.
>
> I then use aliases in the apache config to map /img/ to ~\templates\img\,
> etc, so that the site works when the PHP code is run (from Apache's
document
> root of ~\htdocs).
>
> Advantages: All the design stuff is separate from the code logic, so the
> designer has complete control over the ~\templates directory. But it is
all
> outside document root, except for the specific img/js/css stuff which is
> mapped back inside document root by Apache.
>
> On the occasions where I need dynamic css/js/img files (eg a stylesheet
> which is generated through PHP and likely also through Smarty) I create
> additional directories:
>
> ~\htdocs\dyncss <- Dynamic CSS (ie PHP code)
> ~\templates\dyncss <- Templates for dynamic CSS
>
> .. etc. Therefore again there is separation between the work of the coder
> and the designer.
>
> A general point: be VERY careful if you move your templates under document
> root (by which I really mean don't do it).
>
> Consider:
> ~\htdocs\index.php
> ~\htdocs\templates\index.tpl
>
> It's obvious what http://example.com/index.php will show (ie your webpage,
> presumably based on the index.tpl tenplate), but you must also recognise
> that http://example.com/templates/index.tpl will allow the site visitor to
> see your raw (unprocessed by Smarty or PHP) template code, which may well
> include things you do not want made available. You can fix this through
> appropriate apache configuration, but in my view it's safer to avoid
> altogether.
>
> [If you use a Linux/Unix server, as I do, then of-course all the 's
should
> be /'s. However I think it's easier to distinguish between the file
> structure and the URL's when they're written this way.]
>
> Mark Rogers,
> More Solutions Ltd
--
Smarty General Mailing List (http://smarty.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
|
|
|
|
|