Marc

When its ready ™  😄
Seriously though. Thats the honest answer. We're getting must closer to that state however. 🙂 

Please upload a fresh set of files from your client area, then try visiting /admin/upgrade again. This would indicate that for some reason the files were not downloaded or unpacked properly on the server

Fixed.

Solved
I removed session.save_path from php.ini on cpanel

Always a good start, I find 😄 

Always a good start, I find 😄 

Always a good start, I find 😄 

Give this plugin a go (it's unsupported, etc, etc if anything goes wrong, just disable it).
Search_ no force index() 1.0.0.xml

Have you actually viewed the page source to see if the code appears?  If the code is not appearing, I would use the option in the ACP support area to clear your system cache. If the source code appears but the banner does not, it’s a problem you have to address with the code provider. 

To upgrade such an old version you need to:
Switch to PHP 8.0 and check the requirements are all good. (Don't use 8.1 because it causes a few more upgrade errors compared to 8.0. The old upgrade steps were never written for 8.0/8.1 which didn't even exist at the time.) Manually upload the new 4.7 files to your server. Go to /admin/upgrade to start the upgrade process.  
Before doing the upgrade, you also should uninstall any 3rd party applications/plugins that don't have any updated version for 4.x, if not a lot of extra tables/columns/settings (maybe even tasks) will remain in the database.
Considering how old the version is, doing a test upgrade in another location is usually a good idea, especially if you have lots of 3rd party modifications installed.

Marc,
Thanks for the clarification/correction.
John

Edit the highlighted template (ideally, edit your own version of the default templates)

 
Find this line:
{{foreach $record->comments( NULL, NULL, 'date', 'asc', NULL, NULL, NULL, NULL, FALSE, isset( \IPS\Request::i()->showDeleted ) ) as $comment}} Change 'asc' to 'desc' and save.

There isnt a way in which to do this at present unfortunately, so indeed it would be feedback for something to add 🙂 

Yes. You can create a database and disable the add/submit permission for all groups but a few select ones (admins, moderators, news writers, etc).
You can also link/sync every record to a topic in a specific forum for comments. Or you can just keep comments in the record itself.

I have just seen your email there. It was under a different email address. Please note, this was sent only an hour ago. 
As I mentioned above, you need to ensure the redirect is not in place while you reset this. I have gone ahead and reset on this occasion for you. 

Indeed, as mentioned my Stuart in the topic above, performance is something actively being worked on

Hi, Kudos to IPB Team 🧡 For Custom Page databases superb features with that kind of flexibility sky's the limit. With Pages we could easily ditch WordPress need for custom Pages and articles. The only feature is missing is able to select multiple categories for same record or article. Wordpress provide that support for that out of box like follows:

 



Sometime same piece of information falls under many different categories rather than just once. so it would be really great if team could also add support for this feature for custom page records. Please submit your inputs for what you think about this feature. 🙂

Thanks
Dia ^_^
 

Because of how the framework works, records can't be in multiple categories. Just like the same topic can't be in multiple forums.
 
What you can do is add a custom select/checkboxset field to the database, and allow users to select categories there (while setting up the database to use a single category for all records in the backend).

I was also one of the complainers but PHP had a surprise for us. It doesn't seem to have received press yet but there was a policy change:
https://github.com/php/web-php/commit/94f19598acef411b9286587c8e1a721b587ff152
PHP supported version page already displays the change of extended support. As of now, PHP 8.1 will receive security support until 31 Dec 2025 so it pretty much gives Invision and us some pressure relief.
https://www.php.net/supported-versions.php

When its ready ™  😄
Seriously though. Thats the honest answer. We're getting must closer to that state however. 🙂 

You wont see it until you have done a search. So you need to click the cog icon, set some criteria, and search 

Neither of those are the client area. Go to https://invisioncommunity.com/clientarea and then sign out.

The recommended versions in the latest releases are aligned with the minimum requirements for v5

There isnt a way in which you would be able to ban them in that manner, however as a suggestion, what you could do is create a group with no permissions and move them all to that group, if its something where you want to immediately remove their access.