It seems like pretty much everybody runs into an issue with {relative_date} where it pulls from the outer {exp:channel:entries} loop, rather than the {exp:twitter:*} loop. This causes confusion, because it looks like EE_Twitter is giving back a horribly formatted string, when in fact that blame falls squarely on ExpressionEngine. Preventing this collision is also pretty much the only reason anybody uses the prefix= parameter.
So, EE_Twitter should expose a different tag (open to what it should be called) instead of {relative_date}. We should, however, keep {relative_date} around for backwards compatibility.
It seems like pretty much everybody runs into an issue with
{relative_date}where it pulls from the outer{exp:channel:entries}loop, rather than the{exp:twitter:*}loop. This causes confusion, because it looks like EE_Twitter is giving back a horribly formatted string, when in fact that blame falls squarely on ExpressionEngine. Preventing this collision is also pretty much the only reason anybody uses theprefix=parameter.So, EE_Twitter should expose a different tag (open to what it should be called) instead of
{relative_date}. We should, however, keep{relative_date}around for backwards compatibility.