Jordan Miller

PS

Happy Hump Day! I've been working on a new blog post about the dos and don'ts when it comes to community moderation/guidance. Before I share it with you on Friday, I'd love to know your thoughts! What is something you should do when moderating your community. How about something that you ought to avoid? Something that immediately came to mind for me is moderating on the offense versus the defense. Generally speaking, most view moderation as a restrictive tool that takes power away from the community. A member posts profanity? Moderate! A topic goes live in the wrong section? Moderate! A spam bot infiltrates the latest blog entry? Moderate, moderate, moderate! That facet of community building will always exist, but going on the offense by setting up automations will save you time and money (and energy!). More importantly, it creates an elevated user experience because your attention is spent engaging with your members instead of policing people. Fostering a sense of connection with the community in my opinion is essential. PS - you may recall my blog post on shifting our mindset from moderation to guidance, but we love an SEO moment. Share your two cents in the comments below please! Would love to feature some of your comments in the upcoming blog post. 🙂 --- Check out a recent batch of platform updates since we released 4.6.7 into the wild. Shout-out to the support and dev team for all their hard work! - Fixed an issue where removing a currency can cause errors in search results. - Fixed an issue where reviews may not be correctly indexed with Elastic Search. - Fixed an issue where insert attachment links in dark mode may show in the wrong color. - Fixed an issue where importing the achievement rules xml file could fail during the upgrade. - Fixed an issue where insert attachment links in dark mode may show in the wrong color. - Fixed an issue where custom meta tags/titles may not always show on the community homepage. - Fixed an incorrect registration stats admin restriction. - Fixed an issue where insert attachment links in dark mode may show in the wrong color. - Fixed an issue where the 'recently browsing' Javascript may not load properly. - Fixed a rare issue where you may see the Service Worker Javascript after login. - Fixed a database error shown if a user does not have permission to edit date fields. - Fixed an issue where a guest may see a CSRF error when trying to purchase a subscription. - Fixes incorrectly escaped node form helper titles. - Fixed an issue where it was not possible to toggle the anonymous state of content items. - Fixed admins not being able to ban or flag member as spammers via the ACP profile when warnings were disabled. - Fixed incorrectly escaped node form helper titles. - Fixed an issue where task progress bars could show percent completion above 100%. - Fixed an error when moderators with permission to post anonymous content edit content of those that can't. - Fixed admins not being able to ban or flag member as spammers via the ACP profile when warnings were disabled. - Fixed an issue where multiple ACP notifications for the same item were visible. - Fixed the ACP-Follower Statistics Page which was returning an IN_DEV error if no followed content was present. - The ACP Member Profile Template will remove the left column if there are blocks to show. - Fixed orphan language phrases when deleting databases and custom fields. - Fixed a PHP 8 type error when upgrading between Commerce packages. - Fixed an issue with Activity Streams where the results may be incomplete when the 'Content I posted in' filter is used. - Added some missing VAT territories to checkout form. Appreciate you all! Thanks for participating in our community 🙂. Looking forward to hearing from you!

The XenForo converter for 2.2.x. is included in 4.6.7 🙂

Super fun to see us gaining momentum like this!

Me

Happy hump day, team! Apologies for no hump day post from me last week - I was on the streets of LA freedom fighting for Britney. 💪😅 However, this post isn't about me 😏 this is about us officially releasing 4.6.7 into the wild! It's available to you now! Just to refresh your memory, you and members of your community will now have the ability to subscribe to custom Activity Streams and receive emails with all the latest activity. There's also new Closed Club functionality and Stock Replies. Ya boy penned a post about it last month. Feel free to give it another check - it includes more details on the aforementioned: Btw, one of my favorite parts of the new custom Activity Streams is the decay feature. 😎 Please be sure to have full working backups before updating. The upgrade should go smoothly, but just in case it's always great to have them. Now, onto the updates! Since we didn't loop you in with all of the fixes and updates last week, here's a comprehensive list of all the awesomeness the dev team knocked out the past two weeks. Legit 🤯 Sink your teeth into these then drop us a line in the comments and let us know what you think! - Fixed members REST endpoint responsible to award a badge. - Added the ability to quickly navigate between Node permissions and Group permissions in the AdminCP. - Fixed an issue where deleting members my leave orphan status update reports. - Fixed an issue where json-ld info can show the wrong author details after a display name change. - Fixed an issue where deleting members may leave orphan status update reports. - Fixed an issue where json-ld info can show the wrong author details after a display name change. - Improved the reliability and security of using the (S)FTP upgrade method in the AdminCP. - Fixed an error when viewing members with Commerce purchases in the admin control panel. - Fixed an issue where it was not possible to resend validation emails if internal logins were disabled. - Added a Limit of 1 to the First Comment query to improve performance. - Fixed an issue where Blog json-ld output may contain invalid HTML output. - Fixed members REST endpoint responsible to award a badge. - Fixed an issue where it was not possible to create new default database inserts in the developer center. - Fixed an issue where links to user profiles were shown in some circumstances where profiles could not be viewed. - Added the ability to optionally require a billing address for subscriptions. - Fixed an issue where adding similar events could cause a blank cover photo to be saved. - Fixed an issue where incoming emails may be rejected incorrectly when the x-auto-response-suppress header is set. - Added a Limit of 1 to the First Comment query to improve performance. - Fixed incomplete administrator logs when performing actions on achievement rules. - Fixed an issue where promoting content may cause items to appear twice in our picks. - Fixed a database error shown when managing followed content for Gallery images. - Added a Limit of 1 to the First Comment query to improve performance. - Improved the achievement new rank and new badge emails. - Fixed an issue where deleting members may leave orphan status update reports. - Fixed an error thrown when sending Easypost shipping notification emails. - Fixed an issue where, after splitting a hidden content item, the comments show as hidden without the option to un-hide from within the new content item - Added Achievement filters for bulk mail, group promotion and automatic moderation - Fixed an issue that may prevent new badge emails from being sent. - Added a Limit of 1 to the First Comment query to improve performance. - Added member's rank and achievement point total to the member CSV export. - Fixed an issue where task progress bars could show percent completion above 100% - Fixed an issue where deleting members may leave orphan status update reports. - Fixed an issue where it was not possible to resend validation emails if internal logins were disabled. - Fixed an issue where word filters may not work correctly when editing titles inline. - Added a Limit of 1 to the First Comment query to improve performance. - Changed the stream subscription email to include max. 10 items. - Fixed an issue that may prevent new badge emails from being sent. - Fixed an issue where the confirmation modal for stream subscriptions would show a broken confirmation description. - Changed the activity stream subscription emails to filter only by the create date. - Fixed a minor link target issue with the add phrase button when editing blocks. - Fixed an issue where removing a currency can cause errors in search results. - Fixed an issue where reviews may not be correctly indexed with Elastic Search.

Appreciate the followup. Sorry that I missed some of your posts! Been seeing a lot of good stuff though. You're not coming off any type of way :] you're sharing your thoughts in a constructive way and that's greatly appreciated. If you didn't care about IC you wouldn't be exerting the energy to share and contribute. 👌 I'd like to push back a little that your words didn't have any effect. To the contrary! We want to provide the best user experience as possible, and in my opinion we're always going to have an uphill challenge towards betterment (because change and improvement isn't always easy and that's ok). One of the coolest things about our new support structure is that we're trying to be more visible and communicative by posting on the forums (versus in email tickets). That includes topics like this one - where we're openly discussing the pros and cons of a swift change. Ultimately, we recognize that before we make changes that can impact a community, we need to address it beforehand. One of the tough parts about these kinds of changes is there's always going to be some pushback. That's probably the hardest thing for us (at least for me). But at the end of the day we want to be on the same page with you. This is a team effort - if we didn't have people using the platform, we couldn't exist. We're going to continue to work towards being as transparent as possible with you. Apologies if we missed the mark! 🙏

Haha! Soon! They are almost all done being edited. Just gotta finish that, upload the rest to our YouTube channel (or possibly native right into IC) and then get them formatted in slick way so people can consume. Excited to share it. :]

I also use this to send automated emails and PMs upon registering. It's been a great way to connect with new members right off the bat. 🙂

Hey @Pavel Chernitsky 👋 Thanks for offering your insight! I do agree we could've executed this a bit better. Regarding the sample size and all that, I agree with you that although there wasn't a huge group voting, the people that did participate were heard loud and clear. So whether that's 50 or 500 people, it still matters and each individual vote is valuable. As a team, we definitely don't want to embody this notion that we are better than anyone. At the end of the day, we're all people, and we make mistakes some times, but at the end of the day we want to grow, learn and become better. If we came off as sticking our noses up than I apologize for that; definitely not our intention! Regarding the feature change, yeah it definitely is no bueno that some communities were adversely affected by this. That's not our aim. 😩 Curious, what are your thoughts on how to move forward from here? The toothpaste is out of the tube so-to-speak. Is there something we can do to help make this a better experience moving forward? Thanks again for the comment. Looking forward to hearing back. 🤲

Appreciate you writing this the way you did.

Hey @slarrr - appreciate you taking the time to write that out. Very well said, constructive and understanding! Thank you. I do agree there's room for improvement regarding the user testing process, as well as listening to feedback, assessing as a team and then taking action (or not). Regarding the developer / support replies - I'm sorry you haven't had the best experience. I know the team cares about you all as well as the platform and are honestly working hard to make this the best user journey possible. We have been putting a lot more focus into community forum support so there are likely still a few growing pains we're working through. Nonetheless I hear you and will take this back to the team! I do want to add my unsolicited two cents and say they are doing a good job 😇 . However, I can recognize we are always looking to up our game, same goes for myself. That's the spice of life isn't it 😅 Apologies for how we handled the custom member titles change. We tried our best to shine a light on this before the update, but in hindsight there could've been more flexibility provided. When it comes to feature changes, we're always in between a rock and a hard place, but ultimately we just want to improve and make things better. That's kinda fluffy, but it's the truth. We'll absorb what you mentioned so we can continue improving (both as a platform and team). Thank you again for how you offered the feedback as well as being an Invision Community loyalist! Let me know what you think!

Hey @growroom! Right now we don't have any concrete plans to develop a built-in LMS application, however... I did create a mini course that includes 10 videos slated for Invision Community beginners. Those videos will somehow need to take the user on a little guided journey, so that might be an opportunity for us to crack the door here. Curious, what basic functionality would you like to see? Prefacing this that this doesn't mean we are actively developing this, but inquiring minds want to know 😄

Hey there - I had experienced a similar issue on my own community - as a result they disabled oembed for Instagram / FB posts. I ended up linking them to an updated Privacy Policy and they approved my app in 12 hours. Do you have a privacy policy in place? Did you link to it in the app setup section in FB Developers? BTW - if you don't have a Privacy Policy or know how to create one to include the info they want, I would suggest going on Fiverr and hiring someone to draft one up for you. I've done that in the past for other agreements and it was a great experience. Hope that helps.

Loving the team work! @Mark Empson let us know if @usmf's suggestions helped.

Lmao. Hey team! I was at a #FreeBritney rally 😅 It was an incredible day being at the courthouse with everyone when the judge decided to suspend Jamie Spears. Just an FYI my community is BreatheHeavy.

Appreciate the kind words/feedback!

Happy Hump Day, fam! I'm bringing this very special Hump Day post from our headquarters in Lynchburg, Virginia. @Ryan Ashbrook, @Matt Finger, @Marshall Slemp and myself flew in from all over the U.S. to join forces with @Charles, @Olivia Clark and @Rikki to A.) meet in person and B.) dream up some exciting new projects! Spoiler alert: we have some pretty exciting things in the works! Olivia is helping us channel our creative energies into effective workflows. Seeee? Speaking of projects, have you had a chance to check out our website refresh? I'd love to point you in the right direction 😏 namely our Innovate section. It's beautiful 🥲 . Curious, what are your thoughts? Content Discovery Visitor Engagement Community Management Integration Achievements Mobile Customize Next up is 4.6.7 Beta 1... it's available now! It includes our new Activity Streams subscription feature, extended Closed Clubs functionality and Stock Replies! And if that wasn't enough Invision Community magic, check out a list of updates/fixes we've knocked out since we last spoke: - Fixed an issue where converted mentions may contain a static URL (breaking them if you change your domain). - Fixed an error that could occur if the Converter tried to delete a content link. - Fixed an issue with tag statistics immediately after a conversion. - Fixed a niche issue where an error could occur if a PayPal Subscription notification arrives after the Subscription is cancelled. - Fixed an issue where it wasn't possible to edit a subscription expiry date. - Fixed an issue that could cause a slow query to run when sending email if a large number of emails have previously failed. - Fixed an issue with the Frontend Theme Editor occurring with PHP8. - Added Stream Subscriptions. - Fixed the broken "Buy" link inside file embeds. - Fixed an issue with some topics not being hidden (but their posts were) after converting from vB5. - Fixed a potential issue adding tags to content when using PHP 8. - Added the ability to quickly navigate between Node permissions and Group permissions in the AdminCP - Made Profile Completion steps non-copyable. - Fixed members REST endpoint responsible to award a badge. Alright folks, that does it for now. If you have any comments, questions or concerns, drop us a line in the comments. We're here for you!!

Nice suggestion! We were thinking of possibly implementing tags somehow. This would be a great thing to discuss in its own dedicated topic 🥲 Appreciate the feedback!

Appreciate the kind words and the reconsideration!

Come here 🥲

Appreciate you saying that!! 🥲

🔥 Great idea. It'd be a good way to showcase some information that one may want to be concealed for all minus IC staff.

Appreciate the response 🙏 One cool thing about asking questions in the forum (generally speaking) is that it's likely going to also help someone in the future. Not to get meta, but it's paying it forward in a way. 🥲