08.02.06

The Official Community Forums Module for DNN CMS

Important Upgrade Notes

The release notes will follow, below these important notes.

Upgrading Through 8.0 & 8.1 (must read)

First, if you're upgrading from a version earlier than 8.0, you NEED to view the important release note FYI wiki articles below.

• What to Know When Upgrading to Community Forums 8.0
• What to Know When Upgrading to Community Forums 8.1

New "Legacy Token" Replacement

Tokens are used in various templates to insert content from a forum, topic, reply, etc. into a page. However, in previous versions, HTML was injected from code for certain tokens, which made it impossible for a designer to tailor the HTML markup without customizing the code.

DNN Community Forums 08.02.00 introduces new token replacement features that inject only the data associated with the token, allowing the designer to create whatever HTML markup is desired.

The community-default and community-bootstrap themes and templates have been updated to include the markup that used to be generated in the module's code.

However, for installed sites that have other themes and templates, DNN Community Forums 08.02.00 will replace a legacy token--on-the-fly--with its modern replacement, including the previously-injected markup.

For example, [GROUPNAME] will now be replaced by [FORUMGROUP:FORUMGROUPLINK|<a href="{0}" class="dcf-forumgroup-link"&gt;[FORUMGROUP:GROUPNAME]&lt;/a&gt;]

IMPORTANT! The legacy token replacement feature will be supported through version 10.00.00, and will then be removed.

If you use your own themes and templates, please visit our wiki to read more and see which legacy tokens are replaced by which updated tokens.

Removed Duplicated Templates

In 08.00.00, template loading was enhanced to fallback/default from theme templates to module default templates, making it no longer necessary to duplicate all templates into a theme folder if not specifically customizing a template for a particular theme.

Several templates shipped with the community themes have been removed in 08.02.00 since they are the same as the defaults in /config/templates. If you have a custom theme and a template has not been customized from the version shipped with DNN Community Forums, the template can be removed from your custom theme if desired.

---

DNN Community Forums Release Notes

08.02.06

THANK YOU for all of the valuable contributions by @johnhenley, @Timo-Breumelhof, and @WillStrohl!

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

New Features & Enhancements

• UPDATE: Removed Search Text from Views on Mobile Browsers (Issue #1281)

Bug Fixes

• FIXED: Module Intitilization Overwrites Bootstrap Theme (Issue #1312)
• FIXED: New Users Unable to Create New Posts Due to Flood Control (Issue #1319)
• FIXED: Unable to Press Enter to Start Searching (Issue #1311)
• FIXED: Child Forums Not Aligned with Other Forums (Issue #1303)
• FIXED: Icons Not Aligned Properly in the Forum View (Issue #1322)

Tasks / Development Updates (and Technical Debt)

• Release Prep: 08.02.06 (Issue #1327)

08.02.05

The Official Community Forums Module for DNN CMS

Important Upgrade Notes

The release notes will follow, below these important notes.

Upgrading Through 8.0 & 8.1 (must read)

First, if you're upgrading from a version earlier than 8.0, you NEED to view the important release note FYI wiki articles below.

• What to Know When Upgrading to Community Forums 8.0
• What to Know When Upgrading to Community Forums 8.1

New "Legacy Token" Replacement

Tokens are used in various templates to insert content from a forum, topic, reply, etc. into a page. However, in previous versions, HTML was injected from code for certain tokens, which made it impossible for a designer to tailor the HTML markup without customizing the code.

DNN Community Forums 08.02.00 introduces new token replacement features that inject only the data associated with the token, allowing the designer to create whatever HTML markup is desired.

The community-default and community-bootstrap themes and templates have been updated to include the markup that used to be generated in the module's code.

However, for installed sites that have other themes and templates, DNN Community Forums 08.02.00 will replace a legacy token--on-the-fly--with its modern replacement, including the previously-injected markup.

For example, [GROUPNAME] will now be replaced by [FORUMGROUP:FORUMGROUPLINK|<a href="{0}" class="dcf-forumgroup-link"&gt;[FORUMGROUP:GROUPNAME]&lt;/a&gt;]

IMPORTANT! The legacy token replacement feature will be supported through version 10.00.00, and will then be removed.

If you use your own themes and templates, please visit our wiki to read more and see which legacy tokens are replaced by which updated tokens.

Removed Duplicated Templates

In 08.00.00, template loading was enhanced to fallback/default from theme templates to module default templates, making it no longer necessary to duplicate all templates into a theme folder if not specifically customizing a template for a particular theme.

Several templates shipped with the community themes have been removed in 08.02.00 since they are the same as the defaults in /config/templates. If you have a custom theme and a template has not been customized from the version shipped with DNN Community Forums, the template can be removed from your custom theme if desired.

---

DNN Community Forums Release Notes

08.02.05

THANK YOU for all of the valuable contributions by @johnhenley, @Timo-Breumelhof, and @WillStrohl!

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

New Features & Enhancements

• Improved User Experience When Placing the Module on a Page (Issue #1305)
• Improved User Experience When Placing the Module on Blue Backgrounds (Issue #1304)

Bug Fixes

• FIXED: Topics Not Showing to Anonymous Visitors (Issue #1301)

Tasks / Development Updates (and Technical Debt)

• Release Prep: 08.02.05 (Issue #1313)

08.02.04

The Official Community Forums Module for DNN CMS

Important Upgrade Notes

The release notes will follow, below these important notes.

Upgrading Through 8.0 & 8.1 (must read)

First, if you're upgrading from a version earlier than 8.0, you NEED to view the important release note FYI wiki articles below.

• What to Know When Upgrading to Commmunity Forums 8.0
• What to Know When Upgrading to Commmunity Forums 8.1

New "Legacy Token" Replacement

Tokens are used in various templates to insert content from a forum, topic, reply, etc. into a page. However, in previous versions, HTML was injected from code for certain tokens, which made it impossible for a designer to tailor the HTML markup without customizing the code.

DNN Community Forums 08.02.00 introduces new token replacement features that inject only the data associated with the token, allowing the designer to create whatever HTML markup is desired.

The community-default and community-bootstrap themes and templates have been updated to include the markup that used to be generated in the module's code.

However, for installed sites that have other themes and templates, DNN Community Forums 08.02.00 will replace a legacy token--on-the-fly--with its modern replacement, including the previously-injected markup.

For example, [GROUPNAME] will now be replaced by [FORUMGROUP:FORUMGROUPLINK|<a href="{0}" class="dcf-forumgroup-link"&gt;[FORUMGROUP:GROUPNAME]&lt;/a&gt;]

IMPORTANT! The legacy token replacement feature will be supported through version 10.00.00, and will then be removed.

If you use your own themes and templates, please visit our wiki to read more and see which legacy tokens are replaced by which updated tokens.

Removed Duplicated Templates

In 08.00.00, template loading was enhanced to fallback/default from theme templates to module default templates, making it no longer necessary to duplicate all templates into a theme folder if not specifically customizing a template for a particular theme.

Several templates shipped with the community themes have been removed in 08.02.00 since they are the same as the defaults in /config/templates. If you have a custom theme and a template has not been customized from the version shipped with DNN Community Forums, the template can be removed from your custom theme if desired.

---

DNN Community Forums Release Notes

08.02.04

THANK YOU for all of the valuable contributions by @johnhenley and @WillStrohl!

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

New Features & Enhancements

• None at this time.

Bug Fixes

• FIXED: Quick Replies Sending Notifications Before Going Through Moderation (Issue #1289)
• FIXED: Unable to Delete a Topic After Creating It (Issue #1277)
• FIXED: MODEDITEDATE Token Incorrectly Being Updated on Every Refresh (Issue #1282)
• FIXED: "Forums not available" Exception in Topics View (Issue #1273)
• FIXED: User Accounts Without a UserPortals Record Throws Exceptions (Issue #1283)
• FIXED: Moderation HTML Output Issues (Issue #1288)
• FIXED: No Longer Getting Current User Accounts from HttpContext (Issue #1290)

Tasks / Development Updates (and Technical Debt)

• TASK: Replaced Obsolete DNN API Methods (Issue #1294)
• TASK: Updates to Unit Test Project to Better Integrate and Mock DNN objects (Issue #1275)
• TASK: 8.2.4 Release Prep (Issue #1296)

08.02.03

The Official Community Forums Module for DNN CMS

Important Upgrade Notes

The release notes will follow, below these important notes.

Upgrading Through 8.0 & 8.1 (must read)

First, if you're upgrading from a version earlier than 8.0, you NEED to view the important release note FYI wiki articles below.

• What to Know When Upgrading to Commmunity Forums 8.0
• What to Know When Upgrading to Commmunity Forums 8.1

New "Legacy Token" Replacement

Tokens are used in various templates to insert content from a forum, topic, reply, etc. into a page. However, in previous versions, HTML was injected from code for certain tokens, which made it impossible for a designer to tailor the HTML markup without customizing the code.

DNN Community Forums 08.02.00 introduces new token replacement features that inject only the data associated with the token, allowing the designer to create whatever HTML markup is desired.

The community-default and community-bootstrap themes and templates have been updated to include the markup that used to be generated in the module's code.

However, for installed sites that have other themes and templates, DNN Community Forums 08.02.00 will replace a legacy token--on-the-fly--with its modern replacement, including the previously-injected markup.

For example, [GROUPNAME] will now be replaced by [FORUMGROUP:FORUMGROUPLINK|<a href="{0}" class="dcf-forumgroup-link"&gt;[FORUMGROUP:GROUPNAME]&lt;/a&gt;]

IMPORTANT! The legacy token replacement feature will be supported through version 10.00.00, and will then be removed.

If you use your own themes and templates, please visit our wiki to read more and see which legacy tokens are replaced by which updated tokens.

Removed Duplicated Templates

In 08.00.00, template loading was enhanced to fallback/default from theme templates to module default templates, making it no longer necessary to duplicate all templates into a theme folder if not specifically customizing a template for a particular theme.

Several templates shipped with the community themes have been removed in 08.02.00 since they are the same as the defaults in /config/templates. If you have a custom theme and a template has not been customized from the version shipped with DNN Community Forums, the template can be removed from your custom theme if desired.

---

DNN Community Forums Release Notes

08.02.03

THANK YOU for all of the valuable contributions by @johnhenley and @WillStrohl!

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

New Features & Enhancements

• None at this time.

Bug Fixes

• FIXED: Filtered Topics View Showing Incorrect "Started By" User (Issue #1254)
• FIXED: Exception Occurs When Sending Email Notifications Due to HttpContext (Issue #1258)
• FIXED: Reversal of Approval for Posts After Moderation (Issue #1240)
• FIXED: Unable to Add a Forum Group After Deleting Sample Groups (Issue #1264)
• FIXED: Exception Logged When Displaying TopicsView (Issue #1253)
• FIXED: HTML Output Mangled Due to Token Replacement (Issue #1252)

Tasks / Development Updates (and Technical Debt)

• TASK: 8.2.3 Release Prep (Issue #1266)

08.02.02

The Official Community Forums Module for DNN CMS

Important Upgrade Notes

The release notes will follow, below these important notes.

Upgrading Through 8.0 & 8.1 (must read)

First, if you're upgrading from a version earlier than 8.0, you NEED to view the important release note FYI wiki articles below.

• What to Know When Upgrading to Commmunity Forums 8.0
• What to Know When Upgrading to Commmunity Forums 8.1

New "Legacy Token" Replacement

Tokens are used in various templates to insert content from a forum, topic, reply, etc. into a page. However, in previous versions, HTML was injected from code for certain tokens, which made it impossible for a designer to tailor the HTML markup without customizing the code.

DNN Community Forums 08.02.00 introduces new token replacement features that inject only the data associated with the token, allowing the designer to create whatever HTML markup is desired.

The community-default and community-bootstrap themes and templates have been updated to include the markup that used to be generated in the module's code.

However, for installed sites that have other themes and templates, DNN Community Forums 08.02.00 will replace a legacy token--on-the-fly--with its modern replacement, including the previously-injected markup.

For example, [GROUPNAME] will now be replaced by [FORUMGROUP:FORUMGROUPLINK|<a href="{0}" class="dcf-forumgroup-link"&gt;[FORUMGROUP:GROUPNAME]&lt;/a&gt;]

IMPORTANT! The legacy token replacement feature will be supported through version 10.00.00, and will then be removed.

If you use your own themes and templates, please visit our wiki to read more and see which legacy tokens are replaced by which updated tokens.

Removed Duplicated Templates

In 08.00.00, template loading was enhanced to fallback/default from theme templates to module default templates, making it no longer necessary to duplicate all templates into a theme folder if not specifically customizing a template for a particular theme.

Several templates shipped with the community themes have been removed in 08.02.00 since they are the same as the defaults in /config/templates. If you have a custom theme and a template has not been customized from the version shipped with DNN Community Forums, the template can be removed from your custom theme if desired.

---

DNN Community Forums Release Notes

08.02.02

THANK YOU for all of the valuable contributions by @johnhenley and @WillStrohl!

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

New Features & Enhancements

• None at this time.

Bug Fixes

• FIXED: Error on Add Answer (Issue #1241)
• FIXED: Error When Deleting a Topic (Issue #1242)
• FIXED: Error on Edit Post (Issue #1243)

Tasks / Development Updates (and Technical Debt)

• TASK: 8.2.2 Release Prep (Issue #1248)

08.02.01

The Official Community Forums Module for DNN CMS

Important Upgrade Notes

The release notes will follow, below these important notes.

Upgrading Through 8.0 & 8.1 (must read)

First, if you're upgrading from a version earlier than 8.0, you NEED to view the important release note FYI wiki articles below.

• What to Know When Upgrading to Commmunity Forums 8.0
• What to Know When Upgrading to Commmunity Forums 8.1

New "Legacy Token" Replacement

Tokens are used in various templates to insert content from a forum, topic, reply, etc. into a page. However, in previous versions, HTML was injected from code for certain tokens, which made it impossible for a designer to tailor the HTML markup without customizing the code.

DNN Community Forums 08.02.00 introduces new token replacement features that inject only the data associated with the token, allowing the designer to create whatever HTML markup is desired.

The community-default and community-bootstrap themes and templates have been updated to include the markup that used to be generated in the module's code.

However, for installed sites that have other themes and templates, DNN Community Forums 08.02.00 will replace a legacy token--on-the-fly--with its modern replacement, including the previously-injected markup.

For example, [GROUPNAME] will now be replaced by [FORUMGROUP:FORUMGROUPLINK|<a href="{0}" class="dcf-forumgroup-link"&gt;[FORUMGROUP:GROUPNAME]&lt;/a&gt;]

IMPORTANT! The legacy token replacement feature will be supported through version 10.00.00, and will then be removed.

If you use your own themes and templates, please visit our wiki to read more and see which legacy tokens are replaced by which updated tokens.

Removed Duplicated Templates

In 08.00.00, template loading was enhanced to fallback/default from theme templates to module default templates, making it no longer necessary to duplicate all templates into a theme folder if not specifically customizing a template for a particular theme.

Several templates shipped with the community themes have been removed in 08.02.00 since they are the same as the defaults in /config/templates. If you have a custom theme and a template has not been customized from the version shipped with DNN Community Forums, the template can be removed from your custom theme if desired.

---

DNN Community Forums Release Notes

08.02.01

THANK YOU for all of the valuable contributions by @johnhenley!

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

New Features & Enhancements

• None at this time.

Bug Fixes

• FIXED: Multiple Issues with Email Notifications (Issue #1236)

Tasks / Development Updates (and Technical Debt)

• None at this time.

08.02.00

The Official Community Forums Module for DNN CMS

Important Upgrade Notes

The release notes will follow, below these important notes.

Upgrading Through 8.0 & 8.1 (must read)

First, if you're upgrading from a version earlier than 8.0, you NEED to view the important release note FYI wiki articles below.

• What to Know When Upgrading to Commmunity Forums 8.0
• What to Know When Upgrading to Commmunity Forums 8.1

New "Legacy Token" Replacement

Tokens are used in various templates to insert content from a forum, topic, reply, etc. into a page. However, in previous versions, HTML was injected from code for certain tokens, which made it impossible for a designer to tailor the HTML markup without customizing the code.

DNN Community Forums 08.02.00 introduces new token replacement features that inject only the data associated with the token, allowing the designer to create whatever HTML markup is desired.

The community-default and community-bootstrap themes and templates have been updated to include the markup that used to be generated in the module's code.

However, for installed sites that have other themes and templates, DNN Community Forums 08.02.00 will replace a legacy token--on-the-fly--with its modern replacement, including the previously-injected markup.

For example, [GROUPNAME] will now be replaced by [FORUMGROUP:FORUMGROUPLINK|<a href="{0}" class="dcf-forumgroup-link"&gt;[FORUMGROUP:GROUPNAME]&lt;/a&gt;]

IMPORTANT! The legacy token replacement feature will be supported through version 10.00.00, and will then be removed.

If you use your own themes and templates, please visit our wiki to read more and see which legacy tokens are replaced by which updated tokens.

Removed Duplicated Templates

In 08.00.00, template loading was enhanced to fallback/default from theme templates to module default templates, making it no longer necessary to duplicate all templates into a theme folder if not specifically customizing a template for a particular theme.

Several templates shipped with the community themes have been removed in 08.02.00 since they are the same as the defaults in /config/templates. If you have a custom theme and a template has not been customized from the version shipped with DNN Community Forums, the template can be removed from your custom theme if desired.

---

DNN Community Forums Release Notes

08.02.00

THANK YOU for all of the valuable contributions by @johnhenley, @Timo-Breumelhof, and @WillStrohl!

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

If you wish to see all of the development work (including updates related to internal testing), you can view the milestone for this release in GitHub.

New Features & Enhancements

Control Panel Security Configuration

• UX: (Re)Organized the Security in the Control Panel (Issue #931
• UPDATE: Allow Default Forum Settings to Be Created & Easily Used by Forum Groups (Issue #650)
• UPDATE: Made Forum Security Configuration Inheritance More Logical (Issue #62)
• UPDATE: Added Inheritance Labels When Forums are Inheriting Security and/or Settings (Issue #1161)
• UX: Re-Labeled Security Permission Options After Consolidation for Better UX (Issue #930)
• UX: Added Helpful Explanatory Text to Security Grid Titles (Issue #862)
• UX: Combined (Duplicated) "ModLock" and "Lock" Security Permission Options (Issue #926)
• UX: Combined (Duplicated) "ModPin" and "Pin" Security Permission Options (Issue #927)
• UX: Combined (Duplicated) "ModEdit" and "Edit" Security Permission Options (Issue #929)
• UX: Combined (Duplicated) "ModDelete" and "Delete" Security Permission Options (Issue #928)
• UX: Improved How the Security Grid is Displayed in the Control Panel (Issue #1115)
• UPDATE: Improved CSS for Control Panel Security Tooltip Position (Issue #1050)

Notifications, Likes, and Pins

• UPDATE: Get Notified When Someone Likes Your Post (Issue #632)
• UPDATE: Allow Authorized Visitors to See Who Likes a Post (Issue #801)
• UPDATE: Send Notification to Original Poster When Topic is Moved (Issue #1008)
• UPDATE: Enable/Disable Option for Email Notification to Posting User (Issue #263)

Templates & Tokens

• UPDATE: Email Notifications Modernized to Use Token Replacement (Issue #1128)
• UPDATE: New Template & Tokens for Search Results (Removes Hard-Coded HTML) (Issue #1101)
• UPDATE: New Template & Tokens for Filtered Topic Results (Removes Hard-Coded HTML) (Issue #1102)
• UPDATE: New Template & Tokens for the Forum Toolbar (Removes Hard-Coded HTML) (Issue #1113)
• UPDATE: New Token [FORUM:LOGINLINK] Replaces [ADDREPLY] When Unauthenticated (Issue #1107)
• UPDATE: Added the [FORUMPARENTNAME] Token for Child Forums (Issue #469)
• UPDATE: New Messages & Admin Log Reporting When Using Legacy Tokens in Templates (Issue #1062)
• UPDATE: Refactored Nested Template Insertion & Honor the [DCF:TEMPLATE-xxxx] Tokens (Issue #1124)
• UPDATE: Use Token Replacement Service for Moderation Notifications (Issue #1112)
• UPDATE: Static Text in Templates Can Now Be Localized (Issue #470)
• UPDATE: Updated community-* Templates to Move Markup from Code to a Template (Issue #1117)
• UPDATE: Use Template Caching Module Setting for Forums Toolbar Template (Issue #1095)
• UPDATE: Changed Replaced Tokens to Use Classes Instead of Inline Styles (Issue #467)
• UPDATE: Improved the HTML Output of the [AF:CONTROL:STATUSICON] Token (Issue #743)
• UPDATE: Added Core Token Replace Support to Some Templates (Issue #521)
• UPDATE: Removed Unnecessary HTML from Token Replacement in Email Templates (Issue #1127)
• UPDATE: Replaced Like Button Hard-Coded HTML with Tokens (Issue #1142)
• UPDATE: Moved Email Subject From the Template to Forum Settings (Issue #702)

User Experience & More...

• UX: Improved the Scaling of Large Images on All Viewports (Issue #982)
• UX: Many New Mobile User Experience Updates (Issue #932)
• UX: Improved How Moderated Forums Are Displayed (Issue #999)
• UX: Improved How IPv6 Addresses Are Displayed (Issue #1118)
• UX: Improved Messaging with No Moderator Content Pending (Issue #958)
• UX: Moderator Button Styling Improved (Issue #969)
• UX: Made Distance Consistent in the TopicsView Bootstrap Template (Issue #1192)
• UX: My Subscriptions & My Settings Cleared Upon Logout (Issue #981)
• UX: Styling for New Like Features (Issue #1189)
• UPDATE: Improved Avatar Image Quality for Forum Users (Issue #888)
• UPDATE: Improved UX on Topics When Not Logged In w/ Login Link (Issue #1001)
• UPDATE: Modernized Statuses for Forums, Topics, Replies (Issue #468)
• UPDATE: Forums Responses Marked as an Answer to be More Obvious (Issue #1144)
• UPDATE: Moderator Views Now Make it Easier to Navigate to Reported Posts (Issue #1041)
• UPDATE: Optimized How & What Gets Posted to the Journal (Issue #748)
• UPDATE: User Online Status Now More Accurate (Issue #1083)
• UPDATE: Search Results HTML Output has Newly Added div Tags (Issue #480)
• UPDATE: Don't Emit the Signature HTML Output When There Isn't a Signature (Issue #486)
• UPDATE: Adds Exception Logging to Web API Authentication (Issue #1051)

Bug Fixes

• FIXED: Images in a Forum Post can Appear to be Oversized & Break the Design (Issue #1105)
• FIXED: Editing the Topic Subject Should Update DNN Journal Item (Issue #821)
• FIXED: Tokens Such as [RESX:Views] are not Supported in UPPERCASE (Issue #475)
• FIXED: False Error When Updating User Profile (Issue #1002)
• FIXED: Posts Going Through Moderation Not Updating a User's Post Count (Issue #983)
• FIXED: Moderator Buttons not styled correctly (Issue #995)
• FIXED: Resolves an Issue When Properly Tracking Forum Reads & Views (Issue #1032)
• FIXED: "What's New" Module Showing Topics from Forums Not Selected in Module Settings (Issue #992)
• FIXED: Using the "Quick Jump" Forum Control Throws an Error (Issue #1034)
• FIXED: Splitting a Forum Thread Can Result in an Exception (Issue #1036)
• FIXED: Next/Previous Links Not Updated After Deleting Topics (Issue #1043)
• FIXED: Exception When Switching Between Tabs with Different Forums Instances (Issue #1075)
• FIXED: Updates to Resolve Known Process Queue Errors (Issue #1090)
• FIXED: Unable to Move an Existing Topic to a Hidden Forum (Issue #1089)
• FIXED: Topic View is Showing an Incorrect Topic Template on a Forum Thread Page with Only Replies (Issue #1139)
• FIXED: Fatal Exception In Getting Started Wizard in Some Cases Due to Serialization (Issue #857)
• FIXED: Forum Collapse Broken Due to [GROUP] Token Location in the Template (Issue #1153)
• FIXED: URL for a Specific Group of Forums Shows Other Groups (Issue #1152)
• FIXED: Subscriptions to Deleted Forums Are Orphaned (Issue #1156)
• FIXED: Update Redirect() Method Calls for Consistent and Correct Usage (Issue #970)
• FIXED: [SIGNATURE] Token Not Replaced in Topic Review Section When Creating a Reply (Issue #1177)
• FIXED: Forum Posts in Topic View Showing Wrong Signature (Issue #1194)
• FIXED: Changed Pin & Lock to Use ID Instead of Class on Reload (Issue #1209)
• FIXED: Updated TopicController to Use the Correct ContentID (Issue #1210)
• FIXED: Multiple UserProfile Records Created for ...

08.02.00 RC 1

The Official Community Forums Module for DNN CMS

---

IMPORTANT!!! This is a Release Candidate (RC)

NOT FOR PRODUCTION!

Please do not use this installation/upgrade package for any production websites of any kind. This release is not supported and is only provided for test purposes, to allow others to test their websites first.

---

Important Upgrade Notes

The release notes will follow, below these important notes.

Upgrading Through 8.0 & 8.1 (must read)

First, if you're upgrading from a version earlier than 8.0, you NEED to view the important release note FYI wiki articles below.

• What to Know When Upgrading to Commmunity Forums 8.0
• What to Know When Upgrading to Commmunity Forums 8.1

New "Legacy Token" Replacement

Tokens are used in various templates to insert content from a forum, topic, reply, etc. into a page. However, in previous versions, HTML was injected from code for certain tokens, which made it impossible for a designer to tailor the HTML markup without customizing the code.

DNN Community Forums 08.02.00 introduces new token replacement features that inject only the data associated with the token, allowing the designer to create whatever HTML markup is desired.

The community-default and community-bootstrap themes and templates have been updated to include the markup that used to be generated in the module's code.

However, for installed sites that have other themes and templates, DNN Community Forums 08.02.00 will replace a legacy token--on-the-fly--with its modern replacement, including the previously-injected markup.

For example, [GROUPNAME] will now be replaced by [FORUMGROUP:FORUMGROUPLINK|<a href="{0}" class="dcf-forumgroup-link"&gt;[FORUMGROUP:GROUPNAME]&lt;/a&gt;]

IMPORTANT! The legacy token replacement feature will be supported through version 10.00.00, and will then be removed.

If you use your own themes and templates, please visit our wiki to read more and see which legacy tokens are replaced by which updated tokens.

Removed Duplicated Templates

In 08.00.00, template loading was enhanced to fallback/default from theme templates to module default templates, making it no longer necessary to duplicate all templates into a theme folder if not specifically customizing a template for a particular theme.

Several templates shipped with the community themes have been removed in 08.02.00 since they are the same as the defaults in /config/templates. If you have a custom theme and a template has not been customized from the version shipped with DNN Community Forums, the template can be removed from your custom theme if desired.

---

DNN Community Forums Release Notes

08.02.00 RC 1

THANK YOU for all of the valuable contributions by @johnhenley, @Timo-Breumelhof, and @WillStrohl!

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

If you wish to see all of the development work (including updates related to internal testing), you can view the milestone for this release in GitHub.

New Features & Enhancements

Control Panel Security Configuration

• UX: (Re)Organized the Security in the Control Panel (Issue #931
• UPDATE: Allow Default Forum Settings to Be Created & Easily Used by Forum Groups (Issue #650)
• UPDATE: Made Forum Security Configuration Inheritance More Logical (Issue #62)
• UPDATE: Added Inheritance Labels When Forums are Inheriting Security and/or Settings (Issue #1161)
• UX: Re-Labeled Security Permission Options After Consolidation for Better UX (Issue #930)
• UX: Added Helpful Explanatory Text to Security Grid Titles (Issue #862)
• UX: Combined (Duplicated) "ModLock" and "Lock" Security Permission Options (Issue #926)
• UX: Combined (Duplicated) "ModPin" and "Pin" Security Permission Options (Issue #927)
• UX: Combined (Duplicated) "ModEdit" and "Edit" Security Permission Options (Issue #929)
• UX: Combined (Duplicated) "ModDelete" and "Delete" Security Permission Options (Issue #928)
• UX: Improved How the Security Grid is Displayed in the Control Panel (Issue #1115)
• UPDATE: Improved CSS for Control Panel Security Tooltip Position (Issue #1050)

Notifications, Likes, and Pins

• UPDATE: Get Notified When Someone Likes Your Post (Issue #632)
• UPDATE: Allow Authorized Visitors to See Who Likes a Post (Issue #801)
• UPDATE: Send Notification to Original Poster When Topic is Moved (Issue #1008)
• UPDATE: Enable/Disable Option for Email Notification to Posting User (Issue #263)

Templates & Tokens

• UPDATE: Email Notifications Modernized to Use Token Replacement (Issue #1128)
• UPDATE: New Template & Tokens for Search Results (Removes Hard-Coded HTML) (Issue #1101)
• UPDATE: New Template & Tokens for Filtered Topic Results (Removes Hard-Coded HTML) (Issue #1102)
• UPDATE: New Template & Tokens for the Forum Toolbar (Removes Hard-Coded HTML) (Issue #1113)
• UPDATE: New Token [FORUM:LOGINLINK] Replaces [ADDREPLY] When Unauthenticated (Issue #1107)
• UPDATE: Added the [FORUMPARENTNAME] Token for Child Forums (Issue #469)
• UPDATE: New Messages & Admin Log Reporting When Using Legacy Tokens in Templates (Issue #1062)
• UPDATE: Refactored Nested Template Insertion & Honor the [DCF:TEMPLATE-xxxx] Tokens (Issue #1124)
• UPDATE: Use Token Replacement Service for Moderation Notifications (Issue #1112)
• UPDATE: Static Text in Templates Can Now Be Localized (Issue #470)
• UPDATE: Updated community-* Templates to Move Markup from Code to a Template (Issue #1117)
• UPDATE: Use Template Caching Module Setting for Forums Toolbar Template (Issue #1095)
• UPDATE: Changed Replaced Tokens to Use Classes Instead of Inline Styles (Issue #467)
• UPDATE: Improved the HTML Output of the [AF:CONTROL:STATUSICON] Token (Issue #743)
• UPDATE: Added Core Token Replace Support to Some Templates (Issue #521)
• UPDATE: Removed Unnecessary HTML from Token Replacement in Email Templates (Issue #1127)
• UPDATE: Replaced Like Button Hard-Coded HTML with Tokens (Issue #1142)
• UPDATE: Moved Email Subject From the Template to Forum Settings (Issue #702)

User Experience & More...

• UX: Improved the Scaling of Large Images on All Viewports (Issue #982)
• UX: Many New Mobile User Experience Updates (Issue #932)
• UX: Improved How Moderated Forums Are Displayed (Issue #999)
• UX: Improved How IPv6 Addresses Are Displayed (Issue #1118)
• UX: Improved Messaging with No Moderator Content Pending (Issue #958)
• UX: Moderator Button Styling Improved (Issue #969)
• UX: Made Distance Consistent in the TopicsView Bootstrap Template (Issue #1192)
• UX: My Subscriptions & My Settings Cleared Upon Logout (Issue #981)
• UX: Styling for New Like Features (Issue #1189)
• UPDATE: Improved Avatar Image Quality for Forum Users (Issue #888)
• UPDATE: Improved UX on Topics When Not Logged In w/ Login Link (Issue #1001)
• UPDATE: Modernized Statuses for Forums, Topics, Replies (Issue #468)
• UPDATE: Forums Responses Marked as an Answer to be More Obvious (Issue #1144)
• UPDATE: Moderator Views Now Make it Easier to Navigate to Reported Posts (Issue #1041)
• UPDATE: Optimized How & What Gets Posted to the Journal (Issue #748)
• UPDATE: User Online Status Now More Accurate (Issue #1083)
• UPDATE: Search Results HTML Output has Newly Added div Tags (Issue #480)
• UPDATE: Don't Emit the Signature HTML Output When There Isn't a Signature (Issue #486)
• UPDATE: Adds Exception Logging to Web API Authentication (Issue #1051)

Bug Fixes

• FIXED: Images in a Forum Post can Appear to be Oversized & Break the Design (Issue #1105)
• FIXED: Editing the Topic Subject Should Update DNN Journal Item (Issue #821)
• FIXED: Tokens Such as [RESX:Views] are not Supported in UPPERCASE (Issue #475)
• FIXED: False Error When Updating User Profile (Issue #1002)
• FIXED: Posts Going Through Moderation Not Updating a User's Post Count (Issue #983)
• FIXED: Moderator Buttons not styled correctly (Issue #995)
• FIXED: Resolves an Issue When Properly Tracking Forum Reads & Views (Issue #1032)
• FIXED: "What's New" Module Showing Topics from Forums Not Selected in Module Settings (Issue #992)
• FIXED: Using the "Quick Jump" Forum Control Throws an Error (Issue #1034)
• FIXED: Splitting a Forum Thread Can Result in an Exception (Issue #1036)
• FIXED: Next/Previous Links Not Updated After Deleting Topics (Issue #1043)
• FIXED: Exception When Switching Between Tabs with Different Forums Instances (Issue #1075)
• FIXED: Updates to Resolve Known Process Queue Errors (Issue #1090)
• FIXED: Unable to Move an Existing Topic to a Hidden Forum (Issue #1089)
• FIXED: Topic View is Showing an Incorrect Topic Template on a Forum Thread Page with Only Replies (Issue #1139)
• FIXED: Fatal Exception In Getting Started Wizard in Some Cases Due to Serialization (Issue #857)
• FIXED: Forum Collapse Broken Due to [GROUP] Token Location in the Template (Issue #1153)
• FIXED: URL for a Specific Group of Forums Shows Other Groups (Issue #1152)
• FIXED: Subscriptions to Deleted Forums Are Orphaned (Issue #1156)
• FIXED: Update Redirect() Method Calls for Consistent and Correct Usage (Issue #970)
• FIXED: [SIGNATURE] Token Not Replaced in Topic Review Section Wh...

08.01.02

The Official Community Forums Module for DNN CMS

IMPORTANT: Upgrade Notes

The release notes will follow, below these important notes.

New Bootstrap 4 & 5 Forum Theme

Please be sure to test this and report any issues you may find. It's a brand-new feature!

When you use the community-default or the community-bootstrap Theme, make sure to set the Avatar size to 250 x 250 pixels in the Module Settings.

Also, please note that this version of the community-bootstrap theme will not work with Bootstrap 3 and/or the DNN Xcillion theme.

New Languages Added!

Dutch already had a language pack, but now there are language packs for German, French, Spanish, and Italian. They were generated though, so we could use your help from the community to make sure the translations are indeed accurate.

We recommend that you use Peter Donker's translation software (below) to make things easier for you.

• Blog: A Central Hub for Language Packs, by Peter Donker
• Download: DNN Translator
• Related Pull Request: Add Azure Cognitive Services (Microsoft Translator v3) as a Translation Service

Upgrading? Reindex Your Search

There have been significant updates in the way the forums module integrates with the DNN search engine. This includes a handful of bug fixes. It's important to reindex your DNN search as soon as possible after the upgrade.

NEW CSS Loading Order (since 8.0)

CSS loading has been improved to deliver robust CSS both within the module, across all themes, and then theme-specific with a custom override.

New Community Forum's CSS Load order:

• ~/DesktopModules/ActiveForums/module.css (already existing)
• ~/DesktopModules/ActiveForums/themes/themes.css (new name and CSS content / used across all themes)
• ~/DesktopModules/ActiveForums/themes/_currenttheme_/theme{.min}.css (already existing / new name). Can now have a .min.css variant.
• ~/DesktopModules/ActiveForums/themes/_currenttheme_/custom/theme{.min}.css (new) has been updated. Can now have a .min.css variant.

Orphaned Web.Config Update (since 8.0)

If you have previously installed the Community Forums module --and its URL rewriter in order to use friendly URLs-- that process inserted the attribute runAllManagedModulesForAllRequests="true" into the <configuration><system.webServer><modules> tag in the main web.config.

Per Microsoft documentation, this attribute is obsolete if you are running IIS 7 (plus a patch), or IIS 8+.

Since you may have other modules that require it, we have chosen to NOT remove it automatically. If you have no other modules that require it, you many remove it manually.

Release Notes

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

If you wish to see all of the development work (including updates related to internal testing), you can view the milestone for this release in GitHub.

08.01.02

New Features & Enhancements

• UPDATE: Make sure Filtered Topics dropdown text is visible on mobile (Issue 959, thanks @Timo-Breumelhof!)

Bug Fixes

• BUG: After Update to 8.1.1 Visited / Read forums icons not reflecting actual status anymore. (#973, thanks @johnhenley!)
• BUG: Email notifications being sent for topics that have not cleared moderation (#971 , thanks @johnhenley!)
• BUG: Redirect after editing a post comment (#962 , thanks @johnhenley!)
• BUG: Clicking Save in forum control panel restores default security when forum is not inheriting security from group (#964, thanks @johnhenley!)

Tasks / Development Updates (and Technical Debt)

• None at this time.

08.01.01

The Official Community Forums Module for DNN CMS

IMPORTANT: Upgrade Notes

The release notes will follow, below these important notes.

New Bootstrap 4 & 5 Forum Theme

Please be sure to test this and report any issues you may find. It's a brand-new feature!

When you use the community-default or the community-bootstrap Theme, make sure to set the Avatar size to 250 x 250 pixels in the Module Settings.

Also, please note that this version of the community-bootstrap theme will not work with Bootstrap 3 and/or the DNN Xcillion theme.

New Languages Added!

Dutch already had a language pack, but now there are language packs for German, French, Spanish, and Italian. They were generated though, so we could use your help from the community to make sure the translations are indeed accurate.

We recommend that you use Peter Donker's translation software (below) to make things easier for you.

• Blog: A Central Hub for Language Packs, by Peter Donker
• Download: DNN Translator
• Related Pull Request: Add Azure Cognitive Services (Microsoft Translator v3) as a Translation Service

Upgrading? Reindex Your Search

There have been significant updates in the way the forums module integrates with the DNN search engine. This includes a handful of bug fixes. It's important to reindex your DNN search as soon as possible after the upgrade.

NEW CSS Loading Order (since 8.0)

CSS loading has been improved to deliver robust CSS both within the module, across all themes, and then theme-specific with a custom override.

New Community Forum's CSS Load order:

• ~/DesktopModules/ActiveForums/module.css (already existing)
• ~/DesktopModules/ActiveForums/themes/themes.css (new name and CSS content / used across all themes)
• ~/DesktopModules/ActiveForums/themes/_currenttheme_/theme{.min}.css (already existing / new name). Can now have a .min.css variant.
• ~/DesktopModules/ActiveForums/themes/_currenttheme_/custom/theme{.min}.css (new) has been updated. Can now have a .min.css variant.

Orphaned Web.Config Update (since 8.0)

If you have previously installed the Community Forums module --and its URL rewriter in order to use friendly URLs-- that process inserted the attribute runAllManagedModulesForAllRequests="true" into the <configuration><system.webServer><modules> tag in the main web.config.

Per Microsoft documentation, this attribute is obsolete if you are running IIS 7 (plus a patch), or IIS 8+.

Since you may have other modules that require it, we have chosen to NOT remove it automatically. If you have no other modules that require it, you many remove it manually.

Release Notes

What's to follow are all of the relevant updates that have occurred during the development cycle of this release.

If you wish to see all of the development work (including updates related to internal testing), you can view the milestone for this release in GitHub.

08.01.01

New Features & Enhancements

• UPDATE: No Longer Listing Informative Posts as "Unanswered" (Issue 946, thanks @johnhenley!)
• UPDATE: Added Headings to Filtered Topic Overviews (Issue 949, thanks @johnhenley!)
• UPDATE: Added 'Add Reply' Buttons on Top of TopicsView (Issue 941, thanks @johnhenley!)
• UPDATE: Added Alignment for 'Next' in the community-default Forum Theme (Issue 934, thanks @Timo-Breumelhof!)

Bug Fixes

• BUG: [DISPLAYNAME] Not Included in Email Notifications (Issue 923, thanks @johnhenley!)
• BUG: Resolved Alignment Issues in the Active Topics Filtered List (Issue 948, thanks @johnhenley!)
• BUG: Resolved Issue Attempting to Mark Topic as Answered (Issue 945, thanks @johnhenley!)
• BUG: Added Cache Keys to Resolve Topic Paging Issues (Issue 933, thanks @johnhenley!)
• BUG: Moderation Email Not Sent if Disapproving a New Topic (Issue 938, thanks @johnhenley!)

Tasks / Development Updates (and Technical Debt)

• None at this time.