Jump to content

Matt

Management
  • Posts

    70,143
  • Joined

  • Last visited

  • Days Won

    649

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by Matt

  1. Yes, lots of thoughts. We want to do it but there's a few things to consider such as our entire website is Pages and there will need to be minor CSS tweaks. We also link up with the client area (which will be on v4 for a while) along with a bucket of customisations for various things. It's on our list but not as simple as just running the upgrader.
  2. It's not about fobbing you off, it's just nothing significant changed between .18 and .19, so there's little we can offer in terms of advice. Personally, I've found MariaDb less efficient than vanilla MySQL 8.x which we generally optimise for as it's the most used MySQL variant. Looking at what you've shared, the query to fetch the comments is fine. It takes virtually no time, and the explain is clean in that there are no temporary tables or file sorts. The process list shows MySQL waiting 111 seconds for 'sending data' which is a bit misleading as it's still likely scanning the disk for data due to the buffer pool either not being primed or being full but it looks more like slow disk access or network latency than a slow query. But it's something you'd need to discuss with your host. I understand the frustration of "but nothing has changed" and can only tell you some of us have been woken in the night to deal with something even though nothing has changed. The alternative is for one of us to debug your MySQL and web servers to identify the problem but that is beyond technical support for our product.
  3. Which version were you on previously? We changed how offsets are handled in large data sets when getting comments in December 2023. We removed an old optimisation in Content/Item.php in April 2024 that was causing a lot of issues with newer versions of MySQL.
  4. That is a standard query to get posts. We have Cloud clients with over over 25,000 pages and it loads just fine. It's likely either a MariaDb issue, or an optimisation issue but the explain is clean and is what we'd expect. Please contact your host for more advice.
  5. I can see all your thumbnails on desktop and mobile.
  6. Those conferencing tools are exactly why we built Live Topics. You are not talking about an open ended chat box, but rather a focused time-limited reason for people to be online at the same time ready and willing to participate. Invision Community 5 (Cloud) has realtime features for showing replies and reactions making it closer to chat than a topic. It wouldn't take too much imagination to theme a forum to look more streamlined and leverage the real time features to provide more of a chat-like experience.
  7. We still retain the findComment method for areas which we have no idea about page numbers (widgets, etc) but you should see the new links when sharing links from posts.
  8. We can renew it one more time. Pretty soon we're going to have to cull all these demos as we move towards the final release.
  9. tl;dr we chose a fixed range of colours that we adapt based on if you are using light or dark mode. Adding any colours may mean posts are illegible on either light or dark mode.
  10. It's a bit too broad of a question to answer with any real insight. What is it you want to do?
  11. Should be fixed in an hour or so. Thanks for your patience.
  12. It's removed in Beta 5.
  13. Beta 5 is out, and you can blame Mick for the title of this post. 😅 If you're under 40, you'll have no idea what that gif is all about, don't worry. It's just an ancient movie from the before times. Anyway, Beta 5 is working its way through the cloud system and will be available in your AdminCP shortly. As always, the full change log is here: https://invisioncommunity.com/release-notes-v5/ Thanks!
  14. Matt

    5.0.0 Beta 4

    Changed Current Release to No
  15. This is the latest version of Invision Community 5.
  16. Sorry. It’ll be tomorrow now.
  17. It's getting a bit late here in the UK. We'll get it out Monday.
  18. Ehren, you look different today.
  19. We have intentionally not added a live chat feature, at least not yet. It would be fairly simple to do as we have the same functionality for live topics. However, Live Chat can drain away content from your forum and make what could be useful rich topics for future people (and Google/SEO) to enjoy more vapid and disposable. Our solution was Live Topics which gave you a time limited chat feature that can convert into a normal topic upon completion so that content isn't lost. I think the case for live chat as a constant companion is weak honestly. If you have a really busy forum then you do not need an extra place for people to talk, and if you have a really quiet forum, you won't have enough people in a live chat area at the same time to do anything constructive. Chat boxes used to be a popular add-on but in most cases, it was generally populated with "Hello?" messages from weeks ago. If people want to chat, they're going to do it via a well trodden path in their routine, that could be Discord, WhatsApp or snapchat. They're unlikely to deviate from these routines because of a chat box on a forum they may visit daily or weekly. This is why we built Live Topics. It gives you an event based platform that people will make time for to come together for a short fixed time to discuss a topic live.
  20. This is wonderful Jimi! I'll get this out across our social channels.
  21. I'm going to tag in our CSS maestro @Ehren for assistance.
  22. A merge tags feature wouldn't be a bad idea for when people change their minds.
  23. v4.* you can keep using MyISAM. It's only version 5 that enforces InnoDB.
  24. Invision Community 5 is a fresh start on many things, and we wanted to remove a lot of old features with roots back into the early 2000s. Security through obscurity was pretty much all we had back then, but now there are better tools including firewalls, 2FA and VPN/IP address restriction. I'd always recommend 2FA for all admin accounts. Just hiding the admin folder is a weak way to secure it. It means that if you accidentally paste the link, or it appears as a referrer in access logs or someone figures out the folder name then you've lost that element of security. It's a bit like locking the door and placing the key under the plant pot. I know all these changes can be overwhelming which is why we're making every effort to communicate them to you and give you as much runway as possible to migrate over.
×
×
  • Create New...