WHMCS + Kayako Super Custom - Step 1

[arcdigital]

Hey, I have completed step one of my WHMCS + Kayako Integration. Can you guys tell me what you think/any bugs you find? (This isn't the normal integration, this is my own mix of things). It still needs a little help. I am NOT using the kayako/whmcs module that comes with kayako!

 

Features:

1) Fully Integrated Kayako + WHMCS LoginShare (Cookies + Email/Password from WHMCS DB)

2) Fully Integrated Kayako Skinning with WHMCS Portal Template

3) Integrated Search Box (Knowledgebase, Downloads, Troubleshooter)

4) Integrated Submit Ticket, View Tickets, Knowledgebase, Downloads, Announcements/News, and Troubleshooter

 

http://www.mygroovyautomation.com/billing/index.php

Login with

Email: anand@boostplatform.com

Password: test

 

Current Bugs:

1) Text/Styling changes a BIT when switching between whmcs and kayako

2) Name at top shows firstname in whmcs, but full name in kayako.

Edited October 25, 2008 by arcdigital
edited

[nielsenj]

Your login and register link when in Kayako 404's since it's not linked to the WHMCS directory and is looking for the files in Kayako's directory.

 

Skinning looks really good but i still prefer the uniformity of URL's with the actual integration and some mods i've released here.

 

If i may ask, why did you goto all the work of skinning Kayako to look the same as WHMCS? Why not make a unique template style for both?

 

And your loginbox in Kayako doesn't work because it's trying to access "dologin.php" which is also in the WHMCS directory.

 

It will probably be easier to maintain during upgrades if you just use the default integration and then the mods posted here. Just my opinion though

Edited October 25, 2008 by nielsenj
found another issue..

[arcdigital]

Maybe it's because i'm crazy, who knows? I was just testing, so I am going to skin both into my main site design next. Thanks for the bugs i'll fix those soon. It's because if I use the normal mods, I just don't like the way kayako is handled between whmcs/kayako. Who knows, it probably would have been easier to do it some other way, but I dunno. Just an FYI, I'm using the WHMCS LoginShare mod for kayako by Explovision. So far works perfectly! It grabs the cookie from WHMCS and logs them in auto, OR the user can login to kayako with whmcs info. Eventually what i'll do is I'll make a separate template group, that does the whmcs integration, and the default template group that doesn't do the whmcs integration. Because with this mod, users can login to kayako with whmcs info, or a separate login (non-clients, etc...)

Edited October 25, 2008 by arcdigital