This shows you the differences between two versions of the page.
|
upgrading [2009/10/16 09:00] Kornel |
upgrading [2024/09/05 07:00] (current) 2605:7980:0:208d::1 1 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | 317 | ||
| + | 317 | ||
| + | |||
| + | |||
| ====== Upgrading from older releases ====== | ====== Upgrading from older releases ====== | ||
| - | These are only changes that could affect existing templates. You'll find all those instructions and additional information about changes/features in [[http://phptal.org/|release annoucements]]. | + | These are only changes that could affect existing templates/installations. You'll find all those instructions and additional information about changes/features in [[http://phptal.org/|release annoucements]]. |
| + | |||
| + | ===== 1.2.2 → 1.3.0 ===== | ||
| + | |||
| + | ''metal:fill-slot'' used outside ''metal:use-macro'' is no longer supported (it used to magically pre-fill slots for later use). Make sure you're using slots as described in the manual. | ||
| + | |||
| + | Removed support for custom code generators using the old ''PHPTAL_Php_Tree'' interface. | ||
| + | |||
| + | ===== 1.2.0 → 1.2.2 ===== | ||
| + | |||
| + | You don't need to ''include''/''require'' files other than ''PHPTAL.php''. You can remove any superfluous ''require''s. | ||
| + | |||
| + | In case autoloading causes any problems and/or you want to use your own autoloader //instead of// PHPTAL's built-in one, execute this after loading ''PHPTAL.php'': | ||
| + | |||
| + | spl_autoload_unregister(array('PHPTAL','autoload')); // ugly workaround | ||
| + | |||
| + | and then call ''PHPTAL::autoload()'' from your autoloader. | ||
| ===== 1.1.14 → 1.2.0 ===== | ===== 1.1.14 → 1.2.0 ===== | ||
| Line 9: | Line 29: | ||
| ==== Entities and encodings ==== | ==== Entities and encodings ==== | ||
| - | The biggest difference is in handling of entities. Entities are now unescaped before passing to expressions, i.e. ''${php:strlen('"')}'' “sees” just the quote character and returns ''1''. In previous versions entities were passed as-is to the expressions (and that example would return ''6''). | + | The biggest difference is in handling of entities. Entities are now unescaped before passing to expressions, i.e. ''${php:strlen('"')}'' “sees” just the quote character and returns ''1''. In previous versions entities were passed as-is to the expressions (and that example would return ''6''). |
| Newly added unescaping of entities can **expose encoding bugs**. Make sure your pages declare document encoding: | Newly added unescaping of entities can **expose encoding bugs**. Make sure your pages declare document encoding: | ||
| For XHTML it's best to send ''Content-Type:application/xhtml+xml;charset=UTF-8'' or ''Content-Type:text/html;charset=UTF-8'' HTTP headers. | For XHTML it's best to send ''Content-Type:application/xhtml+xml;charset=UTF-8'' or ''Content-Type:text/html;charset=UTF-8'' HTTP headers. | ||
| * Don't use ''text/xml'' MIME type, use ''application/xml'' instead. | * Don't use ''text/xml'' MIME type, use ''application/xml'' instead. | ||
| - | In HTML add appropriate ''<meta>'' tag or send ''Content-Type:text/html;charset=UTF-8'' HTTP header. | + | In HTML add appropriate ''&lt;meta&gt;'' tag or send ''Content-Type:text/html;charset=UTF-8'' HTTP header. |
| - | * If you're not using UTF-8 encoding, you must set encoding you use via ''%%$phptal->setEncoding('ISO-8859-…')%%'' (or just switch to UTF-8 already! :) | + | * If you're not using UTF-8 encoding, you must set encoding you use via ''%%$phptal-&gt;setEncoding('ISO-8859-…')%%'' (or just switch to UTF-8 already! :) |
| * Only some 8-bit-based encodings are supported. If your encoding is not supported, you may get away with setting ISO-8859-1 instead. | * Only some 8-bit-based encodings are supported. If your encoding is not supported, you may get away with setting ISO-8859-1 instead. | ||
| Line 22: | Line 42: | ||
| ==== Constants ==== | ==== Constants ==== | ||
| - | * All constants except ''PHPTAL_VERSION'' have been removed. Remove any PHPTAL-specific ''define()''s and use class methods (available in earlier versions too) for configuration (e.g. ''%%$phptal->setPhpCodeDestination('/tmp/phptal/')%%'' for custom temp directory.) | + | * All constants except ''PHPTAL_VERSION'' have been removed. Remove any PHPTAL-specific ''define()''s and use class methods (available in earlier versions too) for configuration (e.g. ''%%$phptal-&gt;setPhpCodeDestination('/tmp/phptal/')%%'' for custom temp directory.) |
| * ''PHPTAL_DIR'' is gone. PHPTAL now temporarily modifies ''include_path'' (this may change in the future). | * ''PHPTAL_DIR'' is gone. PHPTAL now temporarily modifies ''include_path'' (this may change in the future). | ||
| Line 31: | Line 51: | ||
| * XML namespace of ''phptal:*'' attributes has changed from ''%%http://xml.zope.org/namespaces/phptal%%'' to ''%%http://phptal.org/ns/phptal%%''. | * XML namespace of ''phptal:*'' attributes has changed from ''%%http://xml.zope.org/namespaces/phptal%%'' to ''%%http://phptal.org/ns/phptal%%''. | ||
| - | * Comments are required to be well-formed (''%%--%%'' is not allowed in comments.) Comments starting with ''%%<!--!%%'' are stripped from output. | + | * Comments are required to be well-formed (''%%--%%'' is not allowed in comments.) Comments starting with ''%%&lt;!--!%%'' are stripped from output. |
| - | * Duplicate attributes are not allowed and they must be separated with space. ''<b title=""title="">'' is doubly wrong. | + | * Duplicate attributes are not allowed and they must be separated with space. ''&lt;b title=""title=""&gt;'' is doubly wrong. |
| ==== Other issues ==== | ==== Other issues ==== | ||
| Line 42: | Line 62: | ||
| ===== 1.1.x → 1.1.14 ===== | ===== 1.1.x → 1.1.14 ===== | ||
| - | In 1.1.13 translation key like ''%%<p i18n:translate="'żółw'" />%%'' was interpreted as ''%%<p i18n:translate="'<C197><C188><C195><C179><C197><C130>w'">%%'' and you had to use ''msgid "<C197><C188><C195><C179><C197><C130>w"'' in your ''.po'' files. | + | In 1.1.13 translation key like ''%%&amp;lt;p i18n:translate="'żółw'" /&amp;gt;%%'' was interpreted as ''%%&amp;lt;p i18n:translate="'&amp;lt;C197&amp;gt;&amp;lt;C188&amp;gt;&amp;lt;C195&amp;gt;&amp;lt;C179&amp;gt;&amp;lt;C197&amp;gt;&amp;lt;C130&amp;gt;w'"&amp;gt;%%'' and you had to use ''msgid "&amp;lt;C197&amp;gt;&amp;lt;C188&amp;gt;&amp;lt;C195&amp;gt;&amp;lt;C179&amp;gt;&amp;lt;C197&amp;gt;&amp;lt;C130&amp;gt;w"'' in your ''.po'' files. |
| PHPTAL 1.1.14 stops doing this and keys are now left unchanged. The example above would simply expect ''msgid "żółw"'' in the ''.po'' file. | PHPTAL 1.1.14 stops doing this and keys are now left unchanged. The example above would simply expect ''msgid "żółw"'' in the ''.po'' file. | ||
| Line 49: | Line 69: | ||
| $translator = new PHPTAL_GetTextTranslator(); | $translator = new PHPTAL_GetTextTranslator(); | ||
| - | $translator->setLanguage(…); | + | $translator-&amp;gt;setLanguage(…); |
| - | $translator->setCanonicalize(true); // add this line | + | $translator-&amp;gt;setCanonicalize(true); // add this line |
| - | $phptal->setTranslator($translator); | + | $phptal-&amp;gt;setTranslator($translator); |
| + | To upgrade templates, change ''&lt;Cxxx&gt;'' back to bytes. This code snippet will do it: ''%%preg_replace('/&lt;C(\d+)&gt;/e','chr("\1")',$po_file_content)%%'' | ||
| - | To upgrade templates, change ''<Cxxx>'' back to bytes. This code snippet will do it: ''%%preg_replace('/<C(\d+)>/e','chr("\1")',$po_file_content)%%'' | + | 1 |
| + | 1 | ||