re: domain/discover/content-posted/

I noticed that some topics are not updated in this list. I dug around for a common factor, and just performed a test. It appears that if the topic was created more than a year ago, and I add a new post, the topic does not appear in the Posted In list.

I note the following description:

Content I Posted In

Showing all content I posted in and posted in for the last 365 days.

Is that note misleading and this is expected behaviour? Or is there a bug?

If this is expected behaviour, I suggest changing it. This is less than ideal behaviour.

Thanks.

This is a known issue. The way the search index is built, we currently retrieve the most recently created topics in which the member posted, with an upper limit of 800 results. So if you have a particularly active member who's been around for a while, you won't necessarily see all their content.

We do have an open bug report for this, it's something we know we need to fix, but there is no ETA at the moment.

6 hours ago, Esther E. said:

This is a known issue. The way the search index is built, we currently retrieve the most recently created topics in which the member posted, with an upper limit of 800 results. So if you have a particularly active member who's been around for a while, you won't necessarily see all their content.

We do have an open bug report for this, it's something we know we need to fix, but there is no ETA at the moment.

Ah. Thank you for the reply and explanation. So the apparent year cut-off was just coincidence.

Although I admin my community, I do not create that many topics within a year. But I noticed this occurring in a more than 3-years old, still active topic I started. It is an important topic, so I do like to know when there are new replies. Further, I could be mistaken, but neither do I recall receiving notifications for new posts to the topic.

We reported this bug some time ago. Pleased to see it hasn't been forgotten and looking forward to the fix.

It hasn't been forgotten, but will require significant rework, and therefore needs to be scheduled properly.

17 minutes ago, Esther E. said:

It hasn't been forgotten, but will require significant rework, and therefore needs to be scheduled properly.

I will add that I have noticed missing (on site) notifications for some topics. I did not take note of the age of those topics at the time. This might be the explanation. Something for me to watch out for.

Hi @Esther E.

Is there a timeline for fixing this? I started an important topic which remains active well over two years later. But, of course, prior contributors are not receiving notifications when there are new posts.

Is this fixed in 5.1?

Thanks.

13 hours ago, Como said:

Is there a timeline for fixing this

Currently, no. As Esther notes, It's a big thing to resolve.

45 minutes ago, Stuart said:

Currently, no. As Esther notes, It's a big thing to resolve.

Thank you for the reply, @Stuart. But with respect, so is the inability to update members within ongoing topics. Admins by their very role are more likely to exceed the 800 topic limit. But also by their very role, their posts/topics might be more important. Apart from the general inconvenience for all affected accounts/topics, it is a management issue.

25 minutes ago, Como said:

Thank you for the reply, @Stuart. But with respect, so is the inability to update members within ongoing topics. Admins by their very role are more likely to exceed the 800 topic limit. But also by their very role, their posts/topics might be more important. Apart from the general inconvenience for all affected accounts/topics, it is a management issue.

While I understand what you are saying there, the importance doesnt make the resolution to the issue any smaller there

2 hours ago, Marc said:

While I understand what you are saying there, the importance doesnt make the resolution to the issue any smaller there

Yes, I do appreciate that. I just wished to make clear that from a management perspective it is no small issue, and for very active members who make use of long-running support topics.

Thanks, @Marc.