Ibai

Assumption made:
the notification is generated by a background task on the relevant site Theory:
Task method is set to CRON The CRON task itself is using PHP 7.4.x for PHP, while the site itself is using a different version Resolution:
Modify the CRON details in your scheduler

While one can mod these in, I 100% agree it needs to be officially supported. No Tiktok, no Discord, no Twitch.
It's 2022, this should be a top priority now.

You can edit that yourself in your theme if you like:
https://jimiwikman.se/invision-community/invision-community-playbook/invision-community-tips-tricks/remove-and-5-more-from-categories-widget-block-r1/

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

It was always wrong though. You would change a core file and so every future update of that file would cause an unnecessary conflict. Adding an override in the custom.css was always the right solution. So, the change just prevents you from doing it the wrong way. 

Hello,
I would like to suggest adding the possibility of marking forum posts as unread.
Thank you

Absolutely agree, hiding the CSS templates is ridiculous! It was like a live, instant reference, so useful and tbh having realised, I'm unwilling to update the last of my live sites. Having to enter and exit designers mode is no good, it's slow, clunky, buggy, and you even advise us not to do it on live sites. Who in their right mind would do that when they need to make some quick changes to custom css templates or look up some css to refresh their memory?
By all means, remove edit permissions if you absolutely must, but what's the harm in leaving the templates read only and searchable?

Yep 😞 I checked and updated nearly 100 apps and plugins already.

For the sake of my head/health, I need to take a break.

But will end up on an error. That's not the problem here. Scanner is flagging same issues and a new one!
 

My bad... the block changed its position:

 
@Matt, it was fine a couple of days ago. Please don't say we'll have to go through every app again!
😞

I'm pleased I didn't update again - there's far too many people posting issues for this to be updated until everything is sorted.  My sympathies go out to everyone affected, clients and devs.

Why did you remove direct CSS editing???
The entire suite is full of CSS errors anyway - and now you're complicating any improvement....
This version is absolute bullfaeces...
No performance improvement, but some absolute crap you've done...
I am so disappointed that I don't know if I will continue to be client...

Invision Community 4.7.2 now features a third party application and plug-ins PHP 8 compatibility scanner.
Please read this post as you may find applications of plugins disabled after upgrading.
Why do we need this?
The underlying programming language that Invision Community uses is PHP. The latest version, PHP 8 was released in November 2020 and features many breaking changes and incompatibilities that are not backwards compatible. Some of these changes mean that what was a harmless silent notice, is now a fatal error which would mean that if you upgrade with incompatible code, your community would throw a fatal error which results in either a white screen, or a server level error message in your browser.
These fatal errors cannot be captured by Invision Community and managed. The fatal errors are deeper in the execution chain.
PHP 8 has been out for close to two years, and PHP 7.4 is 'end of life' and security updates will cease from November which means that it becomes insecure, so everyone will have to move to PHP 8 very shortly.
What is it
The compatibility checker examines all third party applications and plugins that you have added from the Marketplace.
We encourage our Marketplace authors to test with PHP 8 but not all do, and as such applications and plugins that work fine with PHP 7.4 will fail with PHP 8.
The compatibility checker scans all third party code for issues that could cause fatal errors, and if it finds them it will disable the application or plugin on upgrade.
The only way to re-enable the application or upgrade is to update it to a 4.7.2 compatible version from the marketplace.
Can I re-enable disabled third party plugins and applications?
Yes, if you are confident the plugins and applications are fine to run with your current PHP version then you can re-enable them until our November release which will then enforce the disabling of applications.

It's worth reaching out to the authors of key plugins and applications to see if they have a PHP8 compatible version available, or plan to have one by November so you can prepare for the November upgrade.
Is this really needed?
Unfortunately yes. PHP are making bold changes that are not backwards compatible. Invision Community is fortunate to have so many third party developers releasing apps and plugins to further enhance the feature-set, but we do not have direct control over this code. Our priority is to ensure that your site upgrades smoothly and remains online.
Why now?
We finally ran out of road. We have been working towards PHP 8 compatibility for a while, and we have encouraged our third party authors to do so too, and to test with PHP 8. We also informed the developers in August about the scanner and what it may do to their applications. We also have been releasing Invision Community 4.7 betas since May of this year to give them as much time as possible to update their applications. Enforcing this change is painful in the short term but benefits everyone in the longer term.
What else can I do?
Your self-hosting license allows you a test install which you should use as a staging site and test any upgrades on that staging site before performing the upgrade on your production site. This will enable you to capture any issues that may arise before you run it on your production site.

As always, we recommend that a back-up snapshot is taken before any upgrade so that you can easily rollback if you encounter any issues.
I'm using PHP 7, does this affect me?
Yes, the compatibility scanner will still run on the upgrade and check for PHP 8 issues so that when you do upgrade to PHP 8 you won't find that your community is no longer working.

Thanks for reading!

hi, it would be nice to make it so that custom added emoticons show up after lets say animals and nature category instead of being at the very end?
what I'm trying to suggest is to let us order the emoji categories however we like. not only the newly created emoji categories but all of the  categories.

I put it in the global template before the head.  It's usergroup ID.
For multiple usergroups, follow the logic posted here: 
 

No i never got anywhere with it. I was hoping the invision team would know the answer.Since they dropped support for non cloud customers its been a real chore getting anything

I've asked the devs about this, and the method for embedding with Twitch has changed, enough so this isn't a matter of simply adding back some code or reenabling some settings. it's something which would have to be rewritten.
We've moved the topic to the Feature Suggestions section, for consideration in a future release.

Not a huge deal, but still confusing:
This option in the Database Filter Widget to only show my own records …

is very useful, but pointless and confusing if the database is set to only show my own records. 

I suggest, the filter widget checks that settings and suppresses the choice to only show my own files. 

@My Sharona, Start at tagmanager.google.com. When you have your container setup, you should see a page like this where you can click the container ID in the top right

A popup opens with the head and body snippets

The problem on this platform is not CSS, but JS. Tasks too long.
I think it's a big mistake on your part to look for a CDN core for CSS for this platform. It would be better if it was JS core in CDN.
Let the CSS be as before - editable, also every CSS file has a revert function - ie. even if someone messes up the site's css, it's easiest to post a message - use a Revert and you won't have to deal with your support about it.
Consider javascript - there's the biggest TBT for mobile…

I dont think so... What's that header?
I had to change my settings to this in order to avoid issues with logins and cache:

Anyhow I still experience every now and then some Error communicating with origin... Usually close to the weekend. For instance, this morning.

Sorry this is number 3:
Ability to moderate topic applying tag and prefix without edit topic again
For admin, moderators and authors 

The only way in which to switch off that would be to switch off post before register. You can do this within System->Settings->Posting
As far as changing email settings, you can to this in System->Settings->Email Settings

Would be nice if they remained bold until clicked, like Facebook does, maybe include the dot as well.