Jhong253
Regular
I like this thing except for one change. It doesn't mention the number of minutes ago the post was posted.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I like this thing except for one change. It doesn't mention the number of minutes ago the post was posted.
I like this thing except for one change. It doesn't mention the number of minutes ago the post was posted.
Yea, I agree. I think anything posted within the last 59 minutes should retain the "xx minutes ago" with the time of post. Also anything posted on the same date as the current one should still be labeled as "today" with the time. My main concern, and the reason I voted, was the posts that have the date listed as "2 weeks ago" etc are not accurate at all. Now I have to look at my clock every time I want to see exactly how long ago something that is recent was posted. I don't know how everyone else feels about this, am I alone with Jhong here?
Also something else was that in a specific forum, there are no dates at all for when a thread was started. Like in the speedcubing forum for example, the only information given is the person who started the topic and the date/time of the last posting, but nothing of when the thread was started.
This would require some modification for sure, and I'm not sure exactly how I'd go about doing it. I will look into it, but I can't guarantee anything soon.I agree with Bob. I still like the "X minutes ago" or "Y hours ago" thing, because it was a good way to get a feel for when things were posted. The reason I like the date format is that for anything over a day ago the "X [unit] ago" style used to be extremely vague, but for dates less than 24 hours ago this isn't a problem since we have at least precision to the nearest hour.



else if ($timediff < 172800)
{
$returndate = $vbphrase['1_day_ago'];
}
else if ($timediff < 604800)
{
$returndate = construct_phrase($vbphrase['x_days_ago'], intval($timediff / 86400));
}
else if ($timediff < 1209600)
{
$returndate = $vbphrase['1_week_ago'];
}
else if ($timediff < 3024000)
{
$returndate = construct_phrase($vbphrase['x_weeks_ago'], intval($timediff / 604900));
}
else
{
$returndate = $datefunc($format, $timestamp_adjusted);
}
}
else
{
$returndate = $datefunc($format, $timestamp_adjusted);
}
else if ($timediff < 172800)
{
$returndate = $vbphrase['1_day_ago'];
$returndate .= ", " . $datefunc($vbulletin->options['timeformat'], $timestamp_adjusted);
}
else if ($timediff < 604800)
{
$returndate = construct_phrase($vbphrase['x_days_ago'], intval($timediff / 86400));
$returndate .= ", " . $datefunc($vbulletin->options['timeformat'], $timestamp_adjusted);
}
else
{
$format = $vbulletin->options['dateformat'] . " " . $vbulletin->options['timeformat'];
$returndate = $datefunc($format, $timestamp_adjusted);
}
}
else
{
$format = $vbulletin->options['dateformat'] . " " . $vbulletin->options['timeformat'];
$returndate = $datefunc($format, $timestamp_adjusted);
}
Can you tell me how I can replicate this error?Bit of a problem, which I hope can be fixed. Sometimes, on things that are a few days old, I will see something like this:
05-05-2009 07:25 PM 07:25 PM
This thread itself, when viewed from the main portal, displays the time twice