Chris Anderson

Wouldn't it be easier on your staff, third-party developers and customers to improve upon CSS in a phased approach?
Why not break down the CSS Project into sub-projects? 
One sub-project you concentrate your attention on commerce.  You develop the "new" features you want to offer for that module while addressing any appropriate CSS changes needed.  You concentrate many IPS developer's and testers eyes on just that section of your overall codebase.
By concentrating "lots" of eyes on "one" module of the suite you will make it easier to identify any underlying performance, security problems or bugs. At the end of such a CSS sub project, you will end up with a much better underlying codebase then trying to tackle the entire suite all at once. Once that CSS sub project is "golden" you move on to the next sub-project
Upon release of the "CSS Project - Sub Project X" the third-party developers, theme designers and your customer base only have to make appropriate changes to "one" section of the IPS suite not the entire suite. 
By adopting a more phased approach you will significantly lighten the load and make it much less stressful on your third-party developers, theme designers and your customer base.

Wouldn't it be easier on your staff, third-party developers and customers to improve upon CSS in a phased approach?
Why not break down the CSS Project into sub-projects? 
One sub-project you concentrate your attention on commerce.  You develop the "new" features you want to offer for that module while addressing any appropriate CSS changes needed.  You concentrate many IPS developer's and testers eyes on just that section of your overall codebase.
By concentrating "lots" of eyes on "one" module of the suite you will make it easier to identify any underlying performance, security problems or bugs. At the end of such a CSS sub project, you will end up with a much better underlying codebase then trying to tackle the entire suite all at once. Once that CSS sub project is "golden" you move on to the next sub-project
Upon release of the "CSS Project - Sub Project X" the third-party developers, theme designers and your customer base only have to make appropriate changes to "one" section of the IPS suite not the entire suite. 
By adopting a more phased approach you will significantly lighten the load and make it much less stressful on your third-party developers, theme designers and your customer base.

This is a feature available in the CIC "Creator Pro", "Business", and "Corporate & Enterprise" plans
Sign up for Invision Community - Invision Community
 

This is a feature available in the CIC "Creator Pro", "Business", and "Corporate & Enterprise" plans
Sign up for Invision Community - Invision Community
 

Here's an option if you have pages:
You could use the menu app to create a pull-down list of club categories.  Click on the appropriate category and the member would be directed to a Page using the app above that could further classify the various clubs your site offers.  

I've toggled the third-party "Improved Clubs Ehancement" app off and on over the past few weeks while extensively testing club functionality.  Sometimes I would see the behavior above and sometimes I wouldn't. 
I thought I had disabled the third-party app on all my sites earlier today and it looks like one site (the one that I made the screenshots above) hadn't actually been disabled even though I clicked on it.  Any site where the app is enabled the above behavior presents itself.  The moment I disable the app the above behavior disappears.  I have gone ahead and filed a bug report with the developer.  
Go ahead and close out this support request.

You can modify the "Links Directory" to display whatever labels you want via the translation tool. I've provided a link to the help guide below to assist you through the process. 

You can modify the "Links Directory" to display whatever labels you want via the translation tool. I've provided a link to the help guide below to assist you through the process. 

@Jordan MillerHere's an article about the Bionic Font you might find interesting:
Does Bionic Reading actually work? Test for yourself! (readwise.io)
 

Adriano, thank you for the plugin.
I have a question and a request.
Can these locations / venues be sorted e.g. alphabetically?

Currently, the place is determined by the Admin in the order they were added.
 
This makes it difficult for users to browse places.

Currently running 4.7 Beta 5.  I downgraded to PHP 7.4 and I am now getting prompted to upgrade to PHP 8 not once, but twice. 

 
 
Many an admin will "Fix This" and wonder why they experience problems they never had before. 
I will get off of my soapbox now.  

Please see my findings attached below.  If a customer installs the suite on a site running PHP 8 or higher one would assume that all of the marketplace apps would be compatible based on the statement above. Even though PHP 8 has been around for 1 1/2 years many marketplace apps are not in fact fully compatible and in some instances, they will break a site hard if they are enabled with PHP 8 running. You might be expecting marketplace developers to keep their apps compatible with each new PHP release, but they are not consistently meeting those expectations.
A lot of assumptions are at play here.  I'm simply recommending that IPS and marketplace developers be more explicit around PHP compatibility to minimize problems going forward.
Encouraging customers to upgrade to PHP 8 could be very problematic if many custom and marketplace developers have not ensured their apps are fully compatible. A site is bound to show very strange behavior that will be difficult to trace from a customer's perspective and IPS support and marketplace developers.
I updated to PHP 8 approximately a month ago while testing out 4.7 betas.  I reenabled all of my third-party apps and I couldn't log into the ACP any longer.  Revert back to PHP 7.4 and I could.  After disabling all third-party resources, I painstakingly reenabled them one at a time to find out the last resource was NOT compatible with PHP 8. It's quite possible that those individuals that had purchased that particular resource hadn't updated to PHP 8 so the developer never received any reports of incompatibilities,   I myself had used the app without any incident for a year but on PHP 7.4. 
Once being apprised of the situation; I was told the resource had not been vetted to run on PHP 8.  So as long as I don't enable that app which has great value to my site, I can use all of the others.  I have only installed a small portion of third-party apps so I don't know how many more will be problematic.  There might be just enough apps incompatible with PHP 8 that I won't be able to update to that version for some time.  So I will revert back to PHP 7.4 which will be problematic as some of my resources will only support PHP 8 going forward as the developer has chosen to drop support for PHP 7.4 going forward.  
Each PHP version currently available has minus and plusses in their use.  I'm simply encouraging some clarity around the issue so that customers can choose a version that's best for their unique needs and have the requisite information to make an informed decision. That should come from both the IPS team and marketplace developers.  The more forthcoming you are the less one-on-one support interactions you will have to endure.
PHP Audit.docx

Many self-hosted servers are setup to support running just one version of PHP.  All PHP scripts need to support that particular version or there will be compatibility issues. 
Now that PHP 7.4 is approaching it's EOL there will be a concerted effort by developers to ensure their PHP code supports PHP 8.0 and PHP 8.1 in the very near future.
The challenge is that some developers will release products that will only work when PHP 8.0 or PHP 8.1 is running on a server as they will have decided to abandon support for PHP 7.4 all together.
So IPS and custom and marketplace apps will support (or not) a variety of vastly different PHP versions for the next several years. 
With the upcoming release of 4.7 developers are already starting to upload compatible updates of their apps.
The rule of thumb in the past has been that marketplace submissions had to fully support PHP 7.4 and support for PHP 8 or higher was optional, so there was little reason to note PHP compatibility.
Now that PHP 8 support is no longer going to be optional but will soon be a necessity the marketplace will need to track PHP compatibility for each new release. 
After a quick audit of the new marketplace releases, some developers are being very diligent and are clearly noting which PHP versions are supported and some are not.
It would be nice to put into place a marketplace guideline that all new uploads post 4.7 should clearly state which PHP version or versions that release is fully compatible with.
That way customers can audit their marketplace purchases to see if all of them will uniformly support a particular PHP version. 
It would be great if IPS added an additional "File Information" attribute as shown below to allow customers to more readily see and search for PHP version compatibility on this site and in the ACP marketplace.

Hopefully, PHP 8.2 and beyond we won't have to worry so much about PHP compatibility. 

If it had only happened once on each site and on one browser, I would have marked it down to a random glitch and not reported it.  But as it has happed more than once on all 8 sites something is amiss.  Whether the root cause is attributable to browsers or to your code it's an issue you should be aware of.
 

Appreciate you weighing in. In theory, one could clone a theme and name them according to what font they use and voila! Kind of clunky but it could be a quick way to accomplish what you suggested.
Also yes I was being lighthearted about the Bionic Reading, but serious at the same time. I was genuinely curious what our community would think, and if it opens the door to a larger discussion around UX and fonts than great! 

Already done as noted above.  
I run "Disk Cleanup" on my PC, clear my cache in my browsers and use Wise Disk Cleaner to further clean up my PC several times a day to minimize cookie tracking and ensure my browser has a minimal amount of potential problems lurking in the caches.  
I don't do this while actively browsing the ACP.  It happens before or after.
I use browsers with added security features enabled when browsing other sites but for accessing my site I use default browsers with no added plugins or tweaks to the settings.  I want to mimic as best I can the "average" user who may be accessing my ACP or front end.
 

Stored Access Information has been updated on all sites.
Uploads directory and all subdirectories are all assigned the same permissions for all sites.
Uploads 0775
Sub Directories 0777
Logs 0775
Mind you the ACP pages are properly formatted 99.9999% of the time and the errant behavior can snap back if I click on the right menu option.  This doesn't happen on just one site but all 4 primary sites.  This isn't a recent problem it has been happening off and on for weeks. 
 

All jokes aside, not everyone visually processes things the same way when it is in a small, medium, or large format.  A one size fits all approach will leave some folks at a disadvantage. 
If someone has less than "normal" vision, it can be quite challenging to comfortably read everything that is presented to us as we visit one site after another. It would be nice if sites running this software suite could be the exception to the rule. There may be value in offering a variety of different fonts instead of being locked into one. Doing so would likely increase the amount of content actually read and reacted to, increasing overall engagement.
If one font appealed to one and all there wouldn't be thousands of free or purchasable fonts out there.  A vast majority of these fonts are created to be aesthetically pleasing, not for increased readability. There are some fonts that might work far better for some portion of your members, as it stands today, we can't readily offer them an option.
If your site is geared more towards educating, then things get more complicated.  People learn in a variety of different ways. Some like to read content, some like to hear it, and some want to visualize the material being presented, and many want a combination of all three at their fingertips.
Having an all-text site leaves many people out in the cold. Having a built-in ability to hear text would be great for those that want to give their eyes a break or are severely sight impaired.
So, I'm not sure if @Jordan Millerwas being lighthearted in offering up the Bionic font for discussion or was trying to strike up an earnest conversation around fonts and how they can be better utilized to serve our communities.

This Bionic font might be appealing to a segment of one's audience but likely not all.  It would be interesting to see if you could provide a toggle to change the display font and size.   

This Bionic font might be appealing to a segment of one's audience but likely not all.  It would be interesting to see if you could provide a toggle to change the display font and size.   

The issue happens because the Invite cache is deleted on app install/upgrade, so if you don't want to wait for the marketplace version, replace the following file: applications / invite / extensions / core / GroupForm / Invite.php
The fix will load the Invite cache if it isn't in the Groups form.
Also upload the following file: applications / invite / sources / Member / Group.php

Just wanted to give you a head's up as it might not be something you might overlook as part of your compatibility testing.

It seems it’s going to happen “soon”😍
 
https://www.apple.com/ios/ios-16-preview/features/

@Sonya*The app you are asking about is the LearnPlusLMS which was a custom app job.