ahc

What's New in Version 1.1.2:
Fix error when merging members Fix error when trying to edit Notifications on ACP

Everyone here has great points to make, and I'm leaning more to the side of it just being a custom thing that the few communities who would need it could take advantage of it rather than it being suite-wide.
While my community has thousands of members on the LGBTQ+ spectrum, I wouldn't want this or have it enabled either. I've seen first hand what these pronoun labels invite on social media, such as Twitter and TikTok.  It basically puts a target on the person's back for anyone who disagrees with anything that isn't cisgender or heterosexual.  No amount of tools, staff, or community management style can effectively suppress that behavior. There are numerous studies that show how toxic social media in general is and how despite best efforts, this will never change until people themselves change. This will never happen because, well, humans.
Right now, we have a couple custom fields that invite members to provide information about themselves in a broader sense.  If they're comfortable enough to add that in, great, but I don't want them to feel pressured in any shape or form by having multiple fields for individual traits.

There's currently only one built-in manual option in the Withdrawal settings.  I'd like to see this expanded to at least 3 if possible.  We no longer use the built-in PayPal option and instead created our own manual one for PayPal, but we'd like another manual option to add Stripe for people who live in countries that PayPal is not available.
Thanks!

Everyone here has great points to make, and I'm leaning more to the side of it just being a custom thing that the few communities who would need it could take advantage of it rather than it being suite-wide.
While my community has thousands of members on the LGBTQ+ spectrum, I wouldn't want this or have it enabled either. I've seen first hand what these pronoun labels invite on social media, such as Twitter and TikTok.  It basically puts a target on the person's back for anyone who disagrees with anything that isn't cisgender or heterosexual.  No amount of tools, staff, or community management style can effectively suppress that behavior. There are numerous studies that show how toxic social media in general is and how despite best efforts, this will never change until people themselves change. This will never happen because, well, humans.
Right now, we have a couple custom fields that invite members to provide information about themselves in a broader sense.  If they're comfortable enough to add that in, great, but I don't want them to feel pressured in any shape or form by having multiple fields for individual traits.

Everyone here has great points to make, and I'm leaning more to the side of it just being a custom thing that the few communities who would need it could take advantage of it rather than it being suite-wide.
While my community has thousands of members on the LGBTQ+ spectrum, I wouldn't want this or have it enabled either. I've seen first hand what these pronoun labels invite on social media, such as Twitter and TikTok.  It basically puts a target on the person's back for anyone who disagrees with anything that isn't cisgender or heterosexual.  No amount of tools, staff, or community management style can effectively suppress that behavior. There are numerous studies that show how toxic social media in general is and how despite best efforts, this will never change until people themselves change. This will never happen because, well, humans.
Right now, we have a couple custom fields that invite members to provide information about themselves in a broader sense.  If they're comfortable enough to add that in, great, but I don't want them to feel pressured in any shape or form by having multiple fields for individual traits.

I think there are two different use cases:
Editor for user-generated content. Should be simple, not too many options, clear and foolproof. I think that the actual IPS editor fulfills the requirement. Editor for articles wrote by admin. Should be powerful, have many options (text positioning, blocks, columns, grids, custom code pieces, custom styles, extendable with SEO and other plugins, have additional extensions via Marketplace etc.) For this case, the actual IPS editor is not enough. 

Correct me if I'm wrong, but pretty much everything presented that way can easily be hovered over to see the exact amount, no?

Correct me if I'm wrong, but pretty much everything presented that way can easily be hovered over to see the exact amount, no?

Thanks, I know what it is. Will submit a fix. 👍

Quick report,
With this enabled, we can't merge member accounts.  We receive an error halfway through and some information will have been merged while some won't, and both accounts will still exist with duplicated information.
Merging works fine when we temporarily disable it.

@ahc I'm afraid that IPS tech support says that's the intended behaviour for the 4 series. At least when it comes to Status Updates, as they are not deemed content items. So, not sure if that explains or not your case, as maybe Gallery items do count as content.
My recollection regarding Status Updates on 4.3 and 4.4 tends to differ, as I'm almost certain some members triggered the promotion with Status Updates prior to last week when we upgraded to the very latest version. But tech support are adamant that it has never been the case during the 4 series. Maybe my installation had a problem before (because even PMs triggered the promotion and I found that far from great), and now it works as intended.
So, sorry I cannot be of more help. Being your case about a different app than mine, I won't assume IPS reply applies to your case too necessarily. With a bit more time I'll test my own gallery and let you know what happens there. Unless someone has already done so. Cheers.
 

No worries, I will. Cheers.

Having the rank image there period is kinda ugly.  Something I'll def remove if we upgrade to 4.6.  Post profiles in general are really lacking structure and it's not cohesive at all in the style.  For example on this website, you have rather large blurry rank images on top of small circular profile photos, the contributor image has weird capsule shading, the Invision Staff image looks like someone randomly screenshotted a logo from somewhere else, and the client pips... The staff badge is also kinda useless since there are multiple other visual cues that make it obvious someone is staff.
First impression is that a handful of people all had very different ideas and someone allowed them all to contribute one thing each to make them happy.  🤣  Unless they reorganize some things or maybe even make the profile photo larger, it all just looks like clutter to me.  I've heavily edited my postcontainer template to get rid of the everything-center approach.

Daniel recently made this statement in his announcement to developers about 4.6.  Does this mean that 4.6 comes with the ability to set how frequent users can request a withdrawal based on days/weeks/months?  I've been asking for this feature since 2017 and I would be so happy if this is the case.

Just wanted to drop a note here that after testing on both our live and test site, it seems groups with a lot of members causes issues.  Data below.
Moderator Group
Members: 21
Error: None
Notification Verification: All moderators received a notification that they had been mentioned in test topic.
Member Group
Members: 4591
Error: A redirect to a generic 500 server error occurs after attempting to mention this group.  A page refresh will show that the post/mention was actually created even though you receive this error redirect.  I'm assuming this error shows up due to timing out, but I'm only speculating and could be wrong.  My assumption is based on the website being stuck in some sort of loading/pending stage after hitting the submit button for about 10+ seconds before it finally gives up and errors out.
Notification Verification: No one could verify that a notification was received with proper notification settings applied.  I asked roughly 60 members and also checked random accounts for the notification and couldn't find a record of one.
Secondary Member Group  (Promoted to this group after x amount of content.)
Members: 871
Error: None
Notification Verification: Several members verified a notification was received.
Additional Notes: The website hesitates for about 5 or so seconds compared to the moderator test, but the mention is sent without error nonetheless.
 
Similar test results were received on the test site with the exception of being able to verify the large group issue due to not having that many accounts for the test.  Is this something on my end I'll need to look further into or is the application itself struggling to keep up when the group count hits a certain number?

Daniel recently made this statement in his announcement to developers about 4.6.  Does this mean that 4.6 comes with the ability to set how frequent users can request a withdrawal based on days/weeks/months?  I've been asking for this feature since 2017 and I would be so happy if this is the case.

The notification I received of the update almost made me jump up and down.  I'm so HAPPY to have this application back!  Downloading it as we speak to fully test it out.  
Update:  I am back after some extensive testing with the filter options.  Most of my tests went through without issue which is amazing, but there were a couple that didn't work as intended.  I'll be posting my results below for the ones that didn't work.  Please let me know if it's because I did something wrong or if the filter option isn't working correctly.
-----------------
Test #1 
Filters: I selected all of our administrator and moderator groups with the "Groups" filter option.  All other options left at default. 

Results: It says it sent to 21 users, but none of those 21 that should have received it did.  However, I tested this again after some other tests and they did receive it, so I'm not sure if that was a one-time hiccup or what.  I'll let you know if it happens again.
Test #2 
Filters: I selected Administrators & Moderators with the "Member Type" filter option.  All other options left at default.

Results: It sent the notification to everyone in the default new member group assigned after registration.  (Currently 13,650 users are in that group.)  The admins and mods did not receive the notification.  I deleted the test after taking the screenshot so it would not be sitting in their notification list.
Test #5
Filters: I selected a subscription option with the "Member has purchased a Subscription" filter and checked that it only counted expired subscriptions from any time.  All other options left at default.

Results: It once again sent the notification to everyone in the default new member group assigned after registration instead of filtering it to those with the expired subscription option selected.  The notification should have only been sent to a few thousand people total.

I was just about to come here and say this.  Why would people use extremely outdated software that is no longer supported even by its creator and then complain about other systems not supporting it? 
I understand the workplace perspective, but I'm assuming if the site you're trying to view can't be viewed properly on IE, then it's probably not something you're expected to be looking at while working.  😋
Once Edge rebuilt itself on chromium, I never heard another thing about IE.  To be frank, I didn't even know IE still existed or was available for download...  🤨

Very unfortunate. Thanks for sharing your thoughts.

I just submitted a new version to fix moderator permissions.
It should be approved in a couple of days.

Not currently but I've got similar support in other plugins and can add this in a future update relatively easy.

That's interesting indeed.
Maybe this will be the push Invision needs to stop using the outdated MassPay API and integrate the newer Payouts API which does allow individual payments.  It's much cheaper and allows you to send payments to both PayPal and Venmo accounts which helps in countries that don't have PayPal available to them.
Edit:  It doesn't actually look like anything is changing, but I could be wrong so we shall wait and see.  I read through the link and it looks like they're just explaining the guideline more clearly, probably due to some confusion with past clients?

I think the ignore feature needs a few more features to be useful.  Right now it really serves no purpose other than to make members angry/upset when they try to use it and find out it doesn't really serve a purpose.  Most sites give you the ability to actually block someone, preventing them from seeing your content or your account.  My members have been begging me for improvements to this feature or to implement a true blocking system, but it's odd to me that previous people who have requested this are never responded to, or are basically told just use the ignore feature as is and act like an adult about it.
The internet if filled with millions of people of all ages, and just because someone is an adult doesn't mean they'll act like one.  I don't think it's unreasonable to provide a little more in terms of someone feeling more secure about their privacy.
User A ignores User B, so all applicable content by User B is now hidden to User A, and User B is unable to send private messages to User A.  However, User B doesn't know they are being ignored by User A and has no restrictions given to them.  The ignore system works basically as if User A is the one being blocked from User B's content which seems backwards.  User B should be aware they are blocked and have the consequence of User A basically not existing to them in any capacity.
My members are requesting these common blocking features:
A blocked/ignored user cannot see the content of the blocker. A blocked/ignored user cannot view the account profile of the blocker. A blocked/ignored user cannot tag/mention the blocker in any content. If there is a plugin or app that already implements these improvements, please direct me to it.  If not, I can assure anyone who creates one will receive immediate downloads/sales.

That's interesting indeed.
Maybe this will be the push Invision needs to stop using the outdated MassPay API and integrate the newer Payouts API which does allow individual payments.  It's much cheaper and allows you to send payments to both PayPal and Venmo accounts which helps in countries that don't have PayPal available to them.
Edit:  It doesn't actually look like anything is changing, but I could be wrong so we shall wait and see.  I read through the link and it looks like they're just explaining the guideline more clearly, probably due to some confusion with past clients?

The fix for disabling email notifications I mentioned will be in our next release, but I don't know when that will be. We are continuing to discuss the other issues brought up here, particularly separating some of the notification types.