SeNioR-

From the js file (line 61):
ips.createModule('ips.ui.uploader', function(){  
To create a new one you need to copy/paste the file in your app, change the name, update the names/references, edit the code you need, and call the new module's name in the HTML.
 
This is the code that registers the module (I'll use the dialog one which is more used):
ips.ui.registerWidget('dialog', ips.ui.dialog, [ 'url', 'modal', 'draggable', 'size', 'title', 'close', 'fixed', 'destructOnClose', 'extraClass', 'callback', 'content', 'forceReload' , 'flashMessage', 'flashMessageTimeout', 'flashMessageEscape', 'showFrom', 'remoteVerify', 'remoteSubmit' ], { lazyLoad: true, lazyEvents: 'click' } ); You need to change the dialog name (maybe dialogbis) which registers the widget. All the other values in the array are the options you can use inline.
 
This is how the code would be with the original dialog module:
<div data-ipsDialog data-ipsDialog-title="TITLE" data-ipsDialog-remoteSubmit data-ipsDialog-flashMessage="ITEM SUBMITTED"> This is how it would look with your updated dialogbis module:
<div data-ipsDialogbis data-ipsDialogbis-title="TITLE" data-ipsDialogbis-remoteSubmit data-ipsDialogbis-flashMessage="ITEM SUBMITTED">  

Forum moderation management used to be straightforward. It was commonplace to assign a moderator to a single forum. They would be responsible for enforcing the rules, removing spam and generally modelling the behaviour you wanted to see within your community.
As community management has matured and moderators are tasked with roles based on knowledge, help and support, there is a need for more nuance in managing topics within your community.
For example, you may have specialists or teams of specialists who help answer questions about development, sales, or support. Topics that require this help may be posted anywhere within your community.
Indeed, this feature was inspired by a need in our own support community to ensure customers get the right help from the right team member. We have questions on feature sets, purchasing, and support requests, each requiring a different team member. It is not enough to hope that the right person sees the topics; they must be assigned to ensure excellent service.
 
What are the benefits of this feature?
The ability to assign a topic to a single moderator or a team of moderators ensures that each topic gets the best outcome regardless of where it was posted.
Having topics assigned helps moderators deal with issues quickly, as there's clarity over which moderators should handle the topic. It also helps keep your community team accountable by having the ability to monitor their workload and get statistics on the time it takes for your team to reply. These statistics also help the community lead assess quality control.

 
How do you use this feature?
There are two ways to assign a topic to a moderator or team of moderators. You can assign a topic when replying to it or do it from the topic's action menu.
Once assigned, the assignee can review their assigned topics via the Moderator Control Panel and see which are assigned to them via the list of topics. Each moderator will receive a notification informing them they have a new assignment.

Those with permission to assign topics to others will see all the assigned topics and who they are assigned to when reviewing the list of topics.

The Admin CP contains a list of all assigned topics and also allows you to create and manage teams of moderators, such as "Sales Team" or "Developers."

Finally, once the topic has been managed successfully, the moderators can remove themselves from the assignment completing the task.
Assigning a specific topic to a single person or team in a busy online forum is a strategy that can enhance the effectiveness of the forum's management. It promotes efficiency, expertise, consistency, and accountability, which are vital for maintaining a vibrant and respectful online community.
We hope you are looking forward to this feature and look forward to any comments you may have.

View full blog entry

1. Member posting is now working with the latest patch 👍
2. Database records made in clubs do not appear in feeds, not the club feed or the Activity feed. I have seen reactions to records though. 
3. Pages Feed Blocks don’t honor club-level access permissions. On the club level, I turned off access for “Members not in this club” and the records can’t be accessed by non-club-members. But Pages Feed blocks for the database contain these records, despite “honor permission” being activated. The goal here would be to create a “latest news (or whatever the content is) from the clubs I am a member of” block. 
4. Adding a category in a club is missing the Description field
5. Not making a Pages category in a club public leads to a confusing, generic error message, which doesn’t tell the user to join the club to access the content. I think the error should be clearer, or the Pages category tab should be hidden from the club, as it is done with Forums in clubs. Right now, it’s inconsistent. Forum tabs disappear, Pages tabs lead to an error. 

Since applying the 4.7.16 hotfix from today, on default theme with no modifications, we started getting template error in forums.front.index.forumRow template in one of the forums.
On further debugging
{{$count = \IPS\forums\Topic::contentCount( $forum, TRUE );}} returns post count followed by plus sign +, which throws when passed to
{number="$count" format="short"}  since it's not a number.
This happens for just one subforum.
I've updated site access details in Client Area if you would like to have a look 🙂 The forum ID which returns this strange count is 111.

For example when I've typed something in Facebook and I accidentally try to close the tab, I get an alert stating I'm about to lose any unsaved content, and asking me to confirm. Maybe something like that could be a solution. 

I have tagged this for the attention of our developers to have a read of. I cant see how we can control this, however Im not one of the developers myself, so its not to say someone else might

Hi, after updating to 4.7.16, my Topic Feed stopped displaying. It's only visible when I disable the option: 'Honor permissions?.'
If the 'Honor permissions' function is enabled, the Topic Feed does not display, but when I disable this option, it does display. Previously, it displayed without any issue, but after updating to 4.7.16, this error occurred.

 

For example: if I set 4 as maxItems on a Stack field, I get the message:
which is not right. It should be "You must provide up to 4 items" or something like that.
Language bit: form_items_max.

Reporting it as it just occurred on my live site...
UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses` SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709136738 IPS\Db\Exception: Duplicate entry '0138fdaa72c8135e62b3487f5be7b11d-2970-' for key 'PRIMARY' (1062) #0 /home/fbaeefdf/live.ynwa.tv/system/Db/Db.php(1159): IPS\_Db->preparedQuery() #1 /home/fbaeefdf/live.ynwa.tv/applications/core/extensions/core/IpAddresses/Logins.php(33): IPS\_Db->update() #2 /home/fbaeefdf/live.ynwa.tv/system/Member/Member.php(6504): IPS\core\extensions\core\IpAddresses\_Logins->pruneIpAddresses() #3 /home/fbaeefdf/live.ynwa.tv/applications/core/tasks/pruneipaddresses.php(43): IPS\_Member::pruneAllLoggedIpAddresses() #4 /home/fbaeefdf/live.ynwa.tv/system/Task/Task.php(281): IPS\core\tasks\_pruneipaddresses->execute() #5 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(751): IPS\_Task->run() #6 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\settings\_advanced->runTask() #7 /home/fbaeefdf/live.ynwa.tv/applications/core/modules/admin/settings/advanced.php(38): IPS\Dispatcher\_Controller->execute() #8 /home/fbaeefdf/live.ynwa.tv/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\settings\_advanced->execute() #9 /home/fbaeefdf/live.ynwa.tv/admin/index.php(13): IPS\_Dispatcher->run() #10 {main} I believe this is a knock-on effect of it NOT having been pruning the IP addresses correctly previously - the issue you'll have is that there could be multiple entries for a specific device_key and member_id, but with different IP addresses. Now that task has been fixed to do the pruning, when it tries to remove the IP address on those multiple entries, the PRIMARY key for each row will end up being the same as the key is made up of device_key, member_id, IP address (which is now blank)
Sample content attached:core_members_known_ip_addresses.sql
When the query in the task runs against that data, the error occurs:
UPDATE `core_members_known_ip_addresses` `core_members_known_ip_addresses` SET `ip_address`='' WHERE ip_address != '' AND last_seen <1709135288
 
 

This is fixed in 4.7.16.

I'll be disabling that functionality until this is resolved then...just been alerted to a data leak (title of a private topic being visible) which is going to cause a few problems now that it's been seen.
Test of a topic in a private forum, viewable by a normal member...
 

will try tomorrow

Optimize your forums, guys. Interaction to Next Paint (INP) is an official Core Web Vital.
INP replaced First Input Delay (FID) as the new responsiveness metric. Chrome is officially deprecating support for FID, so developers and site owners have until September 9, 2024, to transition over to INP.
 

You also need to upload the files to the server before clicking Continue. Have you done that step?

Not at present for subscriptions, but we do have this in version 5 🙂 

I am trying to install the new security patch on my software and I'm not able to do so. I'm including the errors I'm getting in screenshot form.
I downloaded the package as it asked me to, and when I click Continue, I get the error in the next screen.

It was used for guest page caching in earlier versions. It's no longer used in current releases.

I updated to 4.7.16 and see the same. Members can’t post in a club database category, even though they can post on the database page itself. Admins/club owners can post. 

Please install the latest beta, rather than beta 1. We are a few versions in

There is some unused code in the Authy handler file /system/MFA/Authy/Handler.php in the verifyApiKey() function at the end of the file:
public static function verifyApiKey( $val ) { try { return \IPS\Http\Url::external("https://api.authy.com/protected/json/app/details")->setQueryString( 'api_key', $val )->request()->get()->decodeJson(); } catch ( \IPS\Http\Request\Exception $e ) { throw new \DomainException( $e->getMessage() ); } if ( !$response['success'] ) { throw new \DomainException( $response['message'] ); } }  
The IF after the TRY/CATCH is never executed, it either returns inside the TRY or throws an exception in the CATCH:
if ( !$response['success'] ) { throw new \DomainException( $response['message'] ); } It can be removed.

Kind of.

@Matt Finger is working hard on it as we speak. I don't want to say too much but we did a lot of research and picked the best solution in terms of development, stability and future functionality. More news soon. It's probably one most have never heard of but it is used widely. If anyone is worried about us using Froalo or TinyMCE, don't be. 😅

My oh my, how exciting

We looked at Quill, but no.

🤔-Thinking about the bug
👀-Looking for the solution to the bug
📰-Writing the fix for the bug
➡️-Exiting when he realised the bug fix didnt work
👤-Hiding in the shadow to see if anyone notices
 

I want to thank @teraßyte for outstanding guidance.
We were able to complete the upgrade from an outdated community forum from 4.2 to 4.7+ with his support.
His service is top notch and I highly recommend reaching out to him for help.
Respectfully,
Shyrax