Afrodude

This modification is already compatible with 4.7 and I've just submitted a new version to mark it as compatible (no actual changes).
Those who have it already installed can keep using it without problems. 👍

This is the support topic for this plugin:

Welcome to IPS land where everything can be a dream. 

Create a simple form with a number field with a minimum number required and an unlimited option with a 0 value:
$form = new \IPS\Helpers\Form; $form->add( new \IPS\Helpers\Form\Number( 'test', 0, FALSE, array( 'min' => 2, 'unlimited' => 0, 'unlimitedLang' => 'disabled' ) ) );  
Now load the form, uncheck the Disabled checkbox, and submit the form. Once you've done all the steps this is the error that appears right under the number field:
 
The error makes you believe you have to insert at least 3 but the field does indeed accept a 2 value. The correct error should instead be:

I had same errors whenever I updated yesterday, and after the search index was rebuilt, I don't see the error no more. Yet, if I want to rebuild it again, the error will show again.
OutOfRangeException::0
#0 /forums/system/Content/Comment.php(562): IPS\Patterns\_ActiveRecord::load(199766) #1 /forums/applications/forums/sources/Topic/Post.php(580): IPS\Content\_Comment->item() #2 /forums/applications/core/extensions/core/Queue/RebuildSearchIndex.php(167): IPS\forums\Topic\_Post->isFutureDate() #3 /forums/system/Task/Task.php(47): IPS\core\extensions\core\Queue\_RebuildSearchIndex->run(Array, 361000) #4 /forums/applications/core/tasks/queue.php(43): IPS\_Task::runQueue() #5 /forums/system/Task/Task.php(375): IPS\core\tasks\_queue->IPS\core\tasks\{closure}() #6 /forums/applications/core/tasks/queue.php(55): IPS\_Task->runUntilTimeout(Object(Closure)) #7 /forums/system/Task/Task.php(274): IPS\core\tasks\_queue->execute() #8 /forums/system/Task/Task.php(237): IPS\_Task->run() #9 /forums/applications/core/interface/task/task.php(58): IPS\_Task->runAndLog() #10 {main}  

The issue still occurs on version 4.7.5.

Just for the record the issue still occurs on 4.7.5.

Just a reminder that the issue still occurs on version 4.7.4. Thanks mate.

I can confirm the bug report is still open at present

Yes, we’re aware. It has not yet been patched. Thank you 🙂 

This is the support topic for this modification:

Idea #2:

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

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 have just spoken internally to see what the plan is for this. Currently we support Elasticsearch and OpenSearch, however they forked somewhat after version 7. At present, the plan is to focus on OpenSearch. Note, this may well change of course, but thats the plan currently.

There is no news I am able to give on this front at present. So at present you would simply continue to use the current supported releases

We're not Xenforo. It'll be quicker than that.

You're kidding right? because you can simply do it with one button "Del", and then you don't have to rewrite anything. Issues is fixed. 

@Daniel F Great! While you're at it can you guys give a good look at this forum and check the other bugs? I've posted several ones (even easy ones like this one) and they were never acknowledged nor fixed.
 
Here's some random ones:
https://invisioncommunity.com/forums/topic/468507-bug-470-cannot-setup-extra-fields-in-downloads-to-be-included-in-topics/ https://invisioncommunity.com/forums/topic/468498-bug-470-the-setting-send-diagnostic-data-is-broken/ https://invisioncommunity.com/forums/topic/468464-bug-470-cms-database-setting-field-options-records-per-page-controls-also-comments-per-page/ https://invisioncommunity.com/forums/topic/468123-bug-470-blog-app-has-calendar-code-in-it/  
These are just some recent ones.

Steps to reproduce:
Visit a member's profile in ACP and click the Ban button in the Warnings & Restrictions box. Setup any ban option you want except for the Move to option so the member remains in the same group. Once you click the Save button this new log shows up in the member's account activity:  
This happens because of this code below in /applications/core/modules/admin/members/members.php on lines 2867~2871:
if ( isset( $values['member_ban_group'] ) ) { $member->logHistory( 'core', 'group', array( 'type' => 'primary', 'by' => 'manual', 'old' => $member->member_group_id, 'new' => $values['member_ban_group'] ) ); $member->member_group_id = $values['member_ban_group']; }  
The fix is to change the IF check to use this code in order to skip it when the group ID is the same instead:
if ( isset( $values['member_ban_group'] ) AND $values['member_ban_group'] != $member->member_group_id )  

So by design this is force on us and we can't say to no to not sure it to us forever even when we paid for the product? I didn't pay for ads. @Marc Stridgen You like the comment, but could you expand on this concern?
Oh BTW, not the soultion as I didn't mark it and it was force marked. I was more looking for a reply from IPB.

Instead of:
domain.com/database/record/articles you'd have to use something like this instead:
domain.com/database/record/?tab=articles  
And then in the template account for the tab variable and switch the active tab based on it.

Idea #1:

If you rename topic's title to something new and then you decide to merge it with another topic, the action of changing the title shouldn't be merged to the other one because the other topic has a different title. 

 
 

I noticed there is no sitemap for clubs. As they can be indexed, such a map would be useful for better and faster indexation.