- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I've been getting the above message in every post for a couple of weeks now, but only while being logged in. It occurs consistently on different (Windows) computers and with different browsers (Chrome version 85.0.4183.83, Edge).
Here's a screenshot:
In the HTML source code it says:
class="lia-widget-not-found"
Do I need to install or update something to get that "lia widget" or is it perhaps blocked by my antivirus software?
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi @FreelanceReinh,
This problem was our fault. I fixed it.
The cause was some incorrect code in displaying the "Posted" date. We have two modes: relative (friendly) dates like "Posted on Thursday" and absolute dates like "Posted on 09-03-2020 3:35 PM". Which you see depends on your preferences, as set in your Settings under the Preferences->Display tab:
Default is "Relative", but anyone who set this to "Absolute" would have seen the same problem as you. I had code that contained an error in that case. So thanks for speaking up!
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi @FreelanceReinh,
This problem was our fault. I fixed it.
The cause was some incorrect code in displaying the "Posted" date. We have two modes: relative (friendly) dates like "Posted on Thursday" and absolute dates like "Posted on 09-03-2020 3:35 PM". Which you see depends on your preferences, as set in your Settings under the Preferences->Display tab:
Default is "Relative", but anyone who set this to "Absolute" would have seen the same problem as you. I had code that contained an error in that case. So thanks for speaking up!
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chris,
Thank you very much for fixing this so quickly. I like the "absolute" timestamps, especially if they show my local time, which is the case (but wasn't always in the past). So, thanks for that earlier fix too.