[DBTech] DragonByte eCommerce: Tickets [Paid] 2.4.0

[DragonByte Tech]

DragonByte Tech submitted a new resource:

[DBTech] DragonByte eCommerce: Tickets - Handle support tickets for your DragonByte eCommerce products.

This product requires DragonByte eCommerce to function!

DragonByte eCommerce: Tickets is the perfect companion to DragonByte eCommerce, allowing you to easily deal with any support query your users might have.

Fully integrated with XenForo 2.1 and DragonByte eCommerce, Tickets uses forums to house your support tickets, giving you the...

Read more about this resource...

 

[Alpha1]

Is this GDPR compliant or are you planning it to be? i.e. does this have secure storage of private information and automatic deletion of such?
For example passwords, payment details, personal info, etc.

 

[DragonByte Tech]

Is this GDPR compliant or are you planning it to be? i.e. does this have secure storage of private information and automatic deletion of such?
For example passwords, payment details, personal info, etc.

This system does not have any method for storing such information, just like there isn't @ our site just now. It's something I've been thinking about, but given the fact that it would take some doing to produce a truly secure information storage, it's not like I can just throw it together in five minutes.

For this reason, and because it uses XF's threads / forums, there's nothing about this system that pertains to GDPR that would not happen by using threads to handle support queries without the added eCommece integration this mod brings.

In order to create a properly secure information storage, I would need to create an encryption system that generates a random encryption key that is emailed to both the ticket starter and the assigned agent. Possibly a new user group permission to determine whether someone always receives all encryption keys, similar to how there's a permission to only list assigned tickets.

The key cannot be stored anywhere on the server, or the system is 100% worthless from a security perspective.

In short, this mod is exactly what you currently see @ our site, so if it doesn't exist @ our site then it also doesn't exist in this mod

 

[Alpha1]

This may be of use:

Projects using libsodium

download.libsodium.org

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

1.0.1

Update highlights

This update fixes a couple reported bugs with the "default assigned agent" feature.


Complete Change Log

Fix: Allow tickets to be submitted if a default assigned agent is not set
Fix: It is now possible to remove the default assigned agent

Read the rest of this update entry...

 

[kankan]

Hello
I would only need ticket function.
Any way to disable the Shopping addon and only use the tickets ?
Thanks

 

[DragonByte Tech]

Hello
I would only need ticket function.
Any way to disable the Shopping addon and only use the tickets ?
Thanks

Unfortunately not, this mod requires eCommerce as it's intended to be integrated to provide additional benefit such as autofilling certain fields based on the license selected, etc.

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

1.0.2

Update highlights

This update adds the ability to see the ticket status in the thread list, as well as fixing a few bugs reported by the community.

The registration defaults have also been changed, no longer requiring an entirely separate setting. The toggles can be found inside XF's own registrationDefaults setting.


Complete Change Log

Feature: Ticket status is now displayed in the thread list
Change: Merged registration...

Read the rest of this update entry...

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

1.1.0

Update highlights

This version massively reworks the way support ticket actions are executed. Previously, they would only execute when viewing the ticket, or when the ticket was replied to, or via a cron job. Actions are now executed whenever the ticket is updated, as well as via a cron job.

This, combined with the new ticket criteria for when a ticket's status is being updated, means it's possible to immediately close fully solved tickets and still have features like...

Read the rest of this update entry...

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

1.1.1

Update highlights

This version fixes a compatibility issue with PHP 7.4 / the upcoming XenForo 2.1.3.


Complete Change Log

Fix: Fixed a PHP 7.4 / XenForo 2.1.3 compatibility issue

Read the rest of this update entry...

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

2.0.0

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...

Read the rest of this update entry...

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

2.0.1

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...

Read the rest of this update entry...

 

[ChrisTERiS]

It came on the right time when my old ticketing mod expired Some questions:

1.- The client can starts "unlimited" threads (tickets) per product, or each license has only one thread/ticket and if the client want to ask for a different topic he must reply to the same thread/ticket?

2.- The assignment can be to product add-on and not to the main product? eg I've the AAAA product with Add-on "Ticketing Support". Can the assignment be only if the client buys the Ticketing Support add-on?

3.- What happens when the license of the assigned product expires? Client is still able to:

• View old tickets (that's normal)
• Reply to open tickets (that's fair)
• Open new tickets (I prefer not)

Thank you
Chris

 

[DragonByte Tech]

1.- The client can starts "unlimited" threads (tickets) per product, or each license has only one thread/ticket and if the client want to ask for a different topic he must reply to the same thread/ticket?

There are no limits to the amount of tickets (threads) someone can open. All this does is add additional information to threads.

2.- The assignment can be to product add-on and not to the main product? eg I've the AAAA product with Add-on "Ticketing Support". Can the assignment be only if the client buys the Ticketing Support add-on?

3.- What happens when the license of the assigned product expires?

Since this add-on is only a wrapper for the normal XenForo threads system, you can restrict who can open tickets by configuring your products / user groups / forum permissions in such a way that only people who purchase the "Ticketing Support" product on your site can access the ticket support forum.

You would do this by granting an additional user group to people who own the "Ticketing Support" product, either temporarily or permanently.

 

[ChrisTERiS]

Hello,

In the requirements it says DragonByte eCommerce v1.3.0+ and I've 1.3.0rc2. As I seen 1.3.0 released 5 days after my version.
So my question is if my eCommerce ver 1.3.0rc2 is compatible or not.

Thank you
Chris

 

[DragonByte Tech]

Hello,

In the requirements it says DragonByte eCommerce v1.3.0+ and I've 1.3.0rc2. As I seen 1.3.0 released 5 days after my version.
So my question is if my eCommerce ver 1.3.0rc2 is compatible or not.

Thank you
Chris

It would require the Gold version of eCommerce.

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

2.1.0

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...

Read the rest of this update entry...

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

2.2.0 Release Candidate 1

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...

Read the rest of this update entry...

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

2.2.0

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

Read the rest of this update entry...

 

[DragonByte Tech]

DragonByte Tech updated [DBTech] DragonByte eCommerce: Tickets with a new update entry:

2.2.1

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

Read the rest of this update entry...