Since a few days ago members started reporting that the „Unread Content“ isn't working as intended:

Topics show up not once as intended but several times.

The strange thing:

• This happens in all of my communities.
• I didn't change a thing
• Communities are running different versions of IPB (4.5.4 / 4.6.6 / 4.6.9) and thus Elastic Search (6.5.4 / 7.10.2)
• I'm using Bonsai as search provider – thus my guess is that the problem is on their side.

Some more findings

• Error Log shows no entries.
• I switched one of my smaller communities to mySQL search and the issue was gone
• After rebuilding the search index is issue is gone but shows up after some new member posts

My current guess:

• The problem is related to ElasticSearch, independent from IPB or ES version
• It has something to do with the update process
• I think it's more likely that the problem is with Bonsai than with IPB

Any ideas where to dig or how to ask at the Bonsai support?

TIA

Andreas

 

 

My first bit of advice here would be to ensure all are updated to the latest release. Then with regards the elastic issue, we would need to take a look. If you can let us know which site as an example, we can take a look

Good example is this one:

https://www.fuji-x-forum.de/discover/unread/

Access information stored in Client Area

Before we continue here, could I ask when it was that you run the reindexing? If you havent already, please reindex after upgrading to 4.6.9

Already done.

Update was two days ago, search index rebuild directly after update.

Andreas

@Marc Stridgen

Any news on this? Or are you waiting for input from my side?

Andreas

I have just created a ticket for you on this so we can take a closer look at it for you

Update:

With help from the IPB support I found out that the problem was on Bonsai’s (ElasticSearch provider) side:

Bonsai quietly stopped support for the „update by query“ command for their smaller packages.

Took me weeks to find out, annoyed my members.

Their suggestion is to upgrade to their business packages with price tags starting at $700.

My summary: Do not use Bonsai for Invision.

Andreas

3 hours ago, NZyan said:

Update:

With help from the IPB support I found out that the problem was on Bonsai’s (ElasticSearch provider) side:

Bonsai quietly stopped support for the „update by query“ command for their smaller packages.

Took me weeks to find out, annoyed my members.

Their suggestion is to upgrade to their business packages with price tags starting at $700.

My summary: Do not use Bonsai for Invision.

Andreas

Thank you for coming back to let us know

1 minute ago, Marc Stridgen said:

Thank you for coming back to let us know

My pleasure. And thanks for the IPB support – by you, Daniel and Stuart!