Support

Documentation

Chapter 4. The plugins

[Note]Note

None of the plugins are availabe in Akeeba Ticket System Core.

Akeeba Ticket System is a modular system, allowing you to easily extend it by means of plugins. It comes with several plugins out of the box for features ranging from sending emails to integrating with Joomla! search and user profiles. In this chapter you will learn what each plugin does and how to configure it.

The plugins can be found in the Joomla! plugins manager (Extensions, Manage Plugins at the back-end of your site). The plugins are placed in different groups, depending on the kind of functionality they perform. This chapter is organised by plugin group.

The "ats" plugins

Akeeba Subscriptions 4 / 5 integration

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - Akeeba Subscriptions integration and Akeeba Ticket System - Akeeba Subscriptions 4 integration

This allows you to integrate the Akeeba Subscriptions component with Akeeba Ticket System. Each Akeeba Subscriptions subscription level can be assigned to a number of credits. When the subscription becomes active these credits are added to the user's Akeeba Ticket System credit count. When the subscription becomes inactive you can choose whether to keep the credits or expire them (meaning any unused credits will no longer be available to the user).

Please remember that you should use the correct plugin depending on your Akeeba Subscriptions version:

  1. Akeeba Ticket System - Akeeba Subscriptions integration is for Akeeba Subscriptions 5 and 6 and the current development branch on its GitHub repository.

  2. Akeeba Ticket System - Akeeba Subscriptions 4 integration is for the old Akeeba Subscriptions 4 release

There is no integration available for Akeeba Subscriptions 1.x, 2.x and 3.x since none of them run under the Joomla versions currently supported by Akeeba Ticket System.

[Warning]Warning

Choosing the wrong plugin will cause Akeeba Ticket System to crash. In most cases this will cause your site to crash too, especially if you are using the Reply by Email system plugin.

Joomla! User Groups integration

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - Joomla! user groups integration

This plugin displays to your support staff the user groups each user belongs to. This information is printed under the username displayed along each ticket post.

Alpha User Points integration

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - Alpha User Points integration

This allows you to integrate the third part Alpha User Points component with Akeeba Ticket System. When Akeeba Ticket System detects that the user has run out of ATS credits it will consume Alpha User Points and give the user Akeeba Ticket System credits in return. The conversion (how many AUP points are consumed and how many ATS credits are credited) are specified in the options.

The options you can specify are:

  • Give this many credits. The option defines how many ATS credits will be given to the user when AUP user points are consumed.

  • Consume this many points. This option defines how many AUP points will be consumed to award the number of ATS credits specified above.

Please note that if you install the Alpha User Points component after you've installed Akeeba Ticket System you MUST install ATS again, without uninstalling it first, for this integration to work correctly.

Custom fields

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - Custom fields

You must enable this plugin when using the custom fields feature of Akeeba Ticket System.

Gravatar integration

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - Gravatar integration.

This plugin allows ATS to display the user's avatar using the Gravatar service. We recommend leaving this plugin enabled at all times as it provides an excellent fallback if any other avatar methods do not return an avatar picture.

[Note]Note

In the original ATS release this was the only available avatar method.

EasySocial avatar integration

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - EasySocial avatar integration.

This plugin allows ATS to display the user's avatar using the EasySocial component. If you have EasySocial installed on your site and want to use the avatars provided by it for Akeeba Ticket System enable this plugin. DO NOT enable this plugin if you do not have EasySocial already installed on your site.

New post notification emails

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - New post notification emails.

This is a very important plugin. It is responsible for sending emails whenever a new ticket is created or a reply is sent to an existing ticket. Unless you have a very serious reason not to, we strongly recommend keeping this plugin published at all times.

Social "Like" buttons

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - Social buttons.

This plugin allows visitors of your site to "like" and share your public tickets on various social networks including Facebook, Google+, Twitter and Pinterest. This is a handy feature to allow your users to easily share the public tickets with obvious SEO value.

GeoLocation support

[Note]Note

This plugin is NOT availabe in Akeeba Ticket System Core.

Displayed in the Joomla! Plugin Manager as Akeeba Ticket System - GeoLocation support.

This plugin allows you to record the geographic coordinates (location) of your users when they are filing a ticket and display that on a map for the support staff.

[Warning]Warning

It may be illegal for you to collect this information, with or without explicit consent. Please consult with your lawyer.

The options are:

Use W3C Geolocation API

When enabled, ATS will use the browser's geolocation feature. This is the preferred method on smartphones and other devices which have a built in GPS chip or otherwise can determine the user's exact location. Please note that due to browser restrictions this will only work if your site is using HTTPS and it will ask your users for explicit permission to share their location.

Use GeoIP

When this is enabled, IP geolocation will be used as a fallback when the W3C Geolocation API is disabled above, not available on the user's browser or the user has declined sharing their location. This gets a rough location based on the IP address the user is accessing your site from.

Maximum accepted accurace (metres)

All geolocation methods report their accuracy, i.e. the radius from the returned point on the map where the user may actually be. If the radius is above this value the location will be discarded. Use something really big, such as 500000, to practically accept any result.

GeoIP source

How should I convert IPs to geographic location when the Use GeoIP option is enabled? You can either use a free only service or the Akeeba GeoIP Provider Plugin. The latter requires one of our other GeoIP-capable software (Akeeba Release System, Admin Tools Professional) to update the GeoIP database.

Display map to

Who should see the map with the user's location? It can be just the support staff (default), both the staff and the ticket owner or everyone (NOT recommended!).

Display map with

Which service should we use to render the map? Please note that Google Maps requires paying them to get a Google Maps API key you need to enter below.

Google Maps API Key

If you are using the Google Maps display method you need to enter the API key for Google Maps here. Please note that you need to pay Google for this key.

Internal field name

Under the hood, the geolocation is stored as an ATS "extra field" attached to the ticket. Enter the field name here. The default is geolocation and should be fine unless you already have a field by the same name.

Cookies Notification - Action required

This website uses cookies to provide user authentication and improve your user experience. Please indicate whether you consent to our site placing these cookies on your device. You can change your preference later, from the controls which will be made available to you at the bottom of every page of our site.