[DBTech] DragonByte eCommerce: Tickets 2.3.0

Update highlights

This version adds the option of changing the thread prefix when applying ticket actions, as well as fixing issues when attempting to use this product in a "standalone" mode (not associated with a DB eCommerce product).


Complete Change Log

Feature: New ticket action: Apply prefix
Fix: Fix server errors when not associating a ticket forum with an eCommerce product

Update highlights

This version resolves a potential server error when viewing certain pages (mostly administrative editing pages).


Complete Change Log

Fix: Fix potential server errors when viewing certain pages

Update highlights

This version adds a missing phrase related to the new Thread Type added with the XF 2.2 version of this add-on.


Complete Change Log

Fix: Add missing phrases for thread types

Update highlights

This version adds a missing phrase related to the new Thread Type added with the XF 2.2 version of this add-on.


Complete Change Log

Fix: Added missing "Support ticket" plural phrase

Update highlights

This version fixes an issue where a server error log entry could be generated if someone without appropriate permissions attempted to create a new thread in a support ticket forum.


Complete Change Log

Fix: A server error would be generated if someone without permission attempted to create a ticket

Update highlights

!!! THIS VERSION REQUIRES XENFORO 2.2.0 AND PHP 7.2.0 !!!

Coinciding with the release of XenForo 2.2.0, all XenForo 2.2 versions are now Gold This is also the last version that will contain the XF 2.2 / PHP 7.2 warning in the release notes.


Complete Change Log

No changes, version bump only

Update highlights

!!! THIS VERSION REQUIRES XENFORO 2.2.0 AND PHP 7.2.0 !!!

This version contains coding style updates and changes for XenForo 2.2.0 / PHP 7.2.0. You must also upgrade DragonByte eCommerce to v2.2.0 prior to installing this update.

The main change in this version is that support tickets are now its own forum type, a new feature in XenForo 2.2. This means improved template support and reduced compatibility issues with 3rd party add-ons, as well as advanced filtering options when viewing a product's support forum.

Furthermore, the "Open support tickets" widget now uses a custom thread list macro, showing a ticket's status rather than the number of views the ticket has received.

This version is flagged as a Release Candidate version as it has been tested on a live site.


Complete Change Log

Feature: The "Open support tickets" widget now uses the custom thread list macro
Feature: Add filtering tabs to the support ticket forum view
Feature: Rework support forums to use the "Forum Type" and "Thread Type" systems in XenForo 2.2
Change: Make various custom fields extendable
Change: Update internal functions to follow new XenForo 2.1 / 2.2 coding standards
Fix: Fix template modifications for XenForo 2.2

Update highlights

!!! THIS VERSION REQUIRES YOU TO BE RUNNING DRAGONBYTE ECOMMERCE v2.0.x !!!

This version includes the necessary changes to support DragonByte eCommerce v2.0.0 Beta 1 onwards. As this version includes important template changes, please make sure you have reverted all customised Tickets templates if you experience errors after upgrading.


Complete Change Log

Change: Updated templates to use the new features in eCommerce v2.0.0

Update highlights

The phrase used by the email subject for the "new secure data attached" email has been changed to make it easier to read for mobile users and email clients with limited horizontal space in the message list.

An issue with the default registration options has been addressed, and should now work as intended for new users going forward.


Complete Change Log

Change: Changed secure data attached email subject phrase
Fix: Unticking default registration options would not correctly set registration defaults

Update highlights

After a lengthy beta period here @ DBTech, v2 of DragonByte Tickets is now ready for release

This version contains one very important feature: Secure Data Storage.

This allows the ticket starter to enter data into fields defined by the admins (using the same feature as Thread Fields / User Fields and every other custom field). Once the user submits the form, a random encryption key is generated and emailed to the assigned agent as well as the user who started the ticket, the data is then encrypted with this key before being inserted into the database.

The data can only be decrypted by entering the secret key (even to the thread starter), and the data (even in its encrypted form) is only ever accessible to the assigned agent and the thread starter. The secret key is then stored in a cookie, which expires at the end of the browser session (when the user closes their browser).

The thread starter or the assigned agent can erase the encrypted data at any time, even if they lose the secret key. The person viewing the secure data can also press a button to hide the data again. No over-the-shoulder snooping

While this system has been tested here @ DBTech, and the most modern (at the time of writing) encryption standards are being applied, it is still advised that you do not use this system for long-term storage of data. Once the ticket has been resolved, it is strongly recommended to click the delete button to erase the data.


Complete Change Log

Feature: Secure Data Storage