Afrodude

@Gary if you have access to the ACP, it is worth seeing the errors @PatrickRQ saw more than once or if not, mention it to the dev team to look at it. It could be a bug. 

I did notice it and merged them all into the one topic.
I don't think this is an issue with Invision Community, but perhaps that person posting and/or refreshing one or five too many times. 😛

The error happened yesterday to me. I was posting the topic and clicked SUBMIT button - then your page reported something went wrong error but I continued to click BACK/SUBMIT - still got same error. I even was not aware all topics were posted. You may want to report to developers for review of the logs, as I believe that multi-posting (in case of some error) should be prevented on code-level.

@GaryI did it very fast, but perhaps something like this where everything can be readable. 

This is what I loved whenever IPS released 4.5, and I would love to see this happen again because it helps both sides. 
 

Hi @Afrodude,
We plan to announce new betas in a new forum that's been created here on Invision Community, where you can opt in to be a beta tester, provide feedback and report bugs all in the one place.
Invision Insider - Invision Community
Beta Announcements, in particular, is coming soon, but you can start following the forum now for anything new that is posted there, including Invision Insights and Release Webinars. 😉
I hope this helps keep you in the loop.

I believe it's time to improve the look of the profile area especially user and group names.

Everything looks nice in the profile area but these two. I know that you guys do can better and can make an amazing improvement in here. 🙂 @Ehren

I found the change proposal interesting, so I made a little edit of how it could be.
I still want to tinker with this idea a little more, need to make buttons
Ignore the "font" used haha
The first image looks like it's being removed, so click here

I believe it's time to improve the look of the profile area especially user and group names.

Everything looks nice in the profile area but these two. I know that you guys do can better and can make an amazing improvement in here. 🙂 @Ehren

If you are thinking of going one-by-one then there is a quicker way - go to your group listing, click the permissions icon for Guests.

@GazzaGarratt this is forum permissions. You are giving a permission to guest to be able to create topics on some/all the forums you have.

Go read each topic posted in here, and you will find that at least more than 35% of the topics are solved by IPS clients not IPS staff team. Also, if it was a bug, someone else could confirm it or even find out what causing the reported issue.
Examples:
This is why this forum is open to everyone, and if IPS wants to make private, it would just take them few clicks to do so. By the end of the day in here is a community like anywhere else, and we are just trying to help.
I hope you will find your solution.

Thanks, I have filled an internal bug report for this.

My apologies, I am just helping you and IPS by confirming that we have the same issue. Also, this is a public support community not private. 
Anyway, I won't interfere with your support topic. 🙂 

Verion number unknow 🤣

It's set to 7 days. Somehow i still see members from 2022. So i don't think it's working. 

Yep, ugly as hell and not very functional. Maybe someday... 🙂

@GaryI did it very fast, but perhaps something like this where everything can be readable. 

One of the biggest benefits from IPS is also one of the most annoying things..
The Proxy Classes and full IDE support!
I have related a small script which generates a file with class aliases.
https://github.com/DanielFatkic/ipsaliases
 
This can be installed global on the system via composer
composer global require danielfatkic/ipsaliases and then just call  
vendor/bin/generatealiases . inside your IPS dev instance, or you can also pass the full path to an IPS installation, which will generate a file called aliases.php

Great work @Ehren. Thank you

@Marc Stridgen any news about this bug? It's open since July 2022. I thought it's going to be finally fixed by Jan 2023 release since it's only for 
From version 4.5 this bug is exist. Now we are 4.7.7, and yet this bug report still open!!!

I posted a fix for this error in this post: 
 

Line 265 of your conf_global.php file was corrupted with some non-ASCII characters at the word 'true'.
$INFO['sql_utf8mb4']             =     ÔtrueÕ;
That line is added as part of the utf8mb4 data conversion. If you've actually completed that step, the line is needed.
Just remove those two Ô characters from the line.

There are actually more SEO changes:)
1. Clubs and Club Pages Sitemaps
2. Club page and CMS pages can now also be flagged as not indexable.
3. We've added the noindex tag to few other pages which shouldn't be indexed.

Afrodude, I think it was already on their TODO list, and it just coincided with my sugesstion 🙂