When trying to use the {speedy:set_ttl} with seconds or “2 days”, the ttl to live on the redis item does not get set correctly.

If I use:

{speedy:set_ttl}3600{/speedy:set_ttl}

then the item gets an infinite ttl which was shown by running the following:

127.0.0.1:6379> ttl speedy/redis/default_site/local/news/article/test-cool-stuff/article-test-cool-stuff
returns this value // (integer) -1

If I use:

{speedy:set_ttl}2 days{/speedy:set_ttl}

then the item gets a very large ttl:

127.0.0.1:6379> ttl speedy/redis/default_site/local/news/article/test-cool-stuff/article-test-cool-stuff
returns this value // (integer) 1675041231

Haven’t looked at the method enough to determine what’s wrong, but will on monday.

Here is the simplified version of the channel loop which has a limit of 1:

{exp:speedy:fragment key="article-{segment_3}" tags="news|news-articles" global="no" ttl="900"}
  {exp:channel:entries channel="news" limit="1" track_views="one" disable="pagination|category_fields"}
  	{if "{entry_date format='%F %Y'}" == "{current_time format='%F %Y'}"}
    	   {speedy:set_ttl}3600{/speedy:set_ttl}
       {/if}
{/exp:speedy:fragment}