TDBF

It’s been that way as long as I can remember!

It works on a different principle. IP blocking only works with the registration form. The user can still browse the forum, e.g. by logging out of the account or opening it in incognito mode, but he will not be able to create a new account from this IP.
The IP block is useless, if someone has a changing IP, all you need to do is reset the router or the Internet connection itself and you can create an account again.

Ban by IP prevents any username from signing in.  To be honest, blocking by IP nowadays is almost useless. I can switch IP addresses with my ISP with the click of a button, or use a VPN, or switch to a mobile device and wander around, etc. 
The behavior of blocking only logged in accounts has been like this as long as I can remember. To be honest, if you want to block the entire IP… don’t try to use software. Either use the server (like htaccess or a server firewall like csf) or with a WAF (like cloudflare).

I had a subscription plan in the past that has been deleted. There were no active subscribers on the plan as I removed it. Now, the users who purchased this subscription in the past cannot buy another subscription on my site. They do not see the button “Buy”.
I went and removed all previous expired subscriptions from one user. He has literally nothing in his client account now. But the user still cannot buy any subscription on my site. Is there anything else I should do, to allow users with a “deleted” subscription plan in the past to buy one that exists? 
I know that I can create an invoice manually, but I would rather go through all inactive subscribes of the deleted plan and allow all of them to buy on my site again. 
Thanks!

This is the removal timeline from the Google article:
Deprecation means that it will be removed soon, not cease to function. Q1 2025 maybe that date of cease to function. However, that does not sound firmed up.
Also, it is worth noting that a library we use has this function in it. Whether or not that we use the functionality it uses as a part of it is another thing that a developer can confirm. It also may not be detrimental to your sites at all so I wouldn't panic just yet 😉 

It would be very useful if we were able to automate regular recurring bulk email. E.g I want to send a specific email to certain users when certain filters are met and would like to do this on a regular basis. Currently we can only do this as a one off email.

This issue has been resolved in the recently released 4.7.15 version. Please update your site if you are still experiencing the issue, and let us know if you see any reoccurrence.

It just means that you will have to update your MySQL Database at some point.
PHP versions and MySQL are two different parts to your server. You have highlighted your PHP version, it's your Database (bottom left of the picture) which is the issue here.
If you cannot update your server yourself, ask your hosting company if they will upgrade your MySQL version.

I have flagged this up to our developers for you

It is indeed in the latest beta

Can you let me know if this bug has been fixed in the next release?

As showcased in our past blogs, Invision Community 5 introduces a brand new, modern interface which brings improvements to performance, aesthetics and mobile usability.
An optional side navigation panel, new view modes, light/dark modes, customizable header layouts, a search modal and a mobile navigation bar are some of the things we've showcased previously. Today, lets take a closer look at some other miscellaneous changes that we've been working on while developing Version 5, including some of the code reductions and performance improvements that we've been able to achieve in the process.
For those of you who are developers, we'll also give some simple explanations of how (and why) we've implemented these changes.
 
Widgets
Sidebar widgets are perfect for displaying content feeds, featured members, announcements, advertisements and more on your page. In version 4 however, the widget column would often become an empty space once the widgets had been scrolled past:
  widgets-v4.mp4  
In version 5, widgets now stick to the screen once the last widget has been reached, ensuring your readers have more convenient  access to your widgets rather than a void space:
  sticky-widgets-v5.mp4  
 
Messenger
The Messenger is a great way to reach out to members when a private chat is more appropriate than a topic. Inspired by modern email clients, the messenger in Version 5 has been revamped with a full-height, sticky inbox, a longer message snippet, mini profiles and a more polished UI - all with a 25% reduction in CSS and a 100% reduction in Javascript.
messenger-v5.mp4
 
Sticky elements
We've mentioned sticky elements a couple of times now, so lets take a look behind the scenes at how they're created, and some of the performance improvements with Version 5. Traditionally, sticky elements were created using Javascript which would calculate the position of the element on the page and adjust it's stickiness every time the page was scrolled. Scroll events can be quite taxing for browsers, and when it comes to Javascript, the less, the better (especially when aiming for great page speed scores)!
With that in mind, all sticky elements are now handled using sticky positioning via CSS, which is a native and much more performant way of controlling these elements. We've been able to replace an entire 400 line Javascript component with just 3 lines of CSS.
 
Grids and Masonry
Grids have previously been handled in a similar fashion. Javascript would scan all elements within a grid to determine how many could fit on a single line, and would then shuffle these elements into position after the page was loaded or resized. CSS has since introduced its own grid properties, which has allowed us to replace more than 350 lines of Javascript with just a few lines of CSS, resulting in more performant page rendering and nicer looking grids (especially on small-medium displays such as mobiles and tablets).
 

 
Fun fact: We first introduced a similar performance improvement to "masonry grids" in our Gallery update from January this year, by replacing more than 400 lines of Javascript with, you guessed it, just a few lines of CSS.
 

 
 
 
Click targets
We wanted to make Version 5 as simple as possible to navigate, and one way of doing that has been by implementing larger click targets. Clicking anywhere inside an entry in a table or grid will now take you to that entry (you can still click on other links like normal within the click target, such as subforums or profile links). Click targets are optional and can be disabled via your theme settings if necessary.
 
click-targets.mp4
 
Data Lists (tables)
Speaking of tables, they too have been revamped. Tables automatically adapt to the space they've been assigned to (for those curious, this is done using CSS container-queries), so they're always neat regardless of the screen size, with no overflow or squashed layouts. Behind the scenes, the two columns below are created with identical code, yet they're quite different visually due to the size which they've been allocated. Even with these improvements, tables have received a 25% reduction in CSS.
 

 
Profiles
Profiles have been polished for Version 5 and include some nice improvements such as sticky widgets and tabs. 
profile-desktop.mp4
 
On mobiles, the side column collapses into a carousel, and the sticky tabs allow you to easily flick between content types without scrolling to the top of the page.
profile-mobile.mp4
 

Tabs
You may have noticed in the above clip that tabs on mobiles are now scrollable, compared to a dropdown menu from version 4. We made this change to ensure that tabs are given more equal exposure on small devices, and have managed to reduce the CSS by a whopping 80%.
 
Carousels
Last and certainly not least, are carousels. Carousels are great for displaying large amounts of data in a confined space and they've been rewritten from scratch for version 5. Previously, a Javascript library was used to create the "scroll effect", however this has never been the smoothest experience on laptop trackpads and touch devices.
In version 5, carousels are powered by native smooth-scrolling and scroll-snapping, which results in a much nicer user experience, especially on touchscreens. We've been able to remove a staggering 95% of the Javascript, substituting it with just a few lines of CSS.
 
carousel.mp4
 
To be honest, we've only just scratched the surface here! In addition to these changes, we've modernized (and reduced code) in almost every component throughout the suite including avatars, cover photos, dropdown menus, forms, inputs, buttons, lists, off-canvas menus, side menus, columns and more!
Combined, these changes result in not only a significant reduction in code, but also a polished UI that performs smoothly on desktop and touch devices. We're excited to continue modernizing Invision Community well into the future as new technologies and techniques become available to us, and are looking forward to getting it in your hands in 2024.

View full blog entry

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

The obligatory developer testing code..... because Xdebug isn't good enough! 🤣

Cheers 👍

I have a license that I paid full price for a while back. I stopped renewing it because I never used it. I thought I was going to use it for something but it turns out I didn’t end up using the software for anything. I paid renewals for about a year or two but the software just say there not ever one time being used. It didn’t make sense for me to keep renewing it. 
 
However, I like to think that if I ever figure out a use for this software, then I have already paid for it more than a few times over. It should be there for me to use and start paying renewals again.
 
I hate to think that I would have to pay full price for it all over again. 😣
 

 
 

"We have lots of statistics, no one uses it, it has been discontinued..".  🙂

Never mind, I had not enabled HTML for selected users.
Sorted now.

You don't need to use FileZila for this.
You should have phpMyAdmin in your CPanel.
Look for the core_members table, and on your admin account which is locked, scroll along for 'failed_logins' and delete the contents in that field and then set 'failed_login_count' to 0.
You can then use the forgot password tool to get a new password and be able to sign in.

It is, yes
twitter.com has a different oembed endpoint to x.com, hence the fix in 4.7.13 to account for it.

With the Marketplace EOL and providers switching to or relying on their IPS sites, it's really not the time to also be losing the built-in Support Ticket system. Providers will need it more now than before and all the third-party offerings are not free after trials end, require additional sharing of client data and require integration. The integrated system with Commerce is so convenient and with the planned Commerce improvements even more so.
Please can you consider a stay of execution or perhaps even simplify it to make it less timely for IPS to maintain?
Thank you.

Looking at those logs you have several crashed tables that need to be repaired.
In addition I also see that you're using MySQL 8.0 and I've seen a few people having issues with it. It would be best to use MySQL 5.7 or an equivalent MariaDB version instead.

I assume we would handle this just like we did for v3, v4.0, v4.1, etc. that have reached end of life. We generally give people a LOT of warning and then finally pick a date way in the future that they have to upgrade. We're talking years though. I am afraid I do not have a clear answer to give you on such specifics that are many years away 🙂 
As end of life approaches, you will get a lot more information on how to handle the upgrade. And, of course, by 2025 or 2026, v5 itself will be more mature. We might even be on v6 by then, who knows!

Unless this is a distributed application, not running in CiC, just make an executable file that you run with crontab at 5:00. 

Not by default imo. That will require custom coding.