Jump to content

Kayako Integration - How well is it?


Speedy059

Recommended Posts

I got the Kayako+Add-On's today so I'll probably be installing it sometime this week. Will probably have to do an all nighter so it doesn't affect to many of my clients.

 

If you are already using Kayako without the loginshare module and your clients are already registered to Kayako in a normal way, you do not have to do anything specific to migrate your clients. If the email address of their WHMCS is the same as their Kayako email address and they login using that address (and the WHMCS password off course) they will still see their old tickets. :)

Link to comment
Share on other sites

  • 2 weeks later...
Does anyone know the fix for the problem where every page change in Kayako (inside of WHMCS) produces the "This page contains both secure and nonsecure items. Do you want to display the nonsecure items" alert all the time?

 

Could be due to several things. Probably an image or script or css file that uses http instead of https in the source code. If you give the URL I can take a look for you at the source.

Link to comment
Share on other sites

Well, it's not on our site(s) actually - we use the built in WHMCS Ticket Area and find it perfect for our needs. The problem is at our Dedicated Server Provider. They recently switched to WHMCS from MB, but they still use Kayako.

 

Since their integration - every page load in the ticket area, every reload, every submit, every forward/back/refresh, everything you do produces the alert. They say it's a bug in the software, so I'm thinking that maybe I can help them find the fix for WHMCS.

ticketAug16_08.JPG

Link to comment
Share on other sites

Well, it's not on our site(s) actually - we use the built in WHMCS Ticket Area and find it perfect for our needs. The problem is at our Dedicated Server Provider. They recently switched to WHMCS from MB, but they still use Kayako.

 

Since their integration - every page load in the ticket area, every reload, every submit, every forward/back/refresh, everything you do produces the alert. They say it's a bug in the software, so I'm thinking that maybe I can help them find the fix for WHMCS.

 

its not a bug, its a someone not knowing what they are doing. Its simply poor html coding/design. Whoever calls it a bug has no clue what they are doing.

 

Explovisions suggestion/answer was correct.

Link to comment
Share on other sites

Well, it's not on our site(s) actually - we use the built in WHMCS Ticket Area and find it perfect for our needs. The problem is at our Dedicated Server Provider. They recently switched to WHMCS from MB, but they still use Kayako.

 

Since their integration - every page load in the ticket area, every reload, every submit, every forward/back/refresh, everything you do produces the alert. They say it's a bug in the software, so I'm thinking that maybe I can help them find the fix for WHMCS.

 

View the source of any page producing that error and search for the string:

 

src="http://

 

Or if that doesn't work:

 

http://

 

You'll probably find something being loaded on the page over a non-SSL connection. Like I said this could be a CSS file, an image, a Javascript file. However, if you see an A HREF tag using http:// it shouldn't be a problem since it's just a link and not something which is being loaded by the browser when the page is shown.

Link to comment
Share on other sites

Kayako integration for some time now (Kayako ver. 3.20 and WHMCS ver. 3.61) and it is working great; when our clients log into their Client Portal and click on Submit Ticket; their information is sent with the Ticket; they can see the responses from our Support Team and can reply. The client can also reply to the Ticket via email and it logs everything correctly.

Link to comment
Share on other sites

View the source of any page producing that error and search for the string: src="http://
Hi. Thanx, I had already discovered that this was in fact the problem. They have links to their graphical bullets that are http: links. I simply said 'no' to the 'display nonsecure items' request and saw what things were not loaded, and then did a 'View Source' to confirm the problem.

 

So yes, doesn't really look like a bug to me, it looks like a simple coding issue. FWIW, I've been very pleased with our dedicated hosting provider, and generally, they really know what they're doing big time. However, this one seems a pretty simple messup and it confuses me. :) Nothing critical, but it's any annoyance.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated