SeNioR-

Good idea.

Just a little suggestion about 'Who's Online'
For example:
Who is Online: 3 Members, 0 Anonymous, 20 Guests
 
If there is no anonymous user, system must hide it automatically like:
Who is Online: 3 Members, 20 Guests
 
or if there are only  guests on forum:
 Who is Online: 20 Guests
 
It'll be a little better, right?

Hello there!
The main purpose of user profiles is to make discovering user's content easier. I've found a way to improve the process a bit.
1. Content discovery
Let's take a look on my profile and especially on the filtering options:

Problem: It's quite a long list that grows with every new app or a content type. I find it confusing as during my time here I've posted only a topic and some posts.
I don't think I'm able to post anything in the documentation, release notes, providers, guides, IPS Blog etc. But I'm still able to filter my results by those options [basically to get no results note].
Solution: The idea is to hide all the empty-result-filters. Thanks to this we exactly know what type of content certain user posted, and save our time on scanning the long list.

2. Reputation view
I wanted to check my reputaion activity and this happened:

Problem: The page shows no results. Quite confusing as the sidebar clearly shows that I do have reputation activity. This is because by default the resulsts are filtered by Status updates in which I have no activity. And the list of possible filters is also very long (as stated above).
Solution:  As we have All activity filter in user's content page by default, we should also have All reputation activity filter in user's reputation page. And limiting the possible filters would (as above) make the experience more intuitive and clear.
In my case it would look like this as I have reputation activity in blog entries, blog comments and posts:

Thanks for reading! 🙂

What’s wrong with the pages app? 
 

You can exclude duplicates by using following rules:
Disallow: /*do=* Disallow: /*sort=* Disallow: /*sortby=* Disallow: /*csrf=* Disallow: /*csrfKey=* Disallow: */?tab=* Disallow: */?_fromLogin=* Disallow: */?_fromLogout=* My entire robots.txt https://hoilik.com/robots-txt-for-invision-community-473d8aa32984

app still working on 4.5, but you can change api version to v8
public $apiDomain = 'https://discordapp.com/api/v6';  to
public $apiDomain = 'https://discord.com/api/v8'; More: API Reference

Can the rules be completely customisable?
Could I for example, have someone be awarded a badge for creating a topic in a certain category and then also be awarded based on their specific group?

Example:
User makes 10 posts, changes their user group *badge awarded*.
User requests to be put into a certain group after x amount of posts, and each group can award the user who joins *badge awarded to represent their group*.
While you currently show rank images, could we also have an option to display badges on the Authorpane in topic view?

 
Or to be able to make a rule where only certain badges can be shown in the topicview?

While we have user group icons, I'd like to show special badges as part of the user group.
Just a couple of suggestions I had rolling in the head... As it's something I've been trying to do, as at the moment Fosters app allows you to manually award someone.

I also like the current one.

I think the badges are rather massive compared to the actual avatar personally. But I also have thought that the avatar is rather small for years, could just be me though. It just covers a lot:

It's almost like @SeNioR- has a badge beauty mark on that handsome face.

Look, @Daniel F..... we have to admit defeat. AlienOrigins obviously knows we're deep in the pockets with big PHP and have never touched this stuff in our lives. We are no match for his deductive reasoning skills.

Hi. I don't know about you, but I didn't like the "look" of the badge in the topic. In my opinion, the badge is too big.
What do you think about this look?
Example 1

Example 2

Badges already support this - when you create the rule that awards the badge, you can enter a member-facing summary of the rule, e.g. "You posted 50 replies!".

Few months have passed since our last post here, so let's get ready to rumble🙂
Supported PHP & MySQL Versions:
The PHP min version was increased to PHP 7.2 in IPS 4.6, this means that your marketplace submissions are required to work with this version, but keep in mind that few clients are going to use php8, so I would really suggest to try to get your code working with both versions, which means that you'll need to implement some changes to avoid some BC breaks in PHP8.
Here's a great list https://www.php.net/manual/en/migration80.incompatible.php
Security Improvements:
I have mentioned this change in another topic today, so let's recap it here too:)
We have a new IN_DEV code check similar to the slash check, which will inform you about any outputs containing the CSRF key in the URL.
This is a bad practice allowing attackers and 3rd parties to obtain the users CSRF key, so please try avoid this at any cost!
We're not going to reject MP submissions because of this, but please try to avoid this as much as much as possible.
Withdrawal Requests:
Please keep in mind that you're permitted to have only one payout request per week;) Since this didn't work out that great and to avoid any drama about canceled requests, this is going to be handled now automatically. As long as there's an open request, you won't be able to submit any new requests! But don't worry, you'll still be able to cancel it and create a new request!

@Matt This is much better solution. Thanks!

There is now a separate page to show rank progression and badges earned.

You can easily create a robots.txt files with wildcards:
Check the section: "How to Use wildcards in robots.txt" here: An SEO's Guide to Robots.txt, Wildcards, the X-Robots-Tag and Noindex (builtvisible.com) for example.
To prevent the report URL or other sections being indexed we use this e.g.: 
Disallow: /*?do=reportComment* Disallow: /*?do=add As the robots.txt file is very site and version specific and there are other methods, see article mentioned above, I think every site owner has to create his own robots.txt file or "no index" mechanism.

You could use the live meta tag editor to add robot instructions to the pages which you don't want to have indexed.
 
 
That said, we made also several improvements in IPS 4.6 to remove the CSRF key from URLs

I would also see this possibility in the future.

 

I would also see this possibility in the future.

 

---
I do like the concept of excluding. There are certain instances where I've wanted to exclude things. I'm curious - 1000s of subforums? Literally? How does that function? Not being shady btw I'm genuinely curious. 

This was a bug which was removed due to my above mentioned reason .

Font Awesome 6 Alpha is here.

There are such plugs
SuperVote 1.0.0
Thumbs Rating 1.2.0

You can block access to .json files via htaccess
<Files "*.json"> Order Deny,Allow Deny from all </Files> or only for "versions.json"
<Files "*versions.json"> Order Deny,Allow Deny from all </Files>