×

Notice

The forum is in read only mode.
Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: Matukio compatible with Joomla 2.5?

Matukio compatible with Joomla 2.5? 7 years 2 months ago #35450

  • Jon
  • Jon's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 6
  • Thank you received: 0
Having a lot of issues with Matukio. Lots of Double Bookings which is frustrating my client.
I'm trying to convince them to stay with Matukio and not scrap Joomla all together for WordPress.
Would be great if I can solve this Double Bookings issue first. Using Authroize.net plugin. Users are only "active" if they pay - but still getting double entries in teh booking form, exact same booking details, exact same booking Time - but different ID. Payment plug in is only processing it ONCE.
So the robot employees - see this double booking, cancel it and auto refund the money which means the person goes to the seminar for free. Not good!

We are planning a migration to 3.6 and I'd like to update Matukio before hand. Is the latest version compatible with J2.5?

Looked through the documentation again and can't find a change log. The latest update to the article was in 2014.

Matukio compatible with Joomla 2.5? 7 years 2 months ago #35461

  • Yves Hoppe
  • Yves Hoppe's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 3519
  • Karma: 71
  • Thank you received: 556
Hi Jon,

Would be great if I can solve this Double Bookings issue first. Using Authroize.net plugin. Users are only "active" if they pay - but still getting double entries in teh booking form, exact same booking details, exact same booking Time - but different ID. Payment plug in is only processing it ONCE.


Never heard of anything like that, but that's definitely fixed in the current Matukio version.

latest release compatible with Joomla 2.5 was 5.1.3 iirc.

compojoom.com/changelogs

Best,
Yves

Matukio compatible with Joomla 2.5? 7 years 2 months ago #35465

  • Jon
  • Jon's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 6
  • Thank you received: 0
Hi Yves,
Thanks for your help and the link to the changelogs! I'll start looking thru the documentation there.

I'm not sure if its with the payment plug in, slow server response or what. I do see some transactions marked Duplicate by Authorize.net - these are still recorded as duplicate in Matukio but are not "active" which is ok since but sometimes they are both marked active and paid. We also use a donation plug in and Virtuemart with a different Authorize.net plug in and do not have duplicate transactions issues. When we used paypal we did not have this problem but we had a lot of people pay that were not marked paid within the system ( because of this we are no longer using paypal)

Looking at specific example from the database: everything is identical except the following:
Booking Date: 2017-01-26 16:50:29, 2017-01-26 16:50:10
Even the payment_plugin_data is identical

We do get a lot of bookings - so far this past 30 days we have had 652 confirmed paid transactions. ( not including duplicates )
We are running 5.1.3 with J2.5 it's an older server running php5.3

We are planning a massive update and server migration. When I re-up my subscription while incremental upgrades be available for Matukio?
We are so far off from 3.6 my game plan is to incrementally update joomla on a local server to keep the database intact as much as possible.

Sorry 1 more question. Are the Matukio Webinars listed on your Demo site for real???? I would totally recommend my clients to take one if so! They have a high employee turnover rate so this would be way to get managers up to speed.

Thanks again in advance for your help troubleshooting.

Matukio compatible with Joomla 2.5? 7 years 2 months ago #35498

  • Jon
  • Jon's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 6
  • Thank you received: 0
Any luck getting in touch with the TechJoomla guys?
My problems seem to lead back to their Payments API.
Their support forum appears to of been abandoned.

EDIT: Traced the problem back to the SSL. Some issues with the lack on info not being passed back from the payments plug-in that would help.
  • Page:
  • 1
Time to create page: 0.104 seconds