I've been getting a new error message since today, even though I haven't changed anything anywhere.
It is reported at the very bottom of the index page even when logged out, and in the admin centre this is displayed in the error log:
Type of error: Undefined
Warning: Undefined array key "time"
302 echo '
303 <li class="board_row">
304 <h3 class="ic_section_header">
305 ', $context['show_stats'] ? '<a href="' . $scripturl . '?action=stats" title="' . $txt['more_stats'] . '"><i class="icon i-pie-chart"></i>' . $txt['forum_stats'] . '</a>' : $txt['forum_stats'], '
307 <p class="inline">
308 ', $context['common_stats']['boardindex_total_posts'], '', !empty($settings['show_latest_member']) ? ' - ' . $txt['latest_member'] . ': <strong> ' . $context['common_stats']['latest_member']['link'] . '</strong>' : '', ' - ', $txt['most_online_today'], ': ', comma_format($modSettings['mostOnlineToday']), '<br />
309 ', (!empty($context['latest_post']) ? $txt['latest_post'] . ': <strong>"' . $context['latest_post']['link'] . '"</strong> ( ' . $context['latest_post']['time'] . ' )' : ''), ' - <a href="', $scripturl, '?action=recent">', $txt['recent_view'], '</a>
What's not longer correct there?
Looking at the code I don't have a quick answer as to why that may be suddenly occurring. Is the latest post on a child board or recycle board or other special board?
You can change line 309 to be:
', (!empty($context['latest_post']) ? $txt['latest_post'] . ': <strong>"' . $context['latest_post']['link'] . '"</strong> ( ' . ($context['latest_post']['time'] ?? '') . ' )' : ''), ' - <a href="', $scripturl, '?action=recent">', $txt['recent_view'], '</a>
and that should top the error.
Thanks, that helped and the error messages are now gone.
I had posted in a child child board. A normal text post that contained a link. Which is actually nothing unusual and I have done several times before.
As I had also noticed after posting here yesterday, the error had also paralyzed the scroll/jump down arrow on the index page. Just there. It didn't work anymore, but the arrow up did. Now everything works there again, too. :)
Thanks for the extra details ... I'll do some more testing on nested boards and see if I can see reproduce the exact error. Glad the quick fix got you going again :D