Matt

Changed Status to Not a bug

It's not a deleted template hook. It's the same template being used in two areas as two areas (globalTemplate and globalTemplateHeaderLogic) uses the same template {template="logo" app="core" group="global" params="x"} The param contains 'mobile' if it's the mobile logo, which you can use in your HTML.

This is remarkable Jimi! Thank you for all that you do. It's brave souls like yours that really help get this product stable.

You can convert from 3 to 4, then from 4 to 5.

The production quality is as fantastic as the content!

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

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

Opportunity wasted. 😞

What do you need to change?

Percentage based or em based is better. Fixed pt or pixel sizes don't really scale up and down very well across screen sizes.

What do we want to see? Converting status updates into a specific forum with one topic per person and each status update a comment, and each reply to that status update a quoted reply?

As above, we had a preview site available when v5 was in alpha testing which we've chosen to keep open so people can play with it without having to install a test version themselves. The club here is where all beta discussion will take place, including the bugs which should be reported via the Bugs tab.

I spend a good few minutes trying to come up with a Halloween themed pun and the best I could do is "spooky". But never mind, Beta 3 is working its way through our deployment systems as I type. As always the full list of changes is available here: https://invisioncommunity.com/release-notes-v5/ Let me know how you get on!

Changed Beta Release to Yes Changed Current Release to No

Changed Beta Release to No

Changed Status to Fixed

Fixed in B3.

Changed Status to Fixed

Changed Status to Fixed

Fixed for B3. The issue only affects theme-level template hooks, not app-level.

Indeed, the key aim for v5 was to make it far easier to design a custom community and tailor it without having to create custom templates and pages of CSS. Quite often we'd say "you can do that but you need a custom block, a template and some CSS" which puts it beyond the reach of most community owners.

You could create two themes, with the preset views set differently. You could restrict one to admin only if you wanted to toggle between them without it being an option for everyone.