Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Kócsó Balázs
authored and
testbot
committed
Oct 14, 2022
0 parents
commit 7c1bee9
Showing
234 changed files
with
42,038 additions
and
0 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
|
||
|
||
Starting with Smarty 3.1.21 Composer has been configured to load the packages from github. | ||
|
||
******************************************************************************* | ||
* * | ||
* NOTE: Because of this change you must clear your local composer cache with * | ||
* the "composer clearcache" command * | ||
* * | ||
******************************************************************************* | ||
|
||
To get the latest stable version use | ||
"require": { | ||
"smarty/smarty": "~3.1" | ||
} | ||
in your composer.json file. | ||
|
||
To get the trunk version use | ||
"require": { | ||
"smarty/smarty": "~3.1@dev" | ||
} | ||
|
||
The "smarty/smarty" package will start at libs/.... subfolder. | ||
|
||
To retrieve the development and documentation folders add | ||
"require-dev": { | ||
"smarty/smarty-dev": "~3.1@dev" | ||
} | ||
|
||
If you are using (include) the composer generated autoloader.php which is located | ||
in the /vendor folder it is no longer needed to require the Smarty.class.php file. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,91 @@ | ||
3.1.3" | ||
New tags for inheritance parent and chilD | ||
{parent} == {$smarty.block.parent} | ||
{child} == {$smarty.block.child} | ||
Both tags support the assign attribute like | ||
{child assign=foo} | ||
|
||
3.1.31 | ||
New tags for inheritance parent and child | ||
{block_parent} == {$smarty.block.parent} | ||
{block_child} == {$smarty.block.child} | ||
|
||
Since 3.1.28 you can mix inheritance by extends resource with the {extends} tag. | ||
A template called by extends resource can extend a subtemplate or chain buy the {extends} tag. | ||
Since 3.1.31 this feature can be turned off by setting the new Smarty property Smarty::$extends_recursion to false. | ||
|
||
3.1.28 | ||
Starting with version 3.1.28 template inheritance is no longer a compile time process. | ||
All {block} tag parent/child relations are resolved at run time. | ||
This does resolve all known existing restrictions (see below). | ||
|
||
The $smarty::$inheritance_merge_compiled_includes property has been removed. | ||
Any access to it is ignored. | ||
|
||
New features: | ||
|
||
Any code outside root {block} tags in child templates is now executed but any output will be ignored. | ||
|
||
{extends 'foo.tpl'} | ||
{$bar = 'on'} // assigns variable $bar seen in parent templates | ||
{block 'buh'}{/block} | ||
|
||
{extends 'foo.tpl'} | ||
{$bar} // the output of variable bar is ignored | ||
{block 'buh'}{/block} | ||
|
||
{block} tags can be dynamically en/disabled by conditions. | ||
|
||
{block 'root'} | ||
{if $foo} | ||
{block 'v1'} | ||
.... | ||
{/block} | ||
{else} | ||
{block 'v1'} | ||
.... | ||
{/block} | ||
{/if} | ||
{/block} | ||
|
||
{block} tags can have variable names. | ||
|
||
{block $foo} | ||
.... | ||
{/block} | ||
|
||
Starting with 3.1.28 you can mix inheritance by extends resource with the {extends} tag. | ||
A template called by extends resource can extend a subtemplate or chain buy the {extends} tag. | ||
|
||
NOTE There is a BC break. If you used the extends resource {extends} tags have been ignored. | ||
|
||
THE FOLLOWING RESTRICTIONS ARE NO LONGER EXISTING: | ||
In Smarty 3.1 template inheritance is a compile time process. All the extending of {block} tags | ||
is done at compile time and the parent and child templates are compiled in a single compiled template. | ||
{include} subtemplate could also {block} tags. Such subtemplate could not compiled by it's own because | ||
it could be used in other context where the {block} extended with a different result. For that reasion | ||
the compiled code of {include} subtemplates gets also merged in compiled inheritance template. | ||
|
||
Merging the code into a single compile template has some drawbacks. | ||
1. You could not use variable file names in {include} Smarty would use the {include} of compilation time. | ||
2. You could not use individual compile_id in {include} | ||
3. Separate caching of subtemplate was not possible | ||
4. Any change of the template directory structure between calls was not necessarily seen. | ||
|
||
Starting with 3.1.15 some of the above conditions got checked and resulted in an exception. It turned out | ||
that a couple of users did use some of above and now got exceptions. | ||
|
||
To resolve this starting with 3.1.16 there is a new configuration parameter $inheritance_merge_compiled_includes. | ||
For most backward compatibility its default setting is true. | ||
With this setting all {include} subtemplate will be merge into the compiled inheritance template, but the above cases | ||
could be rejected by exception. | ||
|
||
|
||
If $smarty->inheritance_merge_compiled_includes = false; {include} subtemplate will not be merged.You must now manually merge all {include} subtemplate which do contain {block} tags. This is done by setting the "inline" option. | ||
{include file='foo.bar' inline} | ||
|
||
1. In case of a variable file name like {include file=$foo inline} you must use the variable in a compile_id $smarty->compile_id = $foo; | ||
2. If you use individual compile_id in {include file='foo.tpl' compile_id=$bar inline} it must be used in the global compile_id as well $smarty->compile_id = $bar; | ||
3. If call templates with different template_dir configurations and a parent could same named child template from different folders | ||
you must make the folder name part of the compile_id. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,179 @@ | ||
Smarty: the PHP compiling template engine | ||
|
||
This library is free software; you can redistribute it and/or | ||
modify it under the terms of the GNU Lesser General Public | ||
License as published by the Free Software Foundation; either | ||
version 3.0 of the License, or (at your option) any later version. | ||
|
||
This library is distributed in the hope that it will be useful, | ||
but WITHOUT ANY WARRANTY; without even the implied warranty of | ||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. | ||
|
||
See the GNU Lesser General Public License below for more details. | ||
|
||
|
||
GNU LESSER GENERAL PUBLIC LICENSE | ||
Version 3, 29 June 2007 | ||
|
||
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> | ||
Everyone is permitted to copy and distribute verbatim copies | ||
of this license document, but changing it is not allowed. | ||
|
||
|
||
This version of the GNU Lesser General Public License incorporates | ||
the terms and conditions of version 3 of the GNU General Public | ||
License, supplemented by the additional permissions listed below. | ||
|
||
0. Additional Definitions. | ||
|
||
As used herein, "this License" refers to version 3 of the GNU Lesser | ||
General Public License, and the "GNU GPL" refers to version 3 of the GNU | ||
General Public License. | ||
|
||
"The Library" refers to a covered work governed by this License, | ||
other than an Application or a Combined Work as defined below. | ||
|
||
An "Application" is any work that makes use of an interface provided | ||
by the Library, but which is not otherwise based on the Library. | ||
Defining a subclass of a class defined by the Library is deemed a mode | ||
of using an interface provided by the Library. | ||
|
||
A "Combined Work" is a work produced by combining or linking an | ||
Application with the Library. The particular version of the Library | ||
with which the Combined Work was made is also called the "Linked | ||
Version". | ||
|
||
The "Minimal Corresponding Source" for a Combined Work means the | ||
Corresponding Source for the Combined Work, excluding any source code | ||
for portions of the Combined Work that, considered in isolation, are | ||
based on the Application, and not on the Linked Version. | ||
|
||
The "Corresponding Application Code" for a Combined Work means the | ||
object code and/or source code for the Application, including any data | ||
and utility programs needed for reproducing the Combined Work from the | ||
Application, but excluding the System Libraries of the Combined Work. | ||
|
||
1. Exception to Section 3 of the GNU GPL. | ||
|
||
You may convey a covered work under sections 3 and 4 of this License | ||
without being bound by section 3 of the GNU GPL. | ||
|
||
2. Conveying Modified Versions. | ||
|
||
If you modify a copy of the Library, and, in your modifications, a | ||
facility refers to a function or data to be supplied by an Application | ||
that uses the facility (other than as an argument passed when the | ||
facility is invoked), then you may convey a copy of the modified | ||
version: | ||
|
||
a) under this License, provided that you make a good faith effort to | ||
ensure that, in the event an Application does not supply the | ||
function or data, the facility still operates, and performs | ||
whatever part of its purpose remains meaningful, or | ||
|
||
b) under the GNU GPL, with none of the additional permissions of | ||
this License applicable to that copy. | ||
|
||
3. Object Code Incorporating Material from Library Header Files. | ||
|
||
The object code form of an Application may incorporate material from | ||
a header file that is part of the Library. You may convey such object | ||
code under terms of your choice, provided that, if the incorporated | ||
material is not limited to numerical parameters, data structure | ||
layouts and accessors, or small macros, inline functions and templates | ||
(ten or fewer lines in length), you do both of the following: | ||
|
||
a) Give prominent notice with each copy of the object code that the | ||
Library is used in it and that the Library and its use are | ||
covered by this License. | ||
|
||
b) Accompany the object code with a copy of the GNU GPL and this license | ||
document. | ||
|
||
4. Combined Works. | ||
|
||
You may convey a Combined Work under terms of your choice that, | ||
taken together, effectively do not restrict modification of the | ||
portions of the Library contained in the Combined Work and reverse | ||
engineering for debugging such modifications, if you also do each of | ||
the following: | ||
|
||
a) Give prominent notice with each copy of the Combined Work that | ||
the Library is used in it and that the Library and its use are | ||
covered by this License. | ||
|
||
b) Accompany the Combined Work with a copy of the GNU GPL and this license | ||
document. | ||
|
||
c) For a Combined Work that displays copyright notices during | ||
execution, include the copyright notice for the Library among | ||
these notices, as well as a reference directing the user to the | ||
copies of the GNU GPL and this license document. | ||
|
||
d) Do one of the following: | ||
|
||
0) Convey the Minimal Corresponding Source under the terms of this | ||
License, and the Corresponding Application Code in a form | ||
suitable for, and under terms that permit, the user to | ||
recombine or relink the Application with a modified version of | ||
the Linked Version to produce a modified Combined Work, in the | ||
manner specified by section 6 of the GNU GPL for conveying | ||
Corresponding Source. | ||
|
||
1) Use a suitable shared library mechanism for linking with the | ||
Library. A suitable mechanism is one that (a) uses at run time | ||
a copy of the Library already present on the user's computer | ||
system, and (b) will operate properly with a modified version | ||
of the Library that is interface-compatible with the Linked | ||
Version. | ||
|
||
e) Provide Installation Information, but only if you would otherwise | ||
be required to provide such information under section 6 of the | ||
GNU GPL, and only to the extent that such information is | ||
necessary to install and execute a modified version of the | ||
Combined Work produced by recombining or relinking the | ||
Application with a modified version of the Linked Version. (If | ||
you use option 4d0, the Installation Information must accompany | ||
the Minimal Corresponding Source and Corresponding Application | ||
Code. If you use option 4d1, you must provide the Installation | ||
Information in the manner specified by section 6 of the GNU GPL | ||
for conveying Corresponding Source.) | ||
|
||
5. Combined Libraries. | ||
|
||
You may place library facilities that are a work based on the | ||
Library side by side in a single library together with other library | ||
facilities that are not Applications and are not covered by this | ||
License, and convey such a combined library under terms of your | ||
choice, if you do both of the following: | ||
|
||
a) Accompany the combined library with a copy of the same work based | ||
on the Library, uncombined with any other library facilities, | ||
conveyed under the terms of this License. | ||
|
||
b) Give prominent notice with the combined library that part of it | ||
is a work based on the Library, and explaining where to find the | ||
accompanying uncombined form of the same work. | ||
|
||
6. Revised Versions of the GNU Lesser General Public License. | ||
|
||
The Free Software Foundation may publish revised and/or new versions | ||
of the GNU Lesser General Public License from time to time. Such new | ||
versions will be similar in spirit to the present version, but may | ||
differ in detail to address new problems or concerns. | ||
|
||
Each version is given a distinguishing version number. If the | ||
Library as you received it specifies that a certain numbered version | ||
of the GNU Lesser General Public License "or any later version" | ||
applies to it, you have the option of following the terms and | ||
conditions either of that published version or of any later version | ||
published by the Free Software Foundation. If the Library as you | ||
received it does not specify a version number of the GNU Lesser | ||
General Public License, you may choose any version of the GNU Lesser | ||
General Public License ever published by the Free Software Foundation. | ||
|
||
If the Library as you received it specifies that a proxy can decide | ||
whether future versions of the GNU Lesser General Public License shall | ||
apply, that proxy's public statement of acceptance of any version is | ||
permanent authorization for you to choose that version for the | ||
Library. |
Oops, something went wrong.