NewsBot

Can you start from a stock Invision Community 5 installation and have it themed, customized, and a new homepage built in under an hour without relying on custom templates and coding? Yes, and Jimi Wikman, a long-time Invision Community customer, did just that in his latest YouTube video. Jimi has over twenty-five years of experience in development and twenty years of experience in graphic design. Invision Community 5 has been in testing for a few months now, and Jimi produced this amazing walkthrough of Invision Community 5's new page editor and theme editor while re-creating his own site. Our vision for Invision Community 5 was to put the power into the hands of everyone, not just those who are proficient in PHP, HTML, and CSS. Jimi's video shows this vision as a reality as he moves through the theme editor to create his custom theme, and the page editor to build a custom homepage. Sit back and enjoy watching Jimi put together a new site. Thanks Jimi! If you're interested in testing Invision Community 5 for yourself, just join our Beta Testing Club. View full blog entry Wyświetl pełną treść wpisu

Can you start from a stock Invision Community 5 installation and have it themed, customized, and a new homepage built in under an hour without relying on custom templates and coding? Yes, and Jimi Wikman, a long-time Invision Community customer, did just that in his latest YouTube video. Jimi has over twenty-five years of experience in development and twenty years of experience in graphic design. Invision Community 5 has been in testing for a few months now, and Jimi produced this amazing walkthrough of Invision Community 5's new page editor and theme editor while re-creating his own site. Our vision for Invision Community 5 was to put the power into the hands of everyone, not just those who are proficient in PHP, HTML, and CSS. Jimi's video shows this vision as a reality as he moves through the theme editor to create his custom theme, and the page editor to build a custom homepage. Sit back and enjoy watching Jimi put together a new site. Thanks Jimi! If you're interested in testing Invision Community 5 for yourself, just join our Beta Testing Club.Wyświetl pełną treść wpisu

Can you start from a stock Invision Community 5 installation and have it themed, customized, and a new homepage built in under an hour without relying on custom templates and coding? Yes, and Jimi Wikman, a long-time Invision Community customer, did just that in his latest YouTube video. Jimi has over twenty-five years of experience in development and twenty years of experience in graphic design. Invision Community 5 has been in testing for a few months now, and Jimi produced this amazing walkthrough of Invision Community 5's new page editor and theme editor while re-creating his own site. Our vision for Invision Community 5 was to put the power into the hands of everyone, not just those who are proficient in PHP, HTML, and CSS. Jimi's video shows this vision as a reality as he moves through the theme editor to create his custom theme, and the page editor to build a custom homepage. Sit back and enjoy watching Jimi put together a new site. Thanks Jimi! If you're interested in testing Invision Community 5 for yourself, just join our Beta Testing Club. Wyświetl pełną treść wpisu

Invision Community 4.7.19 contains a significant upgrade to the Report Center to improve compliance and professionalism within the reporting workflow. The existing report center functions well enough but lacks some of the more professional tools modern communities need when managing complaints. In previous versions, a member or guest reported a piece of content, such as a comment or topic, which was then handled by the community team behind the scenes, and the report closed when dealt with. It was up to the community team to inform the original content author if any decision was made and to inform those who reported the content of the outcome. The Invision Community November update improves the report center with a better workflow, including asking those reporting the content the reason for the report, notifications on the report outcome, and the content author being notified as to why their content was moderated. Now, a report can be closed as valid or rejected. These new completion statuses allow you to signal whether your team found the report valid or whether you decided that the report was not required and thus rejected. Let's look at what has changed. Admin Control Panel The initial Report Center interface now has various options to control how the public reporting form works. From here, you can configure how reporting works for guests, whether they are required to leave a name (email is always required), and whether a message is required for the report. Content Author Notifications In this section, you can create notification templates that can optionally be sent to the author of the original content when choosing to complete or reject the report. Report Types In previous versions, report types were solely for automatic moderation. In this update, we've brought report types to both automatic moderation and public reporting. Gathering the reason content has been reported is vital in deciding the outcome. Each report type can also accept a message sent to the person who made the report depending on the valid or rejected outcome via an email notification that can be opted out of. Reporting Content Now, when a logged-in member or a guest user reports content, they can select from one of the pre-configured report types. If a guest is making the report, they are asked to leave their details along with a message to accompany the report. Managing Reports When managing reports via the ModCP, the interface has been updated to make the status of the report and the reasons for the report clearer. This screenshot shows green rows, which are new reports that still need to be managed by the team, along with yellow rows, which are currently under review. Each row of reported content can have multiple reports from different members, and the reason for those reports (such as Spam, Offensive, etc) is shown in labels. Viewing reported content now shows more detail in the user reporting section. If a guest has reported the content, the guest's name and supplied email address are shown, and clicking this allows you to send an email to them. The reason for the report is now shown. For each user report, you can change the submission reason, and this change is logged in the moderator comments to create an audit trail. You can now mark the report as Complete or Rejected, which will trigger an email for all those who have reported this piece of content. You can also send one of the notification templates to the content author to update them on why their content has been moderated. This email to each person who reported the content contains the date, content title, and reason for reporting, along with the pre-configured message for the report outcome. In this case, the report was flagged as valid, and the message to the person who reported it confirmed the outcome. Putting it together These changes help automate notifying both the author of the content and the person who reported the content on the outcome. Let's look at an example flow to understand how these new tools help the workflow. In this example, User A (Author) creates some content, and User B (Reporter) decides to report this content, choosing "Offensive" as the reason for the report. The moderation team picks up the report, examines the reported content, and decides that the report is valid, so they mark the report as complete and choose to use a notification template to tell the content author (User A) that their content has been removed. As the report has been flagged as complete, the person who reported the content (User B) receives an email telling them the report has been upheld and action has been taken. We hope these changes improve your experience with the report center. Let us know what you think below. View full blog entry Wyświetl pełną treść wpisu

Invision Community 5.0.0 has reached a huge milestone; we're now in open beta testing. After numerous alpha releases, we're ready to move forward with the last stage of development and testing. The beta stage is primarily just fixing bugs and tweaking existing features and we're confident that the beta testing stage will run smoothly as its already stable and being used on a handful of production sites by brave souls who have upgraded immediately. Of course, we'd not recommend being so cavalier, especially if you are not very technical and do not have the time or patience to wait for fixes and risk broken functionality between beta releases! The good news is that you can use Invision Community 5 beta on a test installation, so you can set it up, and learn its new UI and feature set before planning your upgrade. The beta is available for both Invision Community Cloud customers, and Invision Community Classic customers. Invision Community Classic (Self Hosting) If you have an older license type (Invision Community Suite) and want to test Invision Community 5, then you are welcome to switch to the new v5 license in the client area. The renewal structure has changed, and all this is explained before you switch. If you have the classic license, you will then see the Invision Community 5 Beta download in your client area. Invision Community Cloud Our Cloud customers can request a time-limited v5 demo. Instructions on how to do this are in the Invision Community 5 Beta Testing Club. We're thrilled to move closer to a final release a year after Ehren revealed the "fresh new vision" for Invision Community 5. We'd love for you to join us in the Beta Testing Club and let us know what you think of Invision Community 5. Wyświetl pełną treść wpisu

Od około miesiąca współpracujemy z niewielką liczbą testerów alfa, aby uzyskać wstępne opinie i dopracować niektóre nowe funkcje. Teraz jesteśmy gotowi na więcej opinii, więc dzisiaj robimy kolejny krok w testowaniu! Otworzyliśmy nową stronę podglądową Invision Community 5, którą każdy może używać, wyszukiwać błędy i oferować swoje opinie. Nowa strona podglądowa ma obszar do przekazywania opinii i zgłaszania błędów, więc prosimy, aby korzystać z tych obszarów na stronie podglądowej, zamiast zamieszczać swoje myśli tutaj. 👉 https://preview.invisionalpha5.com/ Dostępne są obecnie dwa motywy. Pierwszy to bardziej "klasyczny" wygląd, który będzie Ci od razu znany. Drugi motyw ma włączone nowsze widoki, takie jak pasek boczny i tryb feed dla forów. Możesz przełączać się między nimi, a także zmieniać opcje układu w ustawieniach swojego konta. Wszystkie te informacje są zawarte w temacie powitalnym tamże. Baw się dobrze i daj nam znać, co myślisz! Wyświetl pełną treść wpisu

This is our August maintenance release. Wyświetl pełną treść wpisu

This is our August maintenance release. Wyświetl pełną treść wpisu

Introducing new Page Builder tools in Invision Community 5 Widgets are an incredibly powerful tool for displaying curated content of your choice on any page of your community - and despite the extensive array of settings for customizing their data, they've often been limited in terms of their design options. But this changes thanks to the new Page Builder tools in Invision Community 5! Widget Designs Previously in version 4, widgets would often have 2 designs: one for the main content area and a more minimal version for the sidebar. This worked well, but it meant your page was very limited in terms of design as you'd typically need to use the same table-like layout for most widgets. Anything beyond that would typically require a custom block to be coded, often with additional HTML or CSS. Version 5 offers much more customization by allowing you to change the design of each widget with the click of your mouse - no coding necessary! When dragging a widget onto your page, a new toolbar at the bottom of the page appears, holding all of the widget design options. Lets take a look at some below! Grid A familiar a very layout used elsewhere in the suite, the Grid design neatly aligns entries in a grid with a large cover photo sitting up top. A great combination of visual imagery alongside meta data such as entry descriptions. Featured A spacious list and a great way to feature content, pardon the pun. Wallpaper Perfect for content which includes uploaded cover photos or thumbnails! The Wallpaper design stretches each image to make it occupy the entire background, overlaid by a minimal amount of content. A subtle gradient sits behind the text to ensure it's easy to read, even on detailed images. Rows (table) The Rows design is a very familiar one, used very often throughout other areas of the suite. Content is displayed in a neat table, that collapses into a more compact design on small screens. Minimal Great for displaying a lot of content in a compact area! Minimal only shows primary information and hides meta data such as entry descriptions and stats. Great for sidebars, or areas with limited width. Minimal Grid The Minimal Grid design removes large meta information and displays content in a nice, compact grid. A nice option for displaying a lot of content while being cautious of vertical space. Carousel The Carousel option is quite unique because it can be applied in tandem with other widget designs, and is a perfect way to make the existing layouts even more compact. For example, by default, the Wallpaper design is aligned as a grid, but with the Carousel option enabled, the layout is converted into a carousel instead: Carousel-widget.mp4 Here's another example, using the Featured and Carousel options: Blog - featured carousel.mp4 Fun fact for developers: All of these designs use the exact same HTML structure; the only thing that differs is the class name on the parent element. This makes it incredibly easy to adjust the design of your own widgets without needing to manually code multiple layouts. Widget Areas Version 4 was often quite limiting when it came to aligning widgets in pages. Widgets could be dragged into a stacked, vertical list but that was typically as far as you could go in terms of design. Version 5 introduces a new concept called Widget Areas, which allow you to align multiple widgets in a variety of ways. Lets take a look! To create an area, you simply need to drag one widget on top of another. Blog - areas.mp4 By default, they'll align themselves into a grid, but can be realigned with ease by using the toolbar at the bottom of the page. The toolbar also holds controls for adjusting the width of widgets, and the gap between them: Blog - alignments.mp4 Widget Designs and Widget Areas in Version 5 make it incredibly easy to create a completely custom page in a matter of seconds. We're really excited for you to get your hands on these new tools in Invision Community 5, and are looking forward to seeing all of these new page designs in the wild, in the very near future!Wyświetl pełną treść wpisu

Introducing new Page Builder tools in Invision Community 5 Widgets are an incredibly powerful tool for displaying curated content of your choice on any page of your community - and despite the extensive array of settings for customizing their data, they've often been limited in terms of their design options. But this changes thanks to the new Page Builder tools in Invision Community 5! Widget Designs Previously in version 4, widgets would often have 2 designs: one for the main content area and a more minimal version for the sidebar. This worked well, but it meant your page was very limited in terms of design as you'd typically need to use the same table-like layout for most widgets. Anything beyond that would typically require a custom block to be coded, often with additional HTML or CSS. Version 5 offers much more customization by allowing you to change the design of each widget with the click of your mouse - no coding necessary! When dragging a widget onto your page, a new toolbar at the bottom of the page appears, holding all of the widget design options. Lets take a look at some below! Grid A familiar a very layout used elsewhere in the suite, the Grid design neatly aligns entries in a grid with a large cover photo sitting up top. A great combination of visual imagery alongside meta data such as entry descriptions. Featured A spacious list and a great way to feature content, pardon the pun. Wallpaper Perfect for content which includes uploaded cover photos or thumbnails! The Wallpaper design stretches each image to make it occupy the entire background, overlaid by a minimal amount of content. A subtle gradient sits behind the text to ensure it's easy to read, even on detailed images. Rows (table) The Rows design is a very familiar one, used very often throughout other areas of the suite. Content is displayed in a neat table, that collapses into a more compact design on small screens. Minimal Great for displaying a lot of content in a compact area! Minimal only shows primary information and hides meta data such as entry descriptions and stats. Great for sidebars, or areas with limited width. Minimal Grid The Minimal Grid design removes large meta information and displays content in a nice, compact grid. A nice option for displaying a lot of content while being cautious of vertical space. Carousel The Carousel option is quite unique because it can be applied in tandem with other widget designs, and is a perfect way to make the existing layouts even more compact. For example, by default, the Wallpaper design is aligned as a grid, but with the Carousel option enabled, the layout is converted into a carousel instead: Carousel-widget.mp4 Here's another example, using the Featured and Carousel options: Blog - featured carousel.mp4 Fun fact for developers: All of these designs use the exact same HTML structure; the only thing that differs is the class name on the parent element. This makes it incredibly easy to adjust the design of your own widgets without needing to manually code multiple layouts. Widget Areas Version 4 was often quite limiting when it came to aligning widgets in pages. Widgets could be dragged into a stacked, vertical list but that was typically as far as you could go in terms of design. Version 5 introduces a new concept called Widget Areas, which allow you to align multiple widgets in a variety of ways. Lets take a look! To create an area, you simply need to drag one widget on top of another. Blog - areas.mp4 By default, they'll align themselves into a grid, but can be realigned with ease by using the toolbar at the bottom of the page. The toolbar also holds controls for adjusting the width of widgets, and the gap between them: Blog - alignments.mp4 Widget Designs and Widget Areas in Version 5 make it incredibly easy to create a completely custom page in a matter of seconds. We're really excited for you to get your hands on these new tools in Invision Community 5, and are looking forward to seeing all of these new page designs in the wild, in the very near future! View full blog entry Wyświetl pełną treść wpisu

We recently announced the new Invision Community 5 editor which adds many new exciting features such as semantically correct header tags, custom boxes and more. As the new editor is a step forward in technology, some legacy features had to be left behind. We received a lot of messages about these changes, and have created new tools based on that feedback to ensure you still have the tools you need. The new features are based around restricting some high level editor functionality for specific member groups and enabling an easy way to add custom embeds. Permission Levels Invision Community 5 puts a lot of new tools in the editor, including header tags, boxes and positioning tools. These are useful features, but perhaps you do not want your members changing the semantic structure of the page by adding H1 tags. Or maybe you don't want them being able to add custom boxes wtih colors. Based on this feedback, we have introduced a permission levels system. At the heart of the system lies three editor permission levels: Minimal, Standard and Advanced. Specific editor features are assigned to one or more levels. For example, you may only want header tags and content boxes to be for the 'advanced' permission level which only administrators can use. These permission levels are configurable via the Admin Control Panel. When is Each Restriction Level Used? Now that we have set up the permission levels, we need to apply them to member groups. We do this by simplying heading over to the Member Groups section of the Admin Control Panel. In the "Content" section of that form, there are two new options: Default Editor Restriction Level: This is the restriction level the group uses by default, for example in Forum Topics and Blog Posts. Editor Restriction Level for Comments: This is the level used for Comments (including Topic Replies) throughout the Community. When a member has multiple groups, they will use the most permissible editor setting out of all groups. Custom Embeds With news that, because editor technology has moved on, the ability to toggle into 'source mode' and directly edit the underlying structure of the editor document was removed, many people told us they used that feature to add custom iframes from specific services they use. We understood the need for custom embeds, and we've added the option to create iframe elements with any whitelisted URL from a link. CleanShot 2024-06-20 at 15.49.43.mp4 Additionally, iframes created this way have configurable height and width so you can resize to your liking This feature has two editor permissions: "Can Embed External Content," and "Can Convert Links to iframes". Adding iframes into a post can potentially be a security issue, so strong controls are needed to ensure there isn't abuse of this system. The editor will only allow links to be converted to iframes if the domain has been whitelisted. The whitelist exists in the new tab, Admin Control Panel > System > Posting & Editor > Embeds. The feature can also be entirely disabled from here. That wraps up this round of changes based on your comments. We hope that you enjoy this update to our Invision Community 5 editor and we always appreciate your feedback. View full blog entry Wyświetl pełną treść wpisu

We recently announced the new Invision Community 5 editor which adds many new exciting features such as semantically correct header tags, custom boxes and more. As the new editor is a leap forward in technology, some legacy features had to be left behind. We received a lot of messages about these changes, and have created new tools based on that feedback to ensure you still have the tools you need. The new features are based around restricting some high level editor functionality for specific member groups and enabling an easy way to add custom embeds. Permission Levels Invision Community 5 puts a lot of new tools in the editor, including header tags, boxes and positioning tools. These are useful features, but perhaps you do not want your members changing the semantic structure of the page by adding H1 tags. Or maybe you don't want them being able to add custom boxes with colors. Based on this feedback, we have introduced a permission levels system. At the heart of the system lies three editor permission levels: Minimal, Standard and Advanced. Specific editor features are assigned to one or more levels. For example, you may only want header tags and content boxes to be for the 'advanced' permission level which only administrators can use. These permission levels are configurable via the Admin Control Panel. When is Each Restriction Level Used? Now that we have set up the permission levels, we need to apply them to member groups. We do this by simplying heading over to the Member Groups section of the Admin Control Panel. In the "Content" section of that form, there are two new options: Default Editor Restriction Level: This is the restriction level the group uses by default, for example in Forum Topics and Blog Posts. Editor Restriction Level for Comments: This is the level used for Comments (including Topic Replies) throughout the Community. When a member has multiple groups, they will use the most permissible editor setting out of all groups. Custom Embeds In response to news that the ability to toggle into 'source mode' and directly edit the underlying structure of the editor document was not implemented because editor technology has moved on, many people told us they used that feature to add custom iframes from specific services they use. We understood the need for custom embeds, and we've added the option to create iframe elements with any whitelisted URL from a link. CleanShot 2024-06-20 at 15.49.43.mp4 Additionally, iframes created this way have configurable height and width so you can resize to your liking This feature has two editor permissions: "Can Embed External Content," and "Can Convert Links to iframes". Adding iframes into a post can potentially be a security issue, so strong controls are needed to ensure there isn't abuse of this system. The editor will only allow links to be converted to iframes if the domain has been whitelisted. The whitelist exists in the new tab, Admin Control Panel > System > Posting & Editor > Embeds. The feature can also be entirely disabled from here. That wraps up this round of changes based on your comments. We hope that you enjoy this update to our Invision Community 5 editor and we always appreciate your feedback.Wyświetl pełną treść wpisu

Invision Community v5 takes a fresh approach to tagging and content discovery. It overhauls the concept to bring content across different sections together with a beautiful new tag page. Tagging is a powerful concept but underused with Invision Community 4 due to overly complex interfaces in different areas of the suite, a confusing open tagging model option and no real benefit in content discovery beyond a simple list of content items. A driving force behind Invision Community 5 is the question of how we can help time-pressured community members find the content that most interests them. Invision Community has robust taxonomy through forum and category structures, but what about content in less visible areas such as Blogs, galleries or Events? How can we bring those together to homogenise the type of content and focus on the content itself? Taxonomy via tagging across all applications in the community suite is the answer. However, we needed to re-approach how tagging was implemented in the Invision Community to bring our new vision to life. Out with the old The current tagging system is implemented loosely, allowing open tagging, which is more akin to hashtags than high-level taxonomy. Allowing forums, albums, and blog categories to define their own tags turns tagging into more of a status label, which does nothing to help bring disparate content together. In with the new With a new focus on taxonomy and content discovery, we set about rebuilding tagging for Invision Community 5. The UI to tag items is the same, but now each defined, globally available tag has its own page with cover image and ability to feature items within that tag page. A uniform approach to different content items in the UI breaks down the barrier between content types and focuses solely on the content. Tags featured on its page are automatically displayed on the community Featured Content page. Finally, tags can now be followed, allowing your community to get a daily or weekly digest of all new tagged items, bringing people back to read more of the content they love. Let’s take a closer look In Invision Community 5, all tags are defined in the Admin Control Panel. The ability to use open tagging and per-node tags has been removed, but don’t worry—the upgrade system will offer conversion for those tags. Once defined, the tags are available for all content types and feature on a dedicated new tag page. This page features cover photos and more information on the tag via a description. Content from across your suite will be displayed on this page. If a single piece of content has multiple tags, it will appear on every relevant tag page making it easy to have content in multiple areas. If you want to permanently or temporarily feature individual content, perhaps your latest news or product release, you can do so right from the tag page. Featured content will show on the community’s Featured Content Page. Blurring the lines Now that we have an attractive and focused page for each tag, we can start to blur the lines between applications and, indeed, forums and categories, offering a new way to organise content. For some communities, the need for multiple forums to categorise content is diminished, and instead, tagging can be used to separate and find content from across the community. Tags can be featured in the menu system, offering new ways into your community for new visitors, regular community members, and even those who visit daily. Invision Community 5 is fearless in challenging past decisions or streamlining features to make them stronger and more focused. Our new approach to tagging takes a vague and underutilised concept and pushes it front and centre in any content strategy. How will you use it in your community?Wyświetl pełną treść wpisu

Invision Community v5 takes a fresh approach to tagging and content discovery. It overhauls the concept to bring content across different sections together with a beautiful new tag page. Tagging is a powerful concept but underused with Invision Community 4 due to overly complex interfaces in different areas of the suite, a confusing open tagging model option and no real benefit in content discovery beyond a simple list of content items. A driving force behind Invision Community 5 is the question of how we can help time-pressured community members find the content that most interests them. Invision Community has robust taxonomy through forum and category structures, but what about content in less visible areas such as Blogs, galleries or Events? How can we bring those together to homogenise the type of content and focus on the content itself? Taxonomy via tagging across all applications in the community suite is the answer. However, we needed to re-approach how tagging was implemented in the Invision Community to bring our new vision to life. Out with the old The current tagging system is implemented loosely, allowing open tagging, which is more akin to hashtags than high-level taxonomy. Allowing forums, albums, and blog categories to define their own tags turns tagging into more of a status label, which does nothing to help bring disparate content together. In with the new With a new focus on taxonomy and content discovery, we set about rebuilding tagging for Invision Community 5. The UI to tag items is the same, but now each defined, globally available tag has its own page with cover image and ability to feature items within that tag page. A uniform approach to different content items in the UI breaks down the barrier between content types and focuses solely on the content. Tags featured on its page are automatically displayed on the community Featured Content page. Finally, tags can now be followed, allowing your community to get a daily or weekly digest of all new tagged items, bringing people back to read more of the content they love. Let’s take a closer look In Invision Community 5, all tags are defined in the Admin Control Panel. The ability to use open tagging and per-node tags has been removed, but don’t worry—the upgrade system will offer conversion for those tags. Once defined, the tags are available for all content types and feature on a dedicated new tag page. This page features cover photos and more information on the tag via a description. Content from across your suite will be displayed on this page. If a single piece of content has multiple tags, it will appear on every relevant tag page making it easy to have content in multiple areas. If you want to permanently or temporarily feature individual content, perhaps your latest news or product release, you can do so right from the tag page. Featured content will show on the community’s Featured Content Page. Blurring the lines Now that we have an attractive and focused page for each tag, we can start to blur the lines between applications and, indeed, forums and categories, offering a new way to organise content. For some communities, the need for multiple forums to categorise content is diminished, and instead, tagging can be used to separate and find content from across the community. Tags can be featured in the menu system, offering new ways into your community for new visitors, regular community members, and even those who visit daily. Invision Community 5 is fearless in challenging past decisions or streamlining features to make them stronger and more focused. Our new approach to tagging takes a vague and underutilised concept and pushes it front and centre in any content strategy. How will you use it in your community? View full blog entry Wyświetl pełną treść wpisu

Invision Community v5 takes a fresh approach to tagging and content discovery. It overhauls the concept to bring content across different sections together with a beautiful new tag page. Tagging is a powerful concept but underused with Invision Community 4 due to overly complex interfaces in different areas of the suite, a confusing open tagging model option and no real benefit in content discovery beyond a simple list of content items. A driving force behind Invision Community 5 is the question of how we can help time-pressured community members find the content that most interests them. Invision Community has robust taxonomy through forum and category structures, but what about content in less visible areas such as Blogs, galleries or Events? How can we bring those together to homogenise the type of content and focus on the content itself? Taxonomy via tagging across all applications in the community suite is the answer. However, we needed to re-approach how tagging was implemented in the Invision Community to bring our new vision to life. Out with the old The current tagging system is implemented loosely, allowing open tagging, which is more akin to hashtags than high-level taxonomy. Allowing forums, albums, and blog categories to define their own tags turns tagging into more of a status label, which does nothing to help bring disparate content together. In with the new With a new focus on taxonomy and content discovery, we set about rebuilding tagging for Invision Community 5. The UI to tag items is the same, but now each defined, globally available tag has its own page with cover image and ability to feature items within that tag page. A uniform approach to different content items in the UI breaks down the barrier between content types and focuses solely on the content. Tags featured on its page are automatically displayed on the community Featured Content page. Finally, tags can now be followed, allowing your community to get a daily or weekly digest of all new tagged items, bringing people back to read more of the content they love. Let’s take a closer look In Invision Community 5, all tags are defined in the Admin Control Panel. The ability to use open tagging and per-node tags has been removed, but don’t worry—the upgrade system will offer conversion for those tags. Once defined, the tags are available for all content types and feature on a dedicated new tag page. This page features cover photos and more information on the tag via a description. Content from across your suite will be displayed on this page. If a single piece of content has multiple tags, it will appear on every relevant tag page making it easy to have content in multiple areas. If you want to permanently or temporarily feature individual content, perhaps your latest news or product release, you can do so right from the tag page. Featured content will show on the community’s Featured Content Page. Blurring the lines Now that we have an attractive and focused page for each tag, we can start to blur the lines between applications and, indeed, forums and categories, offering a new way to organise content. For some communities, the need for multiple forums to categorise content is diminished, and instead, tagging can be used to separate and find content from across the community. Tags can be featured in the menu system, offering new ways into your community for new visitors, regular community members, and even those who visit daily. Invision Community 5 is fearless in challenging past decisions or streamlining features to make them stronger and more focused. Our new approach to tagging takes a vague and underutilised concept and pushes it front and centre in any content strategy. How will you use it in your community? View full blog entry Wyświetl pełną treść wpisu

As we find ourselves with our toes over the precipice of June; signalling the half way point of the year, I thought it's a good time for an update. Apologies southern hemisphere. Invision Community 5 has been in alpha testing for a while, and a small group have found a good number of bugs, and offered their thoughts and suggestions, some of which we've implemented. During this time we've wrapped up the new editor, a boat load of UI improvements and more. We are now ready for the next stage, which is to give our alpha testers their own Cloud v5 to test with. This opens up testing for the Admin CP, and all areas without using developer mode. v5 has a lot of changes to how CSS, JS and resources are managed. They are now built when we build the apps, and should never need rebuilding. We also store compiled templates now, so lots of slow eval() calls are no longer needed. In brief testing locally, it has made the entire platform super-fast. We are choosing to use a Cloud v5 to test with, rather than a traditional download for two reasons. The first is that using our hosting platform means we don't have to chase down issues with PHP, MySQL and unix versions which can be time consuming in the early stages. The second is that we're still writing the new build code, so we can't actually produce a versioned zip just yet. 😂 But fear not, downloadable versions will be coming at some point. We're aiming to have this alpha demo system ready next week, so if you want to help alpha test, drop a comment below. I want to keep the first round (1-2 weeks) fairly small or it becomes overwhelming sifting through the feedback and bugs but please do register your interest. In terms of functionality, we're wrapping up the tagging changes; I'd expect a blog on that next week. The final parts of the Pages app are coming together. We even tested an upgrade of this site to v5 to see how the Pages built pages looked, and much to all of our relief, it looks great with just a few CSS classes needing updating. It's been a long journey - and a little longer than we'd first hoped but we're getting closer to betas when the fun really starts. We're really proud of v5 and we hope you like what we've created. Wyświetl pełną treść wpisu

With over 20 years of experience developing with Invision Community (IP.Board, IBForums), I have a set of popular pre-made applications available for purchase. I am also available from time to time for custom integrations, SSO, data conversions. My time is currently limited, you may want to look elsewhere for custom requests but I do have some applications available for instant purchase: Mail Bouncer - https://ipb.silvesterwebdesigns.com/file/9-mail-bouncer/ Mail Bouncer is a fully automated app to handle email bounces and spam complaints via 3rd Party Email services SparkPost, SendGrid, Mandrill or Amazon SES/SNS. WordPress SSO - https://ipb.silvesterwebdesigns.com/file/7-wordpress-sso/ Replace the Invision Community front-end login with WordPress, using your WordPress accounts for sign-ins. Trader Feedback System - https://ipb.silvesterwebdesigns.com/file/8-trader-feedback-system/ Build trust in your community, or forum-based marketplace with the Trader Feedback System. Wyświetl pełną treść wpisu

In 2024, a secure WYSIWYG Editor has become a complex intricate thing. Copy/paste bundle files have largely been phased out in favor of complicated NPM repos and build tools. What was more or less just "HTML Manipulation" has evolved to abstract content models with dynamic rules on how to actually render the content to HTML. Then, for kicks, throw in the requirement that this editor needs to work in non-standard cases like the drag and drop page builder and live topics. The solution for Invision Community 5 is a new, custom, state of the art Editor built using ReactJS and Tiptap. In this article, I'll cover high level advantages, technical highlights and what's possible with 3rd party extensions. If you want to know more about the editor functionality, then see my other blog here. This story begins after we switched to CKEditor5 over a year ago. It is a decent product, but it had several serious limitations in a distributed platform like Community. We compared just about every editor currently on the market, and even considered building an editor completely from scratch, and ultimately landed on creating a custom editor using ReactJS and Tiptap. A lightweight package The v5 editor bundle size is small, coming to about 2mb in total (and it's split into separate chunks loaded ad-hoc, each one cached in the browser, so in practice much less data actually "loads"). After optimizing and tweaking CKEditor5, the smallest we could get it was over 50mb; now some build tool experts could probably wrangle that cke package to a smaller size, but I doubt it'd come anywhere close to Tiptap with all the features we added. It's also worth noting that, during operation, Tiptap had by far the lowest impact on browser memory consumption, and stubborn memory leaks never came up with this architecture. Part of this comes from taking advantage of ReactJS's stateful nature, but I think the most significant thing is that Tiptap doesn't have loose logic hanging around. How a modern WYSIWYG works (the short version) As I previously alluded to, editors today don't directly manipulate HTML at all. Instead, they store a Content Model according to a Schema. Different platforms may use different terms, but the content schema consists of the following Entities Nodes - Actual containers to put content in. Think blockquotes, headings or lists. Nodes are then stored in the document in a tree Text and Inline Nodes - Text is, well, text. It is exclusively just a string of characters; one way to think of it is, if it can go in a text message, it's text. Inline nodes, on the other hand, are not true "characters" but displayed inline with characters. Think custom emoticons and mentions. Marks - Styles and/or data that is applied over a range of text. Marks are similar to Nodes except that marks can overlap. For example, it if text is italic and bold, it makes no difference if it's bold inside italic or vise versa. Moreover, it it most accurate to simply say that text is just both italic and bold; this data is stored in Marks. In old editors, like CKEditor4, this was often just thrown into a "style" attribute which led to all sorts of issues and overhead processing. (These are not what CKEditor calls "marks" FYI, they call this concept "text attributes", in case anyone has existing CKE knowledge) All the above entities rely on Converters to generate them from HTML and then reconvert back into HTML. When the editor starts, it uses those converts to convert the initial data into the Content Model. Then, any change is made to the Content Model directly, which is continuously being converted back into HTML for the user to see. Security and Consistency The Schema and architecture add a layer of complexity but provide much better security, consistency and reliability because it only allows whitelisted content structures. For example, if I inserted something with the attribute style="color:white; transform: rotate(45deg)", the transform and color will be stripped out unless there's an existing converter to convert it to a Mark. Another example good example is simple bold styling: I can define several converters to parse the bold Mark: one for <b> tags, one for <strong> and one for style="font-weight: bold", and have them all convert back into a <strong> tag. Lastly, this gives us the assurance that, for any style, there is a user interface to manipulate and manage it. For this reason, source editing was removed because you won't ever need to fall back to source editing. I could go on for hours (seriously, don't get me started) but that's more than enough context to understand the rest of this article. Extending the Editor in Invision Another limitation of CKEditor5 in a distributed platform, where individual admins may want to customize, is that all Plugins have to be present at build not at runtime. This would pretty much mean no extending the editor, just rearranging the toolbar and flipping certain builtin features on and off. Fortunately, in Tiptap we were able to extend their internal node, mark and extension APIs. We'll have a more complete dev guide, but essentially all nodes, marks and extensions, which I'll just call "extensions" collectively, are rolled into the existing app system. There are 2 reasons we did this instead of just "buttons" like Invision 4, where you can just upload the CKEditor4 plugin zip file: It relies on using PHP to parse JavaScript to get things like the button title and stuff. If you create a valid plugin but define things in a slightly different way than expected, such as adding the name to the wrong line in the file, the plugin upload fails. Plugins/extensions are not buttons. Many CKE plugins have multiple buttons and many have none. This make management difficult because sometimes there isn't a button to remove and you have to reset all plugins, or you want to remove just one and 5 others disappear with it. Also, mostly all plugins add a new type of content; this type of content needs to be whitelisted Now, you may be thinking, "like the editor itself, won't the server side HTML Parser will strip any content that is not whitelisted"? Well, the answer is yes and we added a new AdminCP Dev Center tool to create Parser Whitelist Rules inside Invision Community Apps (again more on all this later). With the coupling of the Parser Whitelist and Editor Extensions, admins can rest assured that their editors will just "work" when you install Extensions. If you want to prematurely prepare to create Invision Community 5 Editor Extensions, have a look at Tiptap's Dev API Documentation, specifically the methods Node.create(), Mark.create() and Extension.create(). We've added wrappers for those three methods, in addition to an interface to add and position buttons in the toolbar. Please let me know if you have any questions! Wyświetl pełną treść wpisu

Invision Community 5 has a brand new editing experience powered by a lightweight, fast React text editor built for mobile and modern browsers. The venerable CKEditor v4 at the core of our current editor is starting to show its age, so we wanted a clean slate with Invision Community v5 with an editor that was optimized for mobile use, easily extensible and had a feature set that would take us into the next era of Invision Community and beyond. The obvious choice was to consider the latest version of CKEditor, but it didn't fit our needs as it wasn't easily extensible, external plug-ins would no longer be possible, and its large footprint would affect page speed scores and be painful to use with a mobile connection. After a long search, we settled on Tiptap as the base for our editor. Written in React, loaded in chunks when needed for optimal performance and with many APIs and extensibility options, it was the perfect fit. Aside from the technical improvements, the editor offers new tools and a great base for writing our own plugins. I'll walk you through the main features throughout this blog. If you want a more technical deep dive, then please see my development blog. The ToolbarThe toolbar has been redesigned to put the most commonly used styles first, with the least used styles and functions into an ellipses menu. The new paragraph menu contains the header styles, as well as the code block. The plus menu adds lists, boxes and quotes. The benefit of this new compact menu is that it displays just the same on mobile. Currently, there are different editor styles for desktops, tablets and mobiles with some style buttons removed to save space. With Invision Community 5, this is no longer the case. Even the smallest display gets all the functionality. mobile-toolbar.mp4 Emojis & IconsEmojis have become a great way to embellish writing and express emotion. The new emoji picker has been modernized with larger emojis and tooltips to showcase the emoji shortcodes. The Icons tab, new for Invision Community 5, allows you to add Font Awesome Icons directly to your content. Lastly, both the emoji selector and the shortcode suggestion dropdown support arrow-key navigation, so you don't have to move your hands from the keyboard to the mouse. Content BoxesThe feature I'm personally most excited about is boxes. The concept started as an abstraction of spoilers because sometimes you just want "a box" - a section that stands out from the rest of the content, something we do manually in our documentation and guides on this site. Each box has a tile and the following options: Expandable - You can mark a box as "expandable" which is functionally the same as a spoiler. One improvement is that expandable boxes use native HTML details and summary elements instead of plain Javascript animated divs. Colors - You can optionally keep it grey on grey like spoilers, but I think that's so boring! The colors automatically adjust to the theme colors, so it will look great in dark and light mode. Float (left/right/none) - You can make the box align to the left or right of other content just like you can for images Width - When the box is floated, you can set the width to big, medium or small. Boxes.mp4 Link ExpansionInvision Community has long expanded some links, such as YouTube, offering more context or even a mini-player where appropriate. With Invision Community 5, we've added support for embedding dynamic link previews using site metadata. This is a preview of a topic on our forum. For those unaware, the Open Graph (OG) Protocol is essentially a way webpages can specify a title, image, and description to be dynamically embedded on another platform. This is the underlying technology when you see the link preview in Meta, X, Slack, or iMessage. Code Blocks and Inline CodeThe new editor adds inline, syntax-highlighted code blocks and inline code. Both formats can be applied via the toolbar, or optionally, you can wrap text in a single backtick (`) to convert it to an inline code block or triple backticks (```) to convert it to a code block. The code blocks also support numerous languages for syntax highlighting, including a new custom highlighter for the Invision HTML Template Syntax (Invision Community theme creators and application developers, you're welcome!) Semantic Headings and Relative SizesInvision Community 5 adds a block selector with headings 1 through 6 in the new editor. It's possibly the most common request I hear so that people can use consistent styling rather than just big bold text in a paragraph tag. Semantic headings are also ideal for SEO and accessibility. In addition to the block selector, you can create headings with the corresponding markdown shortcut. Consecutive pound signs (#) at the start of a line followed by a space (the number of pounds corresponds to the "level" of the heading). For example ### creates a Heading 3 ( ) creates the heading for you.Using clear header tags means screen readers and search engines can better understand your content as using absolute font sizes, such as 16px, can make it unclear what type of element is actually being used. Is it a heading or just a paragraph with large bold text? Furthermore, you may want different sizes depending on the content and device type. Mobile devices may benefit from a large base font size. So we added percent-based font sizes which change the font size based on whatever the default would be for that block. text-menus.mp4 Further UX ImprovementsThe new editor in Invision Community 5 has several tangible improvements, including a mobile-first design. In the current editor, some functionality was hidden behind modals and double clicks, which are either not obvious on mobile devices or not possible at all. The new editor no longer relies on modals and instead uses buttons and dropdown menus that work perfectly with mobile and other touch-based devices. New Line ArrowsFor block content, such as boxes, images and quotes, we've added the ability to create a new line before or after the block with the click of a button. This was an issue of frustration for mobile and touch devices where it was not always clear where the cursor was and a finger is a much less accurate aiming device! Sticky ToolbarAnyone who has authored a long piece of content knows the pain of scrolling up and down to get the toolbar in view. To make writing longer content less stressful, we've made the toolbar sticky so that it will always be fixed at the top of the editor after scrolling down. sticky-toolbar.mp4 Markdown Style ShortcutsOne common request is to support markdown in the editor. While we opted not to include full markdown support, the new editor recognizes many markdown-style formatting shortcuts. markdown.mp4 ColorsA common challenge with rich text editors on sites with multiple themes is colors often need to consistently look right across all themes. This is even more important with Invision Community 5, as it has a native dark mode feature. For this reason, we opted to offer a reduced set of color options that all adapt dynamically to the theme. I mentioned this about box colors above, but this is also true of the font color. The difference in shade is slight, but it's very noticeable without it. Toggling between light and dark mode will never produce unreadable text. colors.mp4We can't wait for you to try the new editor; it has already been very popular with our small testing group. Which feature are you most looking forward to trying? View full blog entry Wyświetl pełną treść wpisu

Invision Community 5 has a brand new editing experience powered by a lightweight, fast React text editor built for mobile and modern browsers. The venerable CKEditor v4 at the core of our current editor is starting to show its age, so we wanted a clean slate with Invision Community v5 with an editor that was optimized for mobile use, easily extensible and had a feature set that would take us into the next era of Invision Community and beyond. The obvious choice was to consider the latest version of CKEditor, but it didn't fit our needs as it wasn't easily extensible, external plug-ins would no longer be possible, and its large footprint would affect page speed scores and be painful to use with a mobile connection. After a long search, we settled on Tiptap as the base for our editor. Written in React, loaded in chunks when needed for optimal performance and with many APIs and extensibility options, it was the perfect fit. Aside from the technical improvements, the editor offers new tools and a great base for writing our own plugins. I'll walk you through the main features throughout this blog. If you want a more technical deep dive, then please see my development blog. The Toolbar The toolbar has been redesigned to put the most commonly used styles first, with the least used styles and functions into an ellipses menu. The new paragraph menu contains the header styles, as well as the code block. The plus menu adds lists, boxes and quotes. The benefit of this new compact menu is that it displays just the same on mobile. Currently, there are different editor styles for desktops, tablets and mobiles with some style buttons removed to save space. With Invision Community 5, this is no longer the case. Even the smallest display gets all the functionality. mobile-toolbar.mp4 Emojis & Icons Emojis have become a great way to embellish writing and express emotion. The new emoji picker has been modernized with larger emojis and tooltips to showcase the emoji shortcodes. The Icons tab, new for Invision Community 5, allows you to add Font Awesome Icons directly to your content. Lastly, both the emoji selector and the shortcode suggestion dropdown support arrow-key navigation, so you don't have to move your hands from the keyboard to the mouse. Content Boxes The feature I'm personally most excited about is boxes. The concept started as an abstraction of spoilers because sometimes you just want "a box" - a section that stands out from the rest of the content, something we do manually in our documentation and guides on this site. Each box has a tile and the following options: Expandable - You can mark a box as "expandable" which is functionally the same as a spoiler. One improvement is that expandable boxes use native HTML details and summary elements instead of plain Javascript animated divs. Colors - You can optionally keep it grey on grey like spoilers, but I think that's so boring! The colors automatically adjust to the theme colors, so it will look great in dark and light mode. Float (left/right/none) - You can make the box align to the left or right of other content just like you can for images Width - When the box is floated, you can set the width to big, medium or small. Boxes.mp4 Link Expansion Invision Community has long expanded some links, such as YouTube, offering more context or even a mini-player where appropriate. With Invision Community 5, we've added support for embedding dynamic link previews using site metadata. This is a preview of a topic on our forum. For those unaware, the Open Graph (OG) Protocol is essentially a way webpages can specify a title, image, and description to be dynamically embedded on another platform. This is the underlying technology when you see the link preview in Meta, X, Slack, or iMessage. Code Blocks and Inline Code The new editor adds inline, syntax-highlighted code blocks and inline code. Both formats can be applied via the toolbar, or optionally, you can wrap text in a single backtick (`) to convert it to an inline code block or triple backticks (```) to convert it to a code block. The code blocks also support numerous languages for syntax highlighting, including a new custom highlighter for the Invision HTML Template Syntax (Invision Community theme creators and application developers, you're welcome!) Semantic Headings and Relative Sizes Invision Community 5 adds a block selector with headings 1 through 6 in the new editor. It's possibly the most common request I hear so that people can use consistent styling rather than just big bold text in a paragraph tag. Semantic headings are also ideal for SEO and accessibility. In addition to the block selector, you can create headings with the corresponding markdown shortcut. Consecutive pound signs (#) at the start of a line followed by a space (the number of pounds corresponds to the "level" of the heading. For example ### creates a Heading 3 (<h3/>) creates the heading for you. Using clear header tags means screen readers and search engines can better understand your content as using absolute font sizes, such as 16px, can make it unclear what type of element is actually being used. Is it a heading or just a paragraph with large bold text? Furthermore, you may want different sizes depending on the content and device type. Mobile devices may benefit from a large base font size. So we added percent-based font sizes which change the font size based on whatever the default would be for that block. text-menus.mp4 Further UX Improvements The new editor in Invision Community 5 has several tangible improvements, including a mobile-first design. In the current editor, some functionality was hidden behind modals and double clicks, which are either not obvious on mobile devices or not possible at all. The new editor no longer relies on modals and instead uses buttons and dropdown menus that work perfectly with mobile and other touch-based devices. New Line Arrows For block content, such as boxes, images and quotes, we've added the ability to create a new line before or after the block with the click of a button. This was an issue of frustration for mobile and touch devices where it was not always clear where the cursor was and a finger is a much less accurate aiming device! Sticky Toolbar Anyone who has authored a long piece of content knows the pain of scrolling up and down to get the toolbar in view. To make writing longer content less stressful, we've made the toolbar sticky so that it will always be fixed at the top of the editor after scrolling down. sticky-toolbar.mp4 Markdown Style Shortcuts One common request is to support markdown in the editor. While we opted not to include full markdown support, the new editor recognizes many markdown-style formatting shortcuts. markdown.mp4 Colors A common challenge with rich text editors on sites with multiple themes is colors often need to consistently look right across all themes. This is even more important with Invision Community 5, as it has a native dark mode feature. For this reason, we opted to offer a reduced set of color options that all adapt dynamically to the theme. I mentioned this about box colors above, but this is also true of the font color. The difference in shade is slight, but it's very noticeable without it. Toggling between light and dark mode will never produce unreadable text. colors.mp4 We can't wait for you to try the new editor; it has already been very popular with our small testing group. Which feature are you most looking forward to trying? View full blog entry Wyświetl pełną treść wpisu

This is our May maintenance release. This release also improves bruteforce detection for logins and updates to local Stripe payment methods (such as iDEAL, Sofort, Giropay, Bancontact). Wyświetl pełną treść wpisu

Kluczowe zmiany To jest nasza majowa aktualizacja serwisowa. Poprawki Ulepszono wykrywanie ataków brute force podczas logowania. Zaktualizowano lokalne metody płatności Stripe (iDEAL, Sofort, Giropay, Bancontact). Dodatkowe informacje Core Dodano ostrzeżenie o maksymalnej zalecanej wersji PHP. Usunięto przycisk dołączania do klubu ze strony zasad klubów. Poprawiono widok klubu i strony członków, dodając tytuł strony. Poprawiono obsługę niestandardowej strony aktualizacji, aby zapobiec błędom. Ulepszono ochronę logowania brute force dla wielu kont. Naprawiono błąd na profilu, gdzie sekcja rozwiązań zwracała błąd, jeśli nie było klasy używającej rozwiązań. Naprawiono wyrównanie nazw klubów na zdjęciach okładkowych. Naprawiono problem z osadzaniem obrazów. Naprawiono zadanie s3Delete. Naprawiono powiadomienia o niezatwierdzonych treściach, aby używały statusu przeczytania. Naprawiono wyświetlanie bloku Device Usage. Naprawiono wyświetlanie zapisanych wykresów punktów. Naprawiono tworzenie ogłoszeń z datą końcową w przeszłości. Naprawiono zmianę skali czasu na zapisanych wykresach. Naprawiono błąd w tle przy przenoszeniu/usuwaniu treści. Naprawiono nazwę typu treści w rozpoznawanych treściach. Naprawiono wyświetlanie wykresów aktywności moderatora. Naprawiono błąd w codziennych subskrypcjach strumienia. Blogi Naprawiono aktualizację SEO nazwy bloga po zmianie nazwy bloga. Naprawiono paginację w widoku siatki bloga. Commerce Naprawiono błąd przy ukrywaniu pakietu subskrypcji w ACP. Naprawiono duplikowanie rekordów dla umów PayPal. Naprawiono podwójne przetwarzanie niektórych płatności Stripe. Naprawiono możliwość darmowej aktualizacji planów subskrypcji. Zaktualizowano Stripe non-card payments do nowej wersji API. Events Naprawiono błąd z rzutowaniem offsetu na liczbę całkowitą na stronie przeglądu wydarzeń. Fora Poprawiono wydajność przeglądania dużych zarchiwizowanych tematów. Naprawiono niepoprawne liczenie postów na forum. Naprawiono ścieżki plików po przeniesieniu lokalizacji przechowywania. Pages Poprawiono walidację kodu PHP przy zapisywaniu niestandardowych bloków. Naprawiono wyświetlanie kategorii klubów w liście. Naprawiono problem z przestrzenią w nazwach szablonów stron. Naprawiono tworzenie nowych rekordów przez REST przy włączonej historii wersji. Naprawiono usuwanie wszystkich kategorii bazy danych po jej usunięciu. Naprawiono wyświetlanie wpisów menu kategorii klubów bez uprawnień. Naprawiono otwieranie strony kategorii klubów przez gości. Platforma Cloud Naprawiono wyświetlanie powiadomień o ukrytych/usuniętych tematach. Zmiany dla deweloperów i projektantów Usunięto optymalizację MySQL 5.7 dla ładowania treści z wieloma komentarzami. Wyświetl pełną treść wpisu

Forum moderation management used to be straightforward. It was commonplace to assign a moderator to a single forum. They would be responsible for enforcing the rules, removing spam and generally modelling the behaviour you wanted to see within your community. As community management has matured and moderators are tasked with roles based on knowledge, help and support, there is a need for more nuance in managing topics within your community. For example, you may have specialists or teams of specialists who help answer questions about development, sales, or support. Topics that require this help may be posted anywhere within your community. Indeed, this feature was inspired by a need in our own support community to ensure customers get the right help from the right team member. We have questions on feature sets, purchasing, and support requests, each requiring a different team member. It is not enough to hope that the right person sees the topics; they must be assigned to ensure excellent service. What are the benefits of this feature? The ability to assign a topic to a single moderator or a team of moderators ensures that each topic gets the best outcome regardless of where it was posted. Having topics assigned helps moderators deal with issues quickly, as there's clarity over which moderators should handle the topic. It also helps keep your community team accountable by having the ability to monitor their workload and get statistics on the time it takes for your team to reply. These statistics also help the community lead assess quality control. How do you use this feature? There are two ways to assign a topic to a moderator or team of moderators. You can assign a topic when replying to it or do it from the topic's action menu. Once assigned, the assignee can review their assigned topics via the Moderator Control Panel and see which are assigned to them via the list of topics. Each moderator will receive a notification informing them they have a new assignment. Those with permission to assign topics to others will see all the assigned topics and who they are assigned to when reviewing the list of topics. The Admin CP contains a list of all assigned topics and also allows you to create and manage teams of moderators, such as "Sales Team" or "Developers." Finally, once the topic has been managed successfully, the moderators can remove themselves from the assignment completing the task. Assigning a specific topic to a single person or team in a busy online forum is a strategy that can enhance the effectiveness of the forum's management. It promotes efficiency, expertise, consistency, and accountability, which are vital for maintaining a vibrant and respectful online community. We hope you are looking forward to this feature and look forward to any comments you may have. View full blog entry Wyświetl pełną treść wpisu

Finally, one of the most requested features for clubs in Invision Community is coming with our March 2024 release: Pages databases in Clubs. You may be surprised to see a new feature being introduced for Invision Community 4 during our flow of news for Invision Community 5, but as we're committed to Invision Community 4, we wanted to continue to bring optimizations and improvements to the platform. What is the benefit of this new feature? Clubs enable communities to host multiple micro-communities with many benefits. Clubs allow more specialized and focused discussions on specific topics. This can lead to higher-quality content and a deeper exploration of niche subjects that may get overlooked when posted on a busy forum. Clubs also offer the ability to tailor the community experience based on the needs of that community. That customization is what this feature focuses on. Pages is a powerful application that allows truly custom layouts for content areas. Simply by adjusting templates, you can create a news feed layout (it is what we use for this news blog area!) or something even more customized to your needs. The March 2024 release allows you to create Pages database categories directly inside clubs, including custom fields and templates. How does it work? Setting up your Pages database to allow clubs to use categories is simple. Simply allow categories to be created within clubs when creating or editing a database. Once that is done, club owners can add a Pages database category to their club in the same way they can add topics, galleries, etc. Once the Pages database category has been added, you can then add content as you would any other club area with the added features of Pages, including custom templates and custom fields. This example club uses a custom Pages database listing template to show the articles in a custom format along with custom field data. Likewise, viewing an article in this example club showcases the use of custom templates to present the content differently from the standard topic templates Invision Community uses elsewhere. Allowing Pages database categories inside clubs brings the opportunity for more complex custom areas making use of multiple custom fields along with truly custom layouts using templates. This is a great way to bring additional areas, such as news articles, into your club areas to compliment discussions. We hope you enjoy this feature, and if you have any comments, please leave them below! View full blog entry Wyświetl pełną treść wpisu

Finally, one of the most requested features for clubs in Invision Community is coming with our March 2024 release: Pages databases in Clubs. You may be surprised to see a new feature being introduced for Invision Community 4 during our flow of news for Invision Community 5, but as we're committed to Invision Community 4, we wanted to continue to bring optimizations and improvements to the platform. What is the benefit of this new feature? Clubs enable communities to host multiple micro-communities with many benefits. Clubs allow more specialized and focused discussions on specific topics. This can lead to higher-quality content and a deeper exploration of niche subjects that may get overlooked when posted on a busy forum. Clubs also offer the ability to tailor the community experience based on the needs of that community. That customization is what this feature focuses on. Pages is a powerful application that allows truly custom layouts for content areas. Simply by adjusting templates, you can create a news feed layout (it is what we use for this news blog area!) or something even more customized to your needs. The March 2024 release allows you to create Pages database categories directly inside clubs, including custom fields and templates. How does it work? Setting up your Pages database to allow clubs to use categories is simple. Simply allow categories to be created within clubs when creating or editing a database. Once that is done, club owners can add a Pages database category to their club in the same way they can add topics, galleries, etc. Once the Pages database category has been added, you can then add content as you would any other club area with the added features of Pages, including custom templates and custom fields. This example club uses a custom Pages database listing template to show the articles in a custom format along with custom field data. Likewise, viewing an article in this example club showcases the use of custom templates to present the content differently from the standard topic templates Invision Community uses elsewhere. Allowing Pages database categories inside clubs brings the opportunity for more complex custom areas making use of multiple custom fields along with truly custom layouts using templates. This is a great way to bring additional areas, such as news articles, into your club areas to compliment discussions. We hope you enjoy this feature, and if you have any comments, please leave them below! Wyświetl pełną treść wpisu