it seems the most problematic issues are
== {php} Tag ==
{php} tags is
deprecated. But it can be enabled with $smarty->allow_php_tag=true.
== Delimiters and whitespace ==
But it can be disable with $smarty->auto_literal = false;
== Unquoted Strings ==
this may be the most problematic ; You can still pass strings without quotes
so long as they contain no special characters. (anything outside of A-Za-z0-9_)
extracted from
http://smarty-php.googlecode.com/svn/tr … _NOTES.txt
Offline
Hi,
For information, the next Debian release will only have smarty3 and not smarty anymore. This means that piwigo will soon be removed from Debian unless a version compatible with smarty3 can be uploaded:
http://bugs.debian.org/672374
Debian plans to do the freeze for the next release during June. So, I'm afraid that piwigo wont be released in the next Debian (wheezy).
Regards,
Vincent
Offline
vdanjean wrote:
For information, the next Debian release will only have smarty3 and not smarty anymore.
This is exactly after an email from the Piwigo package maintainer in Debian that I wrote [Forum, post 130057 by plg in topic 16742] Smarty 3 upgrade
Offline
Actually yes, Piwigo will probably be removed from Debian for version 7. The best we can do is to update for Piwigo 2.5 which can't be released before october/november 2012.
Offline
What will this mean to the average user who upgrades to the latest Debian? Will their Piwigo server stop working? Should they be warned not to upgrade Debian until Piwigo changes to Smarty3?
Offline
you could upgrade it and test with
$smarty->allow_php_tag=true;
$smarty->auto_literal = false;
it might be ok
Offline
Billr wrote:
What will this mean to the average user who upgrades to the latest Debian? Will their Piwigo server stop working? Should they be warned not to upgrade Debian until Piwigo changes to Smarty3?
It only concerns users who have installed Piwigo with the Debian package system. Actually I think it's a tiny part of Piwigo users. I use Debian on my servers. I don't use the Debian package to install Piwigo.
Offline
flop25 wrote:
you could upgrade it and test with
$smarty->allow_php_tag=true;
$smarty->auto_literal = false;
it might be ok
Well, I don't want this for Piwigo 2.4 BUT I can tell the Debian maintainer (nicolas) to give a try to this solution.
Offline
smarty 2 has been removed from testing and will probably not enter unstable. If upstream (piwigo team) do not provided an official release with smarty 3, I'm afraid I will have to patch piwigo with flop25 propositon.
Offline
nicolas wrote:
If upstream (piwigo team) do not provided an official release with smarty 3, I'm afraid I will have to patch piwigo with flop25 propositon.
This is exactly the suggestion :-) if it avoids to remove Piwigo from Debian 7, it's a very good solution.
Offline
Piwigo 2.6 is now under preparation. Considering Statistics on Wordpress.org, PHP 5.2+ = 99.4%. Can we upgrade to smarty 3 for Piwigo 2.6?
Offline
As I said Yes! :-)
Offline
One problem with PHP 5.2 : the hosting provider Free.fr does not support it. It might seem surprising to block such an enhancement for just a single hosting provider, but we have many users hosted on Free.fr.
Wordpress 3.2+ requires PHP 5.2.4. Free.fr users can only upgrade up to Wordpress 3.1 (latest release in 2011)
Questions:
1) how much is PHP 5.2 required by Smarty 3? is it just a missing function or is it completely blocked?
2) considering that Free.fr is already not very welcoming for Piwigo users (small upload_max_filesize, no automatic install/upgrade, no 1-click install for plugins, etc.), how long can we afford to make specific code for Free.fr?
Offline
Seems that's a big deal : http://www.smarty.net/forums/viewtopic. … 8337a7618e
Offline