mirror of
https://github.com/smarty-php/smarty.git
synced 2025-08-04 18:34:27 +02:00
update a few files
This commit is contained in:
8
FAQ
8
FAQ
@@ -78,7 +78,7 @@ A: You certainly can. Smarty's cache and these cache solutions have nothing in
|
|||||||
utmost importance, we would recommend using one of these with any PHP
|
utmost importance, we would recommend using one of these with any PHP
|
||||||
application, using Smarty or not.
|
application, using Smarty or not.
|
||||||
|
|
||||||
Q: Why does smarty have a built in cache? Wouldn't it be better to handle this
|
Q: Why does Smarty have a built in cache? Wouldn't it be better to handle this
|
||||||
in a separate class?
|
in a separate class?
|
||||||
A: Smarty's caching functionality is tightly integrated with the template
|
A: Smarty's caching functionality is tightly integrated with the template
|
||||||
engine, making it quite a bit more flexible than a simple caching wrapper.
|
engine, making it quite a bit more flexible than a simple caching wrapper.
|
||||||
@@ -115,8 +115,7 @@ A: Yes. Subscribe by sending an e-mail to subscribe-smarty@lists.ispi.net. This
|
|||||||
Q: Can you change the mailing list so Reply-To sends to the list and not the
|
Q: Can you change the mailing list so Reply-To sends to the list and not the
|
||||||
user?
|
user?
|
||||||
A: Yes we could, but no we won't. Use "Reply-All" in your e-mail client to send
|
A: Yes we could, but no we won't. Use "Reply-All" in your e-mail client to send
|
||||||
to the list.
|
to the list. http://www.unicom.com/pw/reply-to-harmful.html
|
||||||
http://www.unicom.com/pw/reply-to-harmful.html
|
|
||||||
|
|
||||||
|
|
||||||
TROUBLESHOOTING
|
TROUBLESHOOTING
|
||||||
@@ -184,8 +183,7 @@ Q: My ISP did not setup the PEAR repository, nor will they set it up. How do I
|
|||||||
make Smarty run without it?
|
make Smarty run without it?
|
||||||
A: The easiest thing to do is grab all of PEAR and install it locally for your
|
A: The easiest thing to do is grab all of PEAR and install it locally for your
|
||||||
own use. There's nothing that says PEAR must be installed in its default
|
own use. There's nothing that says PEAR must be installed in its default
|
||||||
directory. There won't be a version of Smarty that runs without PEAR, as it
|
directory. There won't be a version of Smarty that runs without PEAR.
|
||||||
dependant on it, and may become moreso in the future.
|
|
||||||
|
|
||||||
Q: Javascript is causing Smarty errors in my templates.
|
Q: Javascript is causing Smarty errors in my templates.
|
||||||
A: Surround your javascript with {literal}{/literal} tags. See the docs.
|
A: Surround your javascript with {literal}{/literal} tags. See the docs.
|
||||||
|
16
INSTALL
16
INSTALL
@@ -12,14 +12,16 @@ libraries is included in your php include_path. Unix users check
|
|||||||
INSTALLATION:
|
INSTALLATION:
|
||||||
|
|
||||||
* copy the Smarty.class.php, Smarty.addons.php, Smarty_Compile.class.php and
|
* copy the Smarty.class.php, Smarty.addons.php, Smarty_Compile.class.php and
|
||||||
Config_File.class.php scripts to a directory that is in your PHP include_path.
|
Config_File.class.php scripts to a directory that is in your PHP include_path,
|
||||||
|
or set the SMARTY_DIR constant and put your class files in this directory.
|
||||||
|
|
||||||
* in the same directory as your php application, create a "templates"
|
* create a "templates" directory, "configs" directory and a "templates_c"
|
||||||
directory, "configs" directory and a "templates_c" directory. Be sure the
|
directory, be sure to set the appropriate directory settings in Smarty for
|
||||||
"templates_c" directory is writable by your web server user (usually nobody).
|
them. If they are located in the same directory as your application, they
|
||||||
chown nobody:nobody templates_c; chmod 700 templates_c
|
shouldn't need to be modified. Be sure the "templates_c" directory is
|
||||||
You can also chmod 777 this directory, but be aware of security issues for
|
writable by your web server user (usually nobody). chown nobody:nobody
|
||||||
multi-user systems.
|
templates_c; chmod 700 templates_c You can also chmod 777 this directory, but
|
||||||
|
be aware of security issues for multi-user systems.
|
||||||
|
|
||||||
* setup your php and template files. A good working example is included to get
|
* setup your php and template files. A good working example is included to get
|
||||||
you started. Also see the QUICKSTART guide for some more examples.
|
you started. Also see the QUICKSTART guide for some more examples.
|
||||||
|
@@ -11,8 +11,7 @@ compile_check, load the page, then turn it back off. This will update the cache
|
|||||||
file with the new content. This is accomplished by maintaining a list of
|
file with the new content. This is accomplished by maintaining a list of
|
||||||
included/loaded templates and config files at the beginning of the cache file.
|
included/loaded templates and config files at the beginning of the cache file.
|
||||||
Therefore it is advisable to remove all cache files after upgrading to 1.4.6
|
Therefore it is advisable to remove all cache files after upgrading to 1.4.6
|
||||||
(although not absolutely necessary, old cache file formats will be skipped of
|
(although not absolutely necessary, old cache files will regenerate)
|
||||||
this check)
|
|
||||||
|
|
||||||
The debug console now has script timing and array values printed. You MUST
|
The debug console now has script timing and array values printed. You MUST
|
||||||
update your debug.tpl file with this version of Smarty. Also, the new debug.tpl
|
update your debug.tpl file with this version of Smarty. Also, the new debug.tpl
|
||||||
|
Reference in New Issue
Block a user