Releases: DNNCommunity/Dnn.CommunityForums
09.00.02
The Official Community Forums Module for DNN CMS
Important Upgrade Notes
The release notes will follow, below these important notes.
Minimum DNN Platform Version
VERY IMPORTANT: The MINIMUM DNN Platform version for this release is now DNN 9.11.
Upgrading to 9.x if you have customized templates (must read)
If you're upgrading to version 9.x AND you have customized templates, you NEED to view What to Know When Upgrading to Commmunity Forums 9.0
DNN Community Forums Release Notes
09.00.02
New Features & Enhancements
- None at this time
Bug Fixes
- None at this time
Tasks / Development Updates (and Technical Debt)
- 09.00.02 Release Prep (Issue #1510)
09.00.01
The Official Community Forums Module for DNN CMS
Important Upgrade Notes
The release notes will follow, below these important notes.
Minimum DNN Platform Version
VERY IMPORTANT: The MINIMUM DNN Platform version for this release is now DNN 9.11.
Upgrading to 9.x if you have customized templates (must read)
If you're upgrading to version 9.x AND you have customized templates, you NEED to view What to Know When Upgrading to Commmunity Forums 9.0
DNN Community Forums Release Notes
09.00.01
New Features & Enhancements
- None at this time
Bug Fixes
- FIXED: "Error: DNN Community Forums is currently unavailable." when viewing likes (Issue #1496)
- FIXED: Privileged content not showing just after logging in (Issue #1501)
- FIXED: Forums containing "announcement" topics are not displaying correctly (Issue #1494)
- FIXED: Moderated post approval not refreshing page when one item on page (Issue #1500)
- FIXED: Misplaced {objectQualifier} token in SQL script (Issue #1498)
Tasks / Development Updates (and Technical Debt)
- 09.00.01 Release Prep (Issue #1505)
09.00.00
The Official Community Forums Module for DNN CMS
Welcome to NEW Contributors in DNN Community Forums 09.00.00!
Before we get to the release notes, first things first -- a SHOUT OUT to our new contributors!!
Important Upgrade Notes
The release notes will follow, below these important notes.
Minimum DNN Platform Version
VERY IMPORTANT: The MINIMUM DNN Platform version for this release is now DNN 9.11.
Upgrading to 9.0 if you have customized templates (must read)
If you're upgrading to version 9.0 AND you have customized templates, you NEED to view the important release note FYI wiki article below.
What to Know When Upgrading to Commmunity Forums 9.0
DNN Community Forums Release Notes
09.00.00
THANK YOU for all of the valuable contributions by @johnhenley, @nvsai, @ernieblues, and @Timo-Breumelhof !
New Features & Enhancements
- NEW: Convention-based template names (Issue ##477)
- NEW: Moderators can now see attachments on unapproved topics (Issue #1386)
- NEW: "Debounce" topic and forum links to prevent multiple clicks (Issue #1027)
- NEW: Avatar token can contain size, e.g.,
[FORUMAUTHOR:AVATAR:50](Issue #421) - NEW: Move text from email notification template to resource files to facilitate localization (Issue #1454)
- NEW: More modern email notification template and UTF8 encoding (Issue #1457)
- NEW: Wider subject text box in quick reply (Issue #1470)
Bug Fixes
- FIXED: Unauthenticated users should not see direct-messaging icon (Issue #1403)
- FIXED: Brackets in content interfering with token replacement (Issue #1384)
- FIXED: 'Edit' link in topics view loading latest reply rather than the originating topic (Issue #1396)
- FIXED: Scheduler item not correctly removed in 8.1 (Issue #1397)
- FIXED: Submit button disabled after click to prevent duplicated posts (Issue #1031)
- FIXED: Improved token replacement causing page to not load if topic contains curly braces (Issue #1435)
- FIXED: Forum Groups not inheriting from default settings are losing their sort order (Issue #1433)
- FIXED: Keep Unicode quotes and accents out of friendly URLs (Issue #1456)
- FIXED: Incorrect image paths for spacers in control panel (Issue #1467)
- FIXED: Collapsible sections not opening on first click (Issue #1462)
- FIXED: Broken link in moderation notification emails (Issue #1468)
- FIXED: During 09.00.00 upgrade, fix any permissions (role Id's) separated by colon rather than semi-colon (Issue #1443)
- FIXED: After upgrade to 09.00.00, email notifications are missing the email body (Issue #1452)
- FIXED: After upgrade to 09.00.00, exception when retrieving notification subscriptions (Issue #1463)
Tasks / Development Updates (and Technical Debt)
- Remove template editor from control panel (Issue #1354)
- Refactor/modernize template caching and controller methods (Issue #465)
- Refactor/modernize permissions checking (Issue #950)
- Convert NTEXT database columns to NVARCHAR(MAX) (Issue #1184)
- Update minimum DNN Platform dependency to 9.11 (Issue #1224)
- Migrate csproj to SDK format (Issue #1274)
- Update third-party dependencies (Issue #1307)
- Update code files to use explicit using statements (Issue #1350)
- Duplicated tags in csproj file (Issue #1421)
- Remove unused images (Issue #1310)
- Remove deprecated methods (Issue #377)
- Update MSBuild.Community.Tasks to 1.5.0.235 (no longer require .NET Framework 3.5/2.0 for build) (Issue #1418)
- Remove legacy Analyzer tags from project file (Issue #1425)
- Update wiki documentation for v8-v9 upgrade path for anyone using customized templates (Issue #1352)
- 09.00.00 RC1 Release Prep (Issue #1423)
- 09.00.00 RC2 Release Prep (Issue #1436)
- 09.00.00 Release Prep (Issue #1460)
Contributors
Assets 4
08.02.08
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">[FORUMGROUP:GROUPNAME]</a>]
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.08
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: Fatal Exception on Attempts to Load the Reply View When There are Unexpected Post Count in the Pager (Issue #1333)
- FIXED: Topic Edit Preview Not Using Token Replacement (Issue #1369)
Tasks / Development Updates (and Technical Debt)
- Release Prep: 08.02.08 (Issue #1372)
Contributors
Assets 4
08.02.07
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">[FORUMGROUP:GROUPNAME]</a>]
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.07
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: Improved the Usability of the Advanced Search View (Issue #1340)
- UPDATE: Improved the Usability of the Pager for Mobile Visitors (Issue #1331)
- UPDATE: Search Pages Now Completely Using Localized Values (Issue #1347)
Bug Fixes
- FIXED: Posts & Reply Display Issues in the Search Results View (Issue #1336)
- FIXED: Exceptions When Banning a User Account (Issue #1334)
- FIXED: Intermittent Exception can Happen on Replies (Issue #1333)
- FIXED: Conflict Between Processing Keystrokes on the Forum Search and Quick Reply (Issue #1360)
- FIXED: Token Replacement Removing
<br />Tags from Content (Issue #1359) - FIXED: Extra Empty Rows Displayed in the Filter Results View (Issue #1335)
Tasks / Development Updates (and Technical Debt)
- TASK: Use the DNN ClientResourceManagement API Instead of Embedding Resources (Issue #1341)
- TASK: Update URL Construction to Better Handle the Viewer Module (Issue #1343)
- TASK: Removed the Legacy Dependency to
SimulateIsNumeric(Issue #1309) - TASK: Removed the Legacy Dependency to
SimulateDateDiff(Issue #1286) - Release Prep: 08.02.07 (Issue #1369)
Contributors
Assets 4
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">[FORUMGROUP:GROUPNAME]</a>]
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)
Contributors
Assets 4
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">[FORUMGROUP:GROUPNAME]</a>]
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)
Contributors
Assets 4
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">[FORUMGROUP:GROUPNAME]</a>]
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:
MODEDITEDATEToken Incorrectly Being Updated on Every Refresh (Issue #1282) - FIXED: "Forums not available" Exception in Topics View (Issue #1273)
- FIXED: User Accounts Without a
UserPortalsRecord 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)
Contributors
Assets 4
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">[FORUMGROUP:GROUPNAME]</a>]
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)
Contributors
Assets 4
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">[FORUMGROUP:GROUPNAME]</a>]
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)