I am passing a timestamp into a Smarty Template, and using
Oct 19, 2208
May 28, 2015
Feb 27, 2016
The best way to avoid this is to cast to
int the timestamp. Now it's a numeric
Smarty did some changes in 2.6.10 to use all numeric input values as timestamp, but before was not always the case.
As I can see the first timestamp ends in
2208 and also the year returned for that timestamp is
2208, so I think smarty think it's not a timestamp, but a date formatted somehow.
See more here (smarty doc)