AlexWright

Sure. In categories where Allow Albums, but not Require Albums is set, users can upload to either an Album or not. Images that aren't added to an album display below a listing of all albums in the category. At one point, we has a category with over 400 albums and about ten thousand images outside of albums. Navigation became...awkward.
 
This is a suggestion we made to xenforo as well, but in essence:

With multiple categories, one could add a Category field above the Album field in the image above. Basically have a nice tidy form for each image being uploaded which you can select these options in.

I have a question before purchasing this app. Is it possible to restrict based on birthday? For example, I have an NSFW group that users must be 18 or older to join. Is it possible to run a check via this app against a birthday?

Related:
https://invisioncommunity.com/forums/topic/425865-reporting-a-member-profile/ https://invisioncommunity.com/forums/topic/426413-modcp-and-moderator-tools-need-lots-of-work/?do=findComment&comment=2617763

Another thing thats often overlooked is the ability to report a member directly. For example, to report a member's About Me area, or a username, etc.

The ignore function is an extremely essential part of running community services such as Invision. However, I feel as if one of the most overlooked features is a fully functional Ignore and/or Block system. While we do have the current iteration of the Ignore function, it is severely lacking in some departments. The image below is (while themed) on a clean install:

This install has all of the Invision applications enabled (Forums, Blogs, Pages, Commerce, Downloads, Gallery). The above only references Posts (which many assume, and correctly, this refers to the Forums), Messages, and Mentions.
So how can this be improved? There's a number of ways, and a few other items I'd like to add.
1. Add most community applications to the Ignore list. This would mean adding Downloads, Blogs, and Gallery items (very unlikely that the need to Ignore admin generated Commerce content would arise) to this list. If I want to Ignore someone's content, generally I want to ignore all of it, not just some.
2. Extend the functionality of Ignore into a full on Block (perhaps as a user option). Most major community/social media platforms do this. Think Twitter, Facebook, etc., where when you Block a user, they cannot access your content (including your profile) either.
3. Add admin options to force users to ignore each other. Currently this requires logging in as the user and adding to their ignore list. At least make this accessible in the admin panel, and have options to disallow the user(s) to un-ignore/unblock each other.
Numbers 2 and 3 here are major reasons why I moved one community off of Invision and onto a competitor and repurposed the license for another project that doesn't need this functionality yet (yet being the key term, of course). The question of "why these changes, specifically" arose in a conversation with my mod team for the community we moved away. Our main answer was: this lowers the amount of moderation work, and allows us to not need to use posting moderation and/or account suspension between users tossing barbs back and forth. We weren't a large community by any means (about 18,000 registered users), but even so these features were so asked for by the moderation team and users that it caused us to shift platforms. Hopefully something will be done with this feature set in the future.
Cheers,
Alex

If its extended to pages I think that the admin should be able to turn on/off showing ignored content in certain areas. I have a database that anyone can contribute to and its not actually attributed to any 1 user (even if the end user submitted it) but there is no way to have my cake and eat it to so if they could ignore all content then a user could inadvertently submit the same content as the other person because they don't see it.
But overall I agree.

The ignore function is an extremely essential part of running community services such as Invision. However, I feel as if one of the most overlooked features is a fully functional Ignore and/or Block system. While we do have the current iteration of the Ignore function, it is severely lacking in some departments. The image below is (while themed) on a clean install:

This install has all of the Invision applications enabled (Forums, Blogs, Pages, Commerce, Downloads, Gallery). The above only references Posts (which many assume, and correctly, this refers to the Forums), Messages, and Mentions.
So how can this be improved? There's a number of ways, and a few other items I'd like to add.
1. Add most community applications to the Ignore list. This would mean adding Downloads, Blogs, and Gallery items (very unlikely that the need to Ignore admin generated Commerce content would arise) to this list. If I want to Ignore someone's content, generally I want to ignore all of it, not just some.
2. Extend the functionality of Ignore into a full on Block (perhaps as a user option). Most major community/social media platforms do this. Think Twitter, Facebook, etc., where when you Block a user, they cannot access your content (including your profile) either.
3. Add admin options to force users to ignore each other. Currently this requires logging in as the user and adding to their ignore list. At least make this accessible in the admin panel, and have options to disallow the user(s) to un-ignore/unblock each other.
Numbers 2 and 3 here are major reasons why I moved one community off of Invision and onto a competitor and repurposed the license for another project that doesn't need this functionality yet (yet being the key term, of course). The question of "why these changes, specifically" arose in a conversation with my mod team for the community we moved away. Our main answer was: this lowers the amount of moderation work, and allows us to not need to use posting moderation and/or account suspension between users tossing barbs back and forth. We weren't a large community by any means (about 18,000 registered users), but even so these features were so asked for by the moderation team and users that it caused us to shift platforms. Hopefully something will be done with this feature set in the future.
Cheers,
Alex

Hi
We have been doing test migrations and I noticed a huge amount of memory usage from Imagick on our install which reminded me that there is another option, GraphicsMagick which was a branch from Imagick a few years ago.
Generally it runs much faster and lighter than Imagick and also it seems to have less security issues. It does have some limitations over Imagick but most of them seem to be related to more advanced image processing so I *think* they would not be an issue for IPB.
If php was directly calling the Imagic binary rather than the php wrapper you used to be able to directly swap them out and it would mostly work if I recall.
Just a thought.

So I have been revamping my main site for ages today and it reminded me how much I loathe the "Create" link.
It shows you EVERYTHING you have access to submit if your database name and the record name are the same they are redundant as hell (Submit Record to Records) and this is even more prevalent when you use a single category setup instead of having multiple categories.
On top of that (and I'm submitting this in a separate topic) Pages databases are a mess in it.
I recently revamped my Create link, though I can't fix all of my issues I was able to take it from this:


To this:

 
While some of that (I'd say about five from the first section) are admin/staff only it doesn't make that list any less daunting or confusing for an end user.
 
So my issues:
No option in order. It currently follows an App order to put it into the list and for Pages they are all listed in whatever order they want looking at it now. No option in what shows in here. If I want a database to be submitted from only one page I can't tell the create menu (without editing the template) what not to show. Create is too vague of a term. I changed my verbiage to "Quick Create Content" to see if it gets used any more than it had been before as it stands even though it moves with the site I still don't think my members know what it is or how to use it.  
What I want is something where you can mange what shows up and in what order. People are already inundated with how much stuff can be on any one site, it would be good not to overload them with looking through a long list of what they can submit and focus them on your primary content sources.

Hello,
will check this mod soon and I'll let you know.

Is it possible to automatically include content with Tags in a search? Is this a setting I missed somewhere? Users are confused that searching for a Tag does not find the tags, because Tag search is an "Advanced" search option. For instance, if I search "Dragon", content tagged Dragon does not come up. I have to go to the "more search options" then "search by tag" and then "dragon" there to get content tagged "dragon" to show up. Is there an easier way to do this?

Hello
I think it is very important to add a check for server free disk space and check also the files size from S3 Cloud before starting the transfering from S3 back to server.
If the available free disk space on the server is not enough for the files that coming from the S3 cloud back then the server will be full and the server will die.
Nothing will work with 0 free space and the user will be in a case that he will not be able to revert that task and the only solution will be to request from the data center extra hard disks to added on the server.
Until then the forum will be down ....
Doesn't seem hard to add that very useful info for the user when he will try to run that task and from a quick check i found:
https://www.php.net/manual/en/function.disk-free-space.php
For Linux hosts:
$df = round(disk_free_space("/") / 1024 / 1024 / 1024);
print("Free space: $df GB");
Or in your case it sounds like you're running on Windows so:
$df = round(disk_free_space("C:") / 1024 / 1024 / 1024);
print("Free space: $df GB");
 
Some related info on how to get the size of the bucket also:
https://stackoverflow.com/questions/3910071/check-file-size-on-s3-without-downloading
https://www.cloudsavvyit.com/1755/how-to-get-the-size-of-an-amazon-s3-bucket/
https://serverfault.com/questions/84815/how-can-i-get-the-size-of-an-amazon-s3-bucket
But i think that you know how to do it anyway 🙂
 
Thanks !!!!
Please add this asap as it is very important !

Conversion to XenForo. Which, unfortunately, requires the files to be localhosted.

Thanks, perfect! Yeah, I set up an s3 bucket and the CDN for it. Would you say this is good for images only, or for all storage settings?

I'm guessing CloudFlare is the recommended choice? Or are people starting to use Amazon's? Thanks Joel.

Hi all,
We are a large image-sharing community and are looking into cheaper options for Storage. I've started to float the idea with the other administrators of storing images off-server and onto Amazon S3. Is this a good idea? And if so, what storage settings should be on the S3, and which should be server-side?
Thanks,
Nowe

It would be very useful if we could add an age (in years) to use the Promote feature. This is handy as it would help sites that have age-restricted areas. Right now we are using Kevin's Rules application to handle this, but a built in option would be much better.

I submited it only a few moments ago. It is waiting approval currently. When it is approved I will post the link here.

So, the Ignore feature is extremely lacking in all of what should probably be essential functionality. Currently, by default, you can only ignore someone's: Forum Posts, Messages, Signatures, and Mentions. While that's great and all, it's an extremely simplistic view of an Ignore/Block function. All major platforms (Facebook, Twitter, etc) have a way to Block and/or Ignore a user account. This hides all of that user's comments and contents and/or blocks them from viewing your content and profile. This is a major oversight in functionality that's missing in the IPS software. Not to mention that the Ignore function misses almost all of the other IPS default applications (Pages, Blogs, Gallery, Downloads, Calendar, Statuses, etc). The entire Ignore function feels like it was just slapped on to solve a singular issue (Forums) and never touched again. What an Ignore / Block function should be able to do:
Ignore all or some of a user's content. Block a user from contacting you (Blocking messages and mentions). Blocking a user from your profile and content. Most users prefer Ease of Use with this. If you're blocking someone, you (usually) have a good reason to. The current ignore feature on IPS is basically bare-bones and doesn't really do a great job at what it does. It can definitely be better, and hopefully this can start that.
 
---
Evidence has been found that William Tell and his family were avid bowlers. However, all the Swiss league records were unfortunately destroyed in a fire, and we'll never know for whom the Tells bowled.

Coincidentally I have developed such a plugin. I just submitted it to the MP.

This 1000x this. And it has to work for All content. Not just forum content.

Ips has confirmed a fix for 4.5.4

Your cache level should definitively be Standard, the default setting. Using anything else will break IPS' cache busting feature, which is needed to recache static assets.
Cache TTL can come down to a matter of preference. Considering important resources like CSS and Javascript assets are cache busted as needed, it's safe to use values up to even 30 days if you so wish.
The potential concern with this is, if image attachments are deleted but left embedded into posts as an example, they will still display as cached in the users browser for however long you set this to. So, it can be a minor privacy concern, as IPS currently does not automatically remove image embeds from posts when attachments are deleted from the users control panel.
That's really the only thing to keep in mind. Otherwise, I recommend at least 7-days personally.
 
Outside of these, there are several useful features Cloudflare provides that I recommend taking advantage of.
Note, some of these features are Pro only, but if you're a Free user, use the ones that aren't. They help if even a little bit and there's no reason not to.
Now, if you have a high traffic website and you can afford it, I personally believe it's worth upgrading to the Pro plan.
 
But to get started with the optimizations, under the Speed tab, go to Optimization and make sure these settings are enabled.

Polish with WebP enabled can be hugely useful if you have a lot of PNG attachments / avatar uploads on your site, as WebP can provide substantially better lossless image compression compared to PNG.
Auto Minify is disabled by default and you should enable it. The actual performance improvement is small, but it's still an improvement with no risks, so there's no reason not to use it.
Brotli, again, small improvements, but no risks and and no reason not to use it for clients that support it. All the overhead involved in performing the compression is handled by Cloudflare here after all.

Enhanced HTTP/2 Prioritization and TCP Turbo are again zero risk performance improvements and if you have access to them you should enable them.
Mirage can be great in theory for mobile browsers by automatically optimizing images on slow networks. It's in beta, but I do definitely recommend enabling this. Roughly half the of the internets traffic today is mobile. These optimizations can yield huge benefits to your users.
Rocket Loader I do not recommend enabling, as it can cause functional and perceptional issues with IPB. It makes things look and act in strange ways, and can potentially just break things. Rocket Loader is one of those things that works well for some sites, but is awful for others. It's not great for IPB in my experience. I say the same for PageSpeed JS optimizations and so on as well.
Under the Network tab, make sure these settings are enabled.

All of these are, again, zero risk performance optimizations. No reason not to use them.
Argo tunnel can potentially be useful as well, but note that it can be extremely expensive depending on your bandwidth requirements. It's an additional $0.10/GB of bandwidth. Do not enable it until you have at least a months worth of bandwidth analytics logged from Cloudflare so you have an idea of how much you can expect to pay if you enable this feature.

Ips has confirmed a fix for 4.5.4

Great 🙂