It happens mostly when you start a thread otherwise it works as intended.It shouldn't be happening any more, but if you notice it somewhere, let me know so I can check it out.
The unfurl is totally dependent on the source site - nothing in XF can control that.
In this case the page doesn't contain the relevant meta property content.
You can use this checker to confirm that: http://debug.iframely.com/
Same here.I dont know if its just me but since yesterday, every time i come on the site it loads the dark skin at the start for less than half of second, then it goes to light which is my chosen one.
Hm, my default's dark and I don't remember it flickering between light and dark. @Arhu has been making changes due to https://rpgwatch.com/forum/threads/...ht-or-dark-style.50301/page-4#post-1061699796I dont know if its just me but since yesterday, every time i come on the site it loads the dark skin at the start for less than half of second, then it goes to light which is my chosen one.
The first time I click, it brings me to the first post, disregarding the /unread. If I go back and click again (so on the same URL with /unread), it brings me to the last post. Perhaps it would do the same by reloading, I haven't tried.You said something about a timeout and second click. Could it be that your first request to load the page isn't completing fully/properly, but enough to where it marks you as having read the new post(s)? So the second time you try to hit the link, it takes you to the first page?
No, those are threads I visit regularly. But you're right, I had that with a few threads right after we moved and it was fixed by marking the forums as read. The two problems might actually be the same, but I have no insight on how the unread posts are managed, so I honestly don't know.My theory is that it happens with threads that existed before the move, got new posts after the move, but which you have never opened after the move. If that's the case I suppose it will sort itself out over time. If not, we need ways to reproduce it.
So, for me just now, the "unread" jump worked fine for Couch's news thread and didn't work for the Birthday Thread (which I'm fairly sure I haven't visited in a long time).
I found this:I don't think it's a timeout but I don't exclude anything, by default of knowing how it works. Perhaps the specific response to /unread has a built-in timeout and produces the first post when it triggers (though I don't see why they would bother to do that). Then perhaps the 2nd time I try to open the same URL, it doesn't do a time-out because the "last read" data may be cached. It's very far-stretched.
Thanks! We'll see.I found this:
XF 2.1 - "Go to first unread" at the top of a thread will not take one member to any posts that are older than 30 days
I have a member whose oldest posts when navigating to first unread is never more than 30 days old. Other members do not have this issue. Any idea what the cause could be? Thanksxenforo.com
Could this be related? The way I understand it, when you go to a thread with "/unread" and the first unread post is actually older than 30 days, Xenforo doesn't know about it anymore and takes you to the first post...? Very strange, but could that explain your cases?
I changed the value to 60 and we'll see if it helps.
For reference: Setup->Options->Threads, discussions and conversations -> Read marking data lifetime. "This is the number of days to maintain read marking data (such as for threads and forums). Data older than this will always be seen as read."
That is something else. In my experience it jumps to the first post of the thread, not a post that is more recent than 30 days ago.This is related to the "Read marking data lifetime" option. Anything older than that is automatically considered to be read. Even if you've never read anything in a thread, clicking that link will jump you to the first post after that time.
I can say without any hesitation that I have never seen this behaviour.(If we have no knowledge of whether you've read a thread, we hedge our bets and take you to the beginning of the thread. It's possible you may have read it but the data has been cleaned up, so that link roughly helps to jump you to a more recent point.)