Matt

When we speak to community moderators of busy sites about what they want to see in future Invision Community versions, most ask for ways to improve daily workflows. Community moderators are at the heart of every community, and those working with busy sites quickly find that repeating the same tasks reveals ways to save clicks and precious time. We recently released our alert system, which is a great way to get information to a single user or an entire group of members. Alerts can be set so the members have to reply before they can continue interacting with the community. Invision Community's November release now allows moderators to send a personal alert message to the author of the content they are moderating when their content is hidden, split, locked or moved. This video takes you through the workflow when hiding a comment. Combining the alert feature into the moderation workflow makes it easier to inform your members that you've taken action on their content. For example, you may notice a member posting a topic in the wrong forum. It's now straightforward to move the topic and let the author know why it's been moved and where to find it. Perhaps you've had to hide some content that doesn't fit your community guidelines. You can now let the author know when hiding the topic and the reason it's been hidden. Informing your members why you've taken action on their content helps educate, remind them of your community guidelines when needed and prevent confusion when they cannot locate the content they recently posted. Making a personal connection when moving or hiding a member's content helps keep a positive relationship throughout the community. Viewing alert replies While we were at it, we have also made it easier to track and respond to alert replies when sending them to large numbers of members. From November onwards, you will see the number of replies sent to your message when viewing alerts in the Moderator Control Panel. Clicking the reply count will show all personal message replies to that alert via a top-level filter. This new time-saving feature will come to all Invision Community platforms in November. @Daniel F proudly led development of this feature. 👏 We'd love your thoughts; let us know in the comments!

Welcome to our September developer's update! I can say with some confidence that both the Invision Community team and our marketplace developers have had a busy September as we prepare for PHP8. Thank you for your patience with this necessary step. As I've mentioned elsewhere, PHP8 is a pretty big jump and is much more strict about many things, and now throws fatal errors when before it would have been a harmless notice. PHP7 is now end of life, and security updates will no longer be available from November. Preparing for PHP8 I've talked about this on the forums a lot over the last few weeks, but I'll summarise the timeline here so you can prepare your plugins and apps to be PHP8-ready. September release (4.7.2): The PHP8 scanner will disable any plugins and applications that would cause issues with PHP8, but Invision Community owners can re-enable them if they choose to do so. October release (4.7.3): A warning shows in the AdminCP if Invision Community is installed with PHP7. As of October, the PHP8 scanner will disable plugins, but they can be re-enabled. November release (4.7.4): The PHP8 scanner will disable plugins and applications found not to be PHP8-ready. They cannot be re-enabled via the AdminCP. The only way to re-enable them is to upload a new version. Code changes to be aware of October hasn't been the biggest of releases, but it does come with the new Events front-end for Calendar, and this changed the parameter signature for getItemsWithPermission(), which is probably the most overloaded method we have. The new parameter signature is as follows: public static function getItemsWithPermission( $where=array(), $order=NULL, $limit=10, $permissionKey='read', $includeHiddenItems=\IPS\Content\Hideable::FILTER_AUTOMATIC, $queryFlags=0, \IPS\Member $member=NULL, $joinContainer=FALSE, $joinComments=FALSE, $joinReviews=FALSE, $countOnly=FALSE, $joins=NULL, $skipPermission=FALSE, $joinTags=TRUE, $joinAuthor=TRUE, $joinLastCommenter=TRUE, $showMovedLinks=FALSE, $location=NULL ) Note, $location has now been added to the list. If you overload getItemsWithPermission then you will need to update any hooks with his new parameter, or it will be flagged via the PHP8 scanner. The reason for this addition is to allow an easier way to get items via a latitude and longitude lookup. If you manage this elsewhere, you might find using getItemsWithPermission a much simpler way. @Daniel F has also been working on improving the GraphQL API, and the GraphQL library has been updated to 14.11.6. We'll cover the upcoming GraphQL changes in a future blog. Deprecations Invision Community is a mature product, and some features and code that we added in the past no longer make sense, work correctly or are no longer appropriate for a modern platform running on well-maintained servers. You can see the upcoming deprecations in this topic. I suspect the biggest change will be removing the option to allow Display Names to form part of the authentication credentials when logging in, which is coming out in November. The other to watch for is the removal of the sockets fallback for when curl is not installed on the server or using a version older than 7.36. It's worth noting that curl 7.36 was released in March 2014 and now has hundreds of CVEs (known vulnerabilities) however, our techs still come across the odd server still using an older version. We will likely run AdminCP notifications to warn those affected of the upcoming socket fallback deprecation nearer the time, as it has no version attached. Just be mindful of this in your own apps if you use sockets directly for anything. You may also note that we've started adding deprecations to the release notes. As a reminder, we do not approve Marketplace submissions that restore functionality we've removed. That's it for September! Hopefully, it won't take too long to run through your apps and plugins. As always, comment here, or reach out via the forums if you need anything clarifying. Happy developing!