Dextro Energy

Hey!
I'm getting scam accounts that make upto 147 topics/posts in around 10 minutes which is quite ridicolous (they usually tend to make around 20~, 147 is the current record). I have used the "Flood control" setting to prevent so many posts in a certain timeframe, but, it would be wonderful if there was a setting to apply moderation if a certain number of posts are made within a given timeframe rather than this. Is there one? I can't seem to find it. 
I understand it may cause false positives, but whoever is creating 10 times in 1 minute probably needs a break/checkup too.

There's a lot of confusion here, so I'll do my best to address it all.
Why have you removed CSS editing?
First off, we have NOT removed the ability to edit and add CSS to your themes. When we released Invision Community 4.0 way back in 2012, we added a "custom.css" file and asked everyone to add their custom CSS to this file. This means that when we make changes to the core CSS, you do not have to merge changes, or re-apply edits. Your custom CSS is untouched.

This is exactly what CSS is designed to do. The core CSS may contain something like this.
body { font-size:14px; font-family: Helvetica; margin: 10px color: black; } So, what do you do if you want to change the colour to red? In the past you could edit this core CSS file directly and make it like so:
body { font-size:14px; font-family: Helvetica; margin: 10px color: red; /* Changed color here from black */ } This would work fine BUT if we changed our core CSS to change the font-size to 16 like so:
body { font-size:16px; font-family: Helvetica; margin: 10px color: black; } This will now overwrite your changes, which means you'll need to re-edit it back to:
body { font-size:16px; font-family: Helvetica; margin: 10px color: red; } This does work, but means you are constantly having to compare your changes to ours.
Fortunately, CSS (cascading style sheets) is designed to allow new CSS files to overwrite rules that we set, and that is why we have a custom.css file ready for you to make your upgrade-proof edits.

So, if you wanted to make the body colour red, instead of editing our code and maintaining changes, you simply add this to custom.css
 
body { color: red; } CSS knows to combine OUR rules with YOUR rules. It's exactly what CSS was designed to do. The computed result (how the browser sees it) of this is exactly the same:
body { font-size:14px; /* from our core css */ font-family: Helvetica; /* from our core css */ margin: 10px /* from our core css */ color: red; /* from custom.css */ } This is clearly a much better way of changing the CSS rules. You can keep all your custom code in one place and you no longer have to maintain copy and paste edits to core CSS.
In short, CSS editing STILL VERY MUCH EXISTS!
Why this change?
To be frank, it's 2022 and there's no valid reason at all to be editing core CSS when CSS itself was designed to cascade and make your lives easier.

We should have locked out editing of core CSS a long time ago. As the web moves on, we have to move on too. Serving CSS from a single CDN will improve the page speed of your site as it will come from a cached no-cookie domain.

No modern application out there will allow you to edit core CSS, there just is not the need.
I realise that for a very small number of people this means changing how you work, but this is how you should have been working since 4.0 was released a decade ago.
If you actually use custom.css I promise once you have completed the initial population of this file, your life will be made so much easier!
This is industry standard
If you look at other apps, they allow you to add custom rules that cascade over the core CSS files. Like Squarespace, and Wordpress which states: "You can use the CSS editor to customize the appearance of your WordPress.com site. It works by allowing you to add your own CSS styles to override the default styles of your theme."

Thank you, that helped clarify a little further. Additionally, I think merging content was enabled prior for me which may have not encountered this.
Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

core -> front -> profile -> profile
Find:
{{if settings.reputation_enabled and settings.reputation_show_profile}} Add the following before it:
<div class='ipsPadding_vertical:half'> <p class='ipsType_reset cProfileRepScore cProfileRepScore_neutral ipsRadius:full ipsDimension_height:4 ipsDimension_minWidth:4 ipsPadding_horizontal:half ipsType_large ipsFlex-inline ipsFlex-ai:center ipsFlex-jc:center'>{number="$member->achievements_points" format="short"}</p> <h3 class='ipsType_reset ipsType_unbold ipsType_medium ipsType_light ipsMargin_top:half'>{lang="achievement_points"}</h3> </div> Save
Result:

If you want to remove the reputation points, then delete the code block that begins at:
{{if settings.reputation_enabled and settings.reputation_show_profile}} and ends with:
{{endif}} <-delete this one {{if $solutions}} <- Don't delete this one  

Use at your own risk
The following will place the member's achievement points total below their group title
Edit forums > front -> topics -> postContainer
After:
{{if $comment->author()->member_id}} <li data-role='stats' class='ipsMargin_top'> <ul class="ipsList_reset ipsType_light ipsFlex ipsFlex-ai:center ipsFlex-jc:center ipsGap_row:2 cAuthorPane_stats">                    
Add:
{{if isset( $comment->author()->achievements_points )}} <li> <a href="{url="app=core&module=members&controller=profile&id={$comment->author()->member_id}&do=badges" seoTemplate="profile_badges" seoTitle="$comment->author()->members_seo_name"}" title="{lang="achievements_awards_points" pluralize="$comment->author()->achievements_points"}" data-ipsTooltip class="ipsType_blendLinks"> <i class="fa fa-bathtub"></i> {number="$comment->author()->achievements_points" format="short"} </a> </li> {{endif}} Result:

You know what, I just tested it myself again and this time it didn't happen this time. How odd? I'm not too sure what to say.
I figured it out... how embarassing. One of our Forum moderators just royally cocked it up and tried to cover their tracks without saying anything; but logs don't lie!
My bad.

Hey!
I just merged a fairly large topic (lets call it X) with a smaller one (Y) that was basically exactly the same in terms of premise. X had a poll on it with quite a lot of votes, but upon merging Y into X - the poll disappeared from X!
Is this intended behaviour? I did not see a warning that, that may happen (might just be my ignorance). Is there anyway to get that poll back? Topic X was also unpromoted (is this intended when merging as well?), that isn't too much of a problem as it can just be promoted again, no real harm there though is there any way to stop that from happening in future?
Thanks in advance.

data-ipsCarousel
data-ipsCarousel-slideshow
data-ipsCarousel-fullSizeItems
data-ipsCarousel-shadows='false'
data-ipsCarousel-showDots
<div class='ipsBox ipsSpacer_bottom'> <h2 class='ipsType_sectionTitle ipsType_reset'>{lang="featured_downloads"}</h2> <section id='elDownloadsFeatured'> <div class='ipsCarousel ipsClearfix' data-ipsCarousel data-ipsCarousel-fullSizeItems data-ipsCarousel-slideshow data-ipsCarousel-shadows='false'> <ul class='cDownloadsCarousel ipsClearfix' data-role="carouselItems"> {{foreach $featured as $file}} {template="featuredFile" group="browse" app="downloads" params="$file"} {{endforeach}} </ul> <span class='ipsCarousel_shadow ipsCarousel_shadowLeft'></span> <span class='ipsCarousel_shadow ipsCarousel_shadowRight'></span> <a href='#' class='ipsCarousel_nav ipsHide' data-action='prev'><i class='fa fa-chevron-left'></i></a> <a href='#' class='ipsCarousel_nav ipsHide' data-action='next'><i class='fa fa-chevron-right'></i></a> </div> </section> </div>  

I just tested and the log is added in the Moderator Logs as I said before:

I'll try to inform the groups added/removed in the log entry.
 
----------------------------
EDIT: Just noticed there's no log for SECONDARY GROUPS; only for PRIMARY.
----------------------------
That's how log entry will be from now on:
- Primary Group:

 
- Secondary Group:

@Liloz01, I'd say the comments in the source files are a pretty good form of documentation.  I use a 3rd party app called FileLocator aka Agent Ransack to search the source files for these sorts of things:

We knew exactly what to search for in this case, but a search for just "moderator" would have ultimately led to the same result since the comment includes the word in line 72.
I'm no programmer, but this tool along with a good IDE like PhpStorm have made all the difference in developing my own plugins as the need arises!
As for how to know what you can do with \IPS\Member::loggedIn, I'd search for "\IPS\Member" and browse around to see how it is used, especially as it pertains to functions which accept a Member object.  (To find it used strictly in functions I'd search for "@param    \IPS\Member")
e.g.:   \IPS\Member::loggedIn()->memberPostCount() 
/** * Post count for member * * @param \IPS\Member $member The member * @param bool $includeNonPostCountIncreasing If FALSE, will skip any posts which would not cause the user's post count to increase * @param bool $includeHiddenAndPendingApproval If FALSE, will skip any hidden posts, or posts pending approval * @return int */ public static function memberPostCount( \IPS\Member $member, bool $includeNonPostCountIncreasing = FALSE, bool $includeHiddenAndPendingApproval = TRUE ) Hope that helps!