LiquidFractal

Whoops!  Obviously meant to say MariaDB 10.6.8 🙄 lol

I recently upgraded to 4.7 and 8.0.x on my business site, and everything is running fine.
However, I tried it first on my test site by first upgrading to 4.7, then disabling all customisations, then upgrading to 8.0 and re-enabling things bit by bit and reloading the site - which helped me discover one or two apps/plugins which broke the upgraded test site so I could delete them on my production site.
I tried 8.1 and it was working for a while but I now have to reinstall my test site as there are strange problems with trying to access the PHP *.sock file (I think switching FPM packages too often does this?).  Anyway, that's probably a general procedure to follow when making such important site updates.
Strangely, I ran this on my newly-wiped-clean test install site and while everything's in the green, the PHP script seems to omit everything below server requirements:

Just FYI: perhaps this is due to PHP 8.1.8?
 

Is anything being logged to your error logs? It's probably a 3rd party hook which isn't compatible with PHP8

Those 5 items must be fixed by your Host, in either the server-wide php.ini file, or in an account-specific php.ini file as an override in your server account. They may need to recompile PHP to add some missing Extensions.
Once that has been done, reload that page and check to see if the red items are now green.

Upload the file to your forum's root (where the conf_global.php file is located) and then access it from your browser using this url:
https://www.singaporebikes.com/ips4.php  

While on PHP 8.0 or 8.1, please use the following requirements checker to ensure that your PHP has all required modules: 
 
Additionally, I noticed you only showed a screenshot of your third party applications. If you are using any third party plugins or custom themes, please disable those and switch to an unmodified theme.

Running MariaDB 10.6.8 without issues.

For what it's worth, I'm currently running IPB 4.7 on MariaDB 4.6.8 and PHP 8.0.8 with no issues whatsoever.  Because my VPS allows me to switch PHP versions with the click of a button, I've even done some preliminary testing with PHP 8.1 and have had no problems with that either.

Also using MariaDB 10.6 with no problems.

MariaDB 10.6 is very good, no problems here

It will only show you resources that are compatible with your current version.

No, all good - I was checking my apps and plugins en masse by clicking through to the Marketplace interface, which apparently doesn't have all this information.

It's compatible as is. No update required. I'm going to update the file in the MP now so that it's marked appropriately.

You should read this topic :
We haven't heard from @newbie LAC for a while. We can only hope he is fine or getting better.

The latest update should be IPB 4.7 and PHP 8.1 compatible.

Poked. I had to increment the version number from 20.0.0 to 20.0.1 for the resubmit. Other than that, the file is identical to what you have now.
All good.

Almost certainly. I'll test both of these (they are separate things) later today and report back. I have to resubmit the files regardless if there are changes or not to get the Marketplace to flag them up for 4.7 compatibility officially though so that will take some time.

Sorry for the late reply, I thought I already replied to this. But unfortunately mentions works differently for Pages Content, Right now it's not possible to hook into this code. I'll try get in contact with an IPS Dev to see if they make this function more hookable in the future so I can dd this.
Do you want an option for members to disable it theirselves (for example on their profile). Or for admins to select a complete group to not show the members in the group listing?
------------------------------------------------------------------------------------------------------
Also update for 4.7 has been pushed, waiting on mod review now 🤞

A new version will be available soon for 4.7. 
Recently I discover that another plugin generates errors that are wrongly assigned to this app. 
I don't know if this is your case, but since I have to do all the testing for 4.7 this is the time to do a recap of the malfunctions you have.

I've had the same issue for months and months now - I have to disable ICE in order to add apps to a Club!  I've given the version number and other applicable information...and nothing for ages.
This app is important to my business functionality, but I'm going to rethink paying for this app if the developer doesn't at least remind us they're alive!

@InvisionHQ any updates on any of the pending issues in this thread. We're not talking features, we're talking basic malfunctions. Many of us truly depend on apps such as yours and your absence hurts us all. We're not whiners, just loyal paying customers who would welcome solutions, if not a simple acknowledgement of your concern. Unless I'm mistaken, your last post on this thread dates from April 3; we are now 17 July. Not sure if I'm alone in feeling this frustration?
PS. If you're having any personal issues, that's fine, we understand, but tell us so we can consider our options.

This has been on my mind for some time now...it would be great to have a bit more more granular control over the subject lines IPB automatically sends out for things like comments, replies, etc.
For example: when a client replies to a project discussion thread, I simply get the title of the forum thread X in my notification email.  It would be a bit clearer if it read "Reply to discussion X" or "Comment on X" or something like that.  I think it would be good to change this, but even better to allow site owners to configure these things wherever possible.

This has been on my mind for some time now...it would be great to have a bit more more granular control over the subject lines IPB automatically sends out for things like comments, replies, etc.
For example: when a client replies to a project discussion thread, I simply get the title of the forum thread X in my notification email.  It would be a bit clearer if it read "Reply to discussion X" or "Comment on X" or something like that.  I think it would be good to change this, but even better to allow site owners to configure these things wherever possible.

There is probably a more efficient way, but I use the method above myself, purely as I dont have to look it up LOL. 

First off: I am not a SQL expert of any kind, so I will not field questions about this procedure - I'm just sharing what I just did on my website to switch over DB tables to InnoDB as per Invision Support-page recommendations.  The code isn't mine - I lifted it off the web somewhere.
If you've been wondering how to switch over your MyISAM tables to (what I understand as) the more stable and optimized InnoDB storage engine, look no further!  It might be best for everyone to do this anyway, as I read somewhere that MyISAM is now deprecated and, I suppose, on the way out eventually(?).
Anyway - to do what follows you will need access to phpMyAdmin or some similar interface which allows you to perform direct SQL queries.  Make backups - I do not assume any responsibility for anything that breaks as a result of this!
First, go in to phpMyAdmin (or whatever) and make sure your Invision DB is selected.  This procedure assumes that you have one DB which is dedicated to IPB with no other app tables in the DB (it may still work, but I have no way of trying it out and I don't know enough about SQL to be sure it will work in a shared DB).
In the SQL query box, run the following code.  Be sure to replace YOUR_DB_NAME_HERE with the name of your Invision DB:
SET @DATABASE_NAME = 'YOUR_DB_NAME_HERE'; SELECT CONCAT('ALTER TABLE `', table_name, '` ENGINE=InnoDB;') AS sql_statements FROM information_schema.tables AS tb WHERE table_schema = @DATABASE_NAME AND `ENGINE` = 'MyISAM' AND `TABLE_TYPE` = 'BASE TABLE' ORDER BY table_name DESC The output will include a list of SQL commands linked to your existing MyISAM tables.  Each line, when run, will convert the MyISAM table in question to InnoDB as per the following example:
ALTER TABLE my_table ENGINE = InnoDB;
You can run each line separately, or (recommended) run batches of them at once.  Just make sure the syntax is correct for each line (phpMyAdmin will truncate longer lines, but will show you if a line has improper syntax).
You may need to do several passes in order to switch over all your tables.  My procedure was as follows: I ran a series of ALTER TABLE statements at a time, then re-ran the SQL query in the above box to get a revised list of remaining MyISAM tables.  Then I'd run the next batch of generated ALTER TABLE lines, and so on until running the SQL query block above generated no results (which means that they've all been converted and you have no more MyISAM tables).
That's it!  Browse your DB and you should see all of them running under innoDB.
If there's a more professional and streamlined way to do this (especially for very big websites), I encourage those with the knowledge to post - again, I'm just posting what worked with my VPS.
Hope this helps someone out there!  I swear I can see a definite speed increase on my site as a result of switching!