JTicketing 2.1.2 Stable

Released on: Saturday, 05 May 2018 06:35

Release notes and changelog:

Backward Compatibility breaks if you are upgrading from 2.0.x or lower versions:

  1. HTML Overrides will break: A lot of the HTML in this release has been optimized and rewritten introducing structural changes and new elements on most of the pages. Any overrides you have done should be reviewed and redone for the extension to work correctly and to get the full benefit of new features. To see the new UI you need to remove your overrides.
  2. Shika Integration Broken: Since JTicketing 2.0 has changed a lot of core APIs the latest Shika release 1.2.3 will not work with JTicketing. Specifically, the ‘Event as Lesson’ integration will break. We will do a compatibility release in an upcoming version of Shika. Please do not upgrade JTicketing till this version is out if you use ‘Event as lesson’ feature. If you do not use this, there is no impact.
  3. Upgrade Event Managers App: You need to upgrade to the latest version 3.3.5 of the Event manager’s app released by AppCarvers today for it to work. Older app versions will not work with this version of JTicketing.

Upgrade Instructions (If you are upgrading from 2.0.x or lower versions)

  1. First of all, Take a backup of your entire site using an extension like Akeeba and try this version on your staging site first

  2. Download the latest package of JTicketing from the Techjoomla website.

  3. You can use the ‘Install from URL’ or ‘Upload and install’ interface to complete the installation

  4. You should have at least JTicketing 1.8.x installed on the site to correctly migrate to the 2.1. If you are on a lower version you need to upgrade to 1.8 release first.

  5. Once you have installed the latest version, browse to the JTicketing Dashboard and click on “Migrate Data”. This will migrate your database data as per the JTicketing 2.1 need.

  6. Since we have done some changes in the TJVendor to run with a multi-vendor scenario, If you are using the Enforce user to be a vendor first, this setting is deprecated. We have added a new config as Enable auto vendor registration?. Please do the changes as per the new config

  7. Read Installation and upgrade instructions


  • If you are upgrading JTIcketing from 2.0.x or below. First of all, take a backup of your entire site using an extension like Akeeba and try this version on your staging site first
  • This is a major release adding multiple features, UI changes, and bug fixes.
  • Read Installation and upgrade instruction

JTicketing v2.1.1 changelog:

- Bugs fixed(10):

Bug #118348 - All Orders - Total paid amount: it includes a pending status amount
Bug #124988 - Security issues.
Bug #125063 - Pin view image not showing.
Bug #126028 - [Retry payment-frontend]- Retry payment is not working.
Bug #126161 - Frontend Event >> Add to calendar >> Outlook ics file not generated.
Bug #126164 - JEvent - JTicketing book module is not getting displayed for r recursive event.
Bug #126250 - JTicketing not supporting non-bootstrap templates.
Bug #126572 - On Events pin view - venue location filter is not working.
Bug #126621 - [All events-filters -frontend]- Display event creator filter label even if admin disables event creator filter from menu creations.
Bug #126887 - Checkin API fixes.

Download release files:

No files were found.

Either you are not logged in Or
You do not have access to download this extension Or
You had a subscription but it is expired