Matt

There is no limit right now. I'll add it to our internal tracking.

I'm not sure why this happened. It's possible an upgrade removed some of the metadata from the template row which allows it to be used for specific database views.

The most common reason for a CSRF failure would be a change of session ID. Have you noticed any issues with sessions recently?

That reminds me, I need to search the database for ... something.

Oh.. "Ads". I've got to admit my mind was racing.

Probably Zapier. It reduces the amount of code I have to write.

If you want to get really technical, there's this: https://konstantin.blog/2021/redis-vs-memcached-vs-file_get_contents/ We use Redis on our infrastructure because it's a great object cache and as we have thousands of connections to MySQL a second, it helps reduce load there. Redis is its own instance, and not taking resources from a single server.

It's a complicated question to answer without seeing more site specifics. Generally speaking, MySQL is fine. The queries are fast and lightweight so shouldn't cause any real increase in load. If you simply install Redis on the same server as MySQL then you won't gain a huge amount (perhaps a little speed but nothing earth shattering). If you have a busy site, then Redis is a good option as it offloads I/O to MySQL which can be beneficial at scale. In that case, then definitely use Redis for both caching and data storage with the caveat that you need to manage server resources to ensure giving Redis RAM doesn't starve MySQL or http.

Unfortunately, you'll need to upgrade ES after you've upgraded Invision Community. Around ES 7.7, they changed the JSON parser which previously was less rigid in the array structures it allowed. The new parser is more strict, which means there are code changes in 4.6.9 to fix those issues in 7.7 of greater.

Thanks. It’s a test post in a test forum. I can fix this tomorrow.

SELECT * will return all the columns of each row into memory, but it won't put any additional strain on the MySQL server. When you add DISTINCT(*) you are asking MySQL to create a temporary table (either in memory or on disk) where it puts all the results without the distinct, then filters them to only return the distinct items. It may also disrupt the optimiser which means that indexes that can be used to move the pointer very quickly through the table are not used, so instead MySQL has to look at each row, only to discard it as there is no match.

I'm on Julia's site and the default community page is streams, so did you change that recently Julia?

I'm confused, the page at /community/ is totally different from /community/store/ - why would the search engine say they are duplicates?

It's not a bug though 😕 I know you need this specific thing, but it's not enough to warrant a change to our core code when there is a better alternative. No, it doesn't. 😀

Modifying getItemsWithPermission() fills me with overwhelming anxiety. 😃 I recommend a sub query, it negates the need to hook onto the count(*).

Just replied to the open ticket, but it's all fixed.

If we nofollow these links, then we reduce the routes into the content and increase the crawl depth, which is also bad. Once you are logged in, the link works as expected. If your guests are complaining, just get them to sign up. It takes just a few clicks with the available sign up options.

No, Opensearch uses the last ES open source version which was 7.10. I would't expect things to change dramatically until ES moves to v8 as their stable branch. We will cross that bridge if/when we get to it. 😄 Worth nothing, that if we offer an ES service ourselves, it'll likely be Opensearch we use.

Webooks, APIs and Zapier remain a core part of our current development cycle. I have nothing specific to announce at this moment, but that doesn't mean it's dropped off our plate. 🙂

Yes. I didn’t see any alternative to be honest. You may be able to get away with editing content/search/elastic/index and dropping the min version constant but there are inconsistencies on elastic search indexes between major versions. I felt it better to focus on the stable branch.

Yes, the minimum version will be set to 7.2. We will be issuing an ACP bulletin on this early next week ahead of the beta.

That's AW. I would expect it'll take weeks, if not months for Google to react to the changes. It's got a lot of sites to index. Google is as Google does.