SJ77

Was just exploring V5 by using this invisioncommunity.com site and found a few things. Might as well report here. If you search for all members to get a member list (a trick I use on my site often) Pagination only has a next or previous button If you search for a blank by entering space bar once or twice, you get a template error. Thank you

Same thing on my server. And given that it works perfectly fine in the forums and only has an issue in downloads app concerns and confuses me.

I’ve got a bit more info now. It seems to work with an older version of ImageMagick, but not the latest one. It’s not clear if the bug is with IPS or ImageMagick itself. I spoke to a developer, and here’s what they found: I think it's a problem with the ImageMagick version installed: I tested on my local development server, and it was all good => ImageMagick v6.9.12-61 I tested on my dev site on this server, and it threw an error => ImageMagick v7.1.1-43 InvalidArgumentException: (0) #0 /home/domain.net/system/File/File.php(330): IPS\_Image::create() #1 /home/domain.net/system/File/File.php(1595): IPS\_File::create() #2 /home/domain.net/applications/downloads/modules/front/downloads/submit.php(336): IPS\_File->thumbnail() #3 /home/domain.net/system/Helpers/Wizard/Wizard.php(181): IPS\downloads\modules\front\downloads\_submit->IPS\downloads\modules\front\downloads\{closure}() #4 /home/domain.net/applications/downloads/modules/front/downloads/submit.php(685): IPS\Helpers\_Wizard->__toString() #5 /home/domain.net/system/Dispatcher/Controller.php(107): IPS\downloads\modules\front\downloads\_submit->submit() #6 /home/domain.net/applications/downloads/modules/front/downloads/submit.php(35): IPS\Dispatcher\_Controller->execute() #7 /home/domain.net/system/Dispatcher/Dispatcher.php(153): IPS\downloads\modules\front\downloads\_submit->execute() #8 /home/domain.net/index.php(13): IPS\_Dispatcher->run() #9 {main}

Great, thank you for testing! It confirms an issue on my end ugh! 🤷‍♂️

I can get to step 2 like you did there. It fails on me after hitting submit Thanks for testing. Which version of 4.x is that? Can you try and hit submit? odd, it works everywhere for me except in downloads app.

Hi, I know webp support was added around the ~ 4.6 release time but seems that it was never correctly implemented for preview images (screen shots) in the downloads app. If you add a webp file as one of your screen shot (preview images) you get a system error after hitting submit. Can someone else running on 4.x confirm this? This error indicates that the system is encountering an issue while trying to generate a thumbnail for the preview image. The stack trace shows that the function IPS_Image::create() is being called with an empty parameter, which suggests that it failed to process the file properly. This only happens when using a WebP file, it’s likely that the Invision Power Downloads application isn’t handling the WebP format correctly in only here in the downloads application. (works perfectly in the forums) Using it for a preview image ends up triggering an InvalidArgumentException. Thank you :)

Hi Thank you. I certainly do not want to manually prune any table. I am asking about features available in the ACP. Just wanted to understand what happens before I use it. Will it crash my site if I use it at this point and try to clear 5 years or so? I can't imagine that being anything but a VERY intensive query that is kicked off.

Hi, I have been afraid to prune member history because I am not really sure what the effect will be but now my core_member_history table is HUGE. Might even be impacting site performance it's so huge. ~15GB+ (just this one table alone) What happens if I set the prune date in the ACP? Will it impact downloads files orders? Will customers no longer see their order history? Will they lose access to things they bought (files) using downloads (nexus gateway)? Please help me to understand what the impact will be. I don't want to upset my members and customers. Anyone who has used this feature. Let me know. PS: my IP and known devices tables are HUGE also and I did try the prune settings but those don't get any smaller so I have no idea what those prune settings do either. EDIT: also if you know, will kicking off the prune make my site slow to a crawl since it would likely be a massive prune at this point and hammer mysql? or will IPS chunk it and handle it gracefully?

I did not know this.

Well, there is this

I hear you. And look, I am certainly for anything that helps stop prevent spreading this around. Protection for the victims is something we should ALL try our best to accommodate. But unfortunately the CF solution only creates risk for you and your site but not much benefit toward solving the problem. It Reports Your Site, Not the Uploader. The tool flags your platform instead of the actual user who uploaded the content. This can make your site look like the offender, even if you’re the one taking positive steps toward removing bad content. Creates a Permanent Legal Paper Trail. Every flagged upload is reported to NCMEC under your site’s name, potentially marking your platform as a repeat source of CSAM even if the content was blocked immediately. CF can report false positives. Can Increase Law Enforcement Scrutiny. Multiple reports can trigger investigations into your platform, forcing you to justify why CSAM is appearing instead of focusing on prevention. Loss of Control Over Reporting. The tool auto reports everything based on hash matches, meaning false positives, context, or your moderation actions don’t matter. the report is still sent. As a site owner, you want control so you can focus on reporting valid concerns only and you want to report bad people not your own site as the source. Potential for Service Termination. If Cloudflare receives too many reports related to your site, they can terminate your account, leaving your platform vulnerable to downtime. There are better solutions that don't increase intrinsic risk for you and your site.

Provides no legal protection, ensures you are reported if there's an event. Not great!

I have 30K+ tags. I just ran a query of the top 500 most used tags and the first tag is used over 51K times and that last tag is used over 1K times. I have 13500 that are used at least 5 or more times. I have loads of functional utility around these tags and my users love them. Not sure what's supposed to happen in my case.

If I switch to the new license, will my $500 one-time branding removal still apply, or will I have to pay for branding removal separately under the new terms?

Pardon my ignorance but I don't even know what "Community Classic" is. I am self hosted and I stay current with my renewals. What am I doing wrong? Thank you in advance.

I specifically don't have this. That is the reason for my post here. Thank you

I don't see the IPB 5.0 download button nor do I see a request upgrade link.

@Matt I completely understand that change is necessary, and part of evolving software means retiring outdated features, I get it. But I believe removing status updates isn’t a step forward, it’s actually a step back, especially considering how critical this feature is for communities like mine. I really believe we should consider an upgrade to address your aforementioned specific concerns versus a removal. Perhaps there are ways to tackle the "conversation drain" etc. Status updates aren’t just a feature on my site, they’re the feature. It’s literally the homepage, the heartbeat of user interaction, and the primary driver of engagement. My Gen Z audience, which makes up a significant portion of my user base, has grown up on platforms where quick, dynamic," feed based" content is the norm. They won’t engage with traditional forums the same way older generations did. For them, status updates aren’t a relic, they’re familiar ground. Removing them strips away the one thing that keeps my community feeling current, vibrant, and aligned with how younger audiences interact online today. I understand that for some communities, status updates might have become stagnant, but that’s not a flaw of the feature itself, it’s about how it’s integrated and supported. That's why I say, instead of removing it, why not focus on improving it? Imagine status updates with better moderation tools, richer content options, smarter algorithms to surface popular posts, or even tighter integration with forum content to create a more cohesive experience. That’s not looking backward, that’s pushing the software into the future. Removing status updates aligns Invision Community with the past, not the future. No matter how pretty, and organized we make the forums they, in a sense are still passé. Social media style features are still the standard for online engagement. If the goal is to make Invision Community competitive and relevant for the next generation, enhancing features that mimic successful social platforms should be part of that vision, not something to retire. I'm honestly shocked it's slated for deletion instead of massive improvements and much better integration into all parts of the software. Even options to monetize it, sell rotating ad's etc could be considered. But I would be happy with simply not killing it and preserving the current functionality. I hope you’ll reconsider. There’s a huge opportunity here to modernize status updates rather than abandon them, or to at least not kill something great. Thanks for hearing me out.

Status Updates - The profile status updates system is a holdover from decades ago and will be removed in Invision Community 5. This is the NUMBER 1 feature on my site. It's literally my home page and everyone uses it. It's the only thing that bumps this software close to the age of social media. Most of my Gen Z audience won't touch the forums.

Oh that is nice!! How did I miss that? WOW THANK YOU

I used language edits to cram what I needed into the terms of use acceptance

They can leave it yes or no and still register. Makes no difference 😞 I basically just want a box they must check in order to register. [ ] I am at least 18 years old For some reason I thought this would be a super easy thing to add.

That's sad news. 😞 Perhaps that's why it's not working on here. Thank you for letting me know. Could this work if I change it to a yes / no ?

Sorry to bring this up again but this solution doesn't work for me. I want a check box that must be checked in order to register. I don't wish to suddenly force all of my existing members to have to jump through this hoop. (only new registrations) I am not even showing this on the users profile, it's just a step I need to be compliant when people are registering in 2025. Is there really no way to make a profile field required in order to register?

Will having our communities on the newest version of 4.7.x better position us for a smoother upgrade to 5.x when it's available, or is 5.x so different that it won't make a difference? Are steps being taken in 5.x to ensure a smooth upgrade to from 4.x? What can we do now to prepare our communities for the upgrade without issues? Thank you