Cannot mark as read one of my watched threads [MERGED]

[zarmanto]

... Something, but no, no response whatsoever ... hence my comment.

Maybe you and I have a different interpretation of who qualifies as an "admin"... but by my count, there are about thirty or so posts by people with some form of the "Staff member" badge on their account, the two latest of which are both dated 7/17 -- only a couple of weeks ago. They are clearly aware of the issue, and tracking it right alongside the rest of us. Personally, I feel like that's much better engagement than I've gotten at other websites where I've participated.

 

[Sital]

the issue exists for over 1 year, site owners/admins have been ping'd multiple times by multiple people. There have been theories tossed around on what the issue is.
All that I and others have asked for is an acknowledgement of the issue and some explanation of what the root cause might be. Something, but no, no response whatsoever ... hence my comment.

Exactly right. Some acknowledgement would be nice.

@zarmanto they could use a different product, since this forum is the only one of many that I visit that has this problem. This is pathetic.

 

[jz0309]

Maybe you and I have a different interpretation of who qualifies as an "admin"... but by my count, there are about thirty or so posts by people with some form of the "Staff member" badge on their account, the two latest of which are both dated 7/17 -- only a couple of weeks ago. They are clearly aware of the issue, and tracking it right alongside the rest of us. Personally, I feel like that's much better engagement than I've gotten at other websites where I've participated.

from 4 months ago ...

so we have some sort of indirect acknowledgement that the issue exists, but nothing else ...

 

[Sital]

from 4 months ago ...
View attachment 2533270

so we have some sort of indirect acknowledgement that the issue exists, but nothing else ...

So he was going to do something 4 months ago...as I said, pathetic.

 

[svenmany]

Maybe you and I have a different interpretation of who qualifies as an "admin"... but by my count, there are about thirty or so posts by people with some form of the "Staff member" badge on their account, the two latest of which are both dated 7/17 -- only a couple of weeks ago. They are clearly aware of the issue, and tracking it right alongside the rest of us. Personally, I feel like that's much better engagement than I've gotten at other websites where I've participated.

Those posts are from staff members who don't seem involved in addressing the problem. They are just chiming in as users who have the same problem as the rest of us.

I do wonder why we've gotten no feedback about what's being done to address it. At this point we don't even know if the vendor has been contacted. I have a feeling something serious is going on and there's nothing safe to say about it. Perhaps the vendor is unresponsive or incompetent and Arn is trying to figure out next steps.

 

[zarmanto]

I decided to try a different approach to understanding this problem: I went over to post a query of my own directly to the XenForo support forum. Turns out someone else beat me to it, having had the same thought way back in January -- and someone else in that forum actually seemed more willing to offer insights at that time than the moderators were when I resurfaced the issue. (Perhaps it didn't help that I linked to a thread in which svenmany had just suggested that they might be incompetent... but whatever.)

The existence of the previous poster's question happened to be somewhat convenient on two levels; obviously it gave me the answer that the previous respondent had provided at that time -- which was that they believe the issue isn't likely to be their code, but rather, something in the backend database (as speculated earlier in this thread) -- but it also gave me an unexpected opportunity to test their assertion. Since that thread was posted well beyond the one month dormancy period that seems to trigger the problem, I specifically looked for the bug to occur on XenForo's own forum in that very thread, after I posted to it. (I know, I know... it was somewhat sneaky and underhanded -- but frankly, I'm okay with that, especially since they weren't even open to speculating on the issue.) Aaaaaand... interestingly, the issue did not occur on their instance of the forum.

I'm somewhat hesitant to speculate further on the core cause... but it seems to me that it would royally suck to debug if the issue is indeed in the database. Is it too optimistic to hope that maybe the MacRumors instance of XenForo is running on an older copy of their codebase, and just needs an update?