mezzo

Okay found the location to change the text size of the text editor window. FYI, it's found at: /assets/js/tiny_mce/themes/advanced/skins/default/content.css First line

Thanks, that helps. And thanks for pointing out that v5 and v6 is different. Does anyone know where to find the config file, for WHMCS v6+ ? - - - Updated - - - This is what I'm relying on: http://www.tinymce.com/develop/bugtracker_view.php?id=4033

I'm looking for the config files for the TinyMCE editor; I need to change the text size in the backend editor. It's far too small while the text around it is larger. Can anyone direct me please?

Simply put how do I remove the navbar if the client is not logged in? I know it's an "if" function but don't know where to place that. Any help is appreciated.

Okay, so the "Open Ticket" assumes that it will only be used for clients logged in. I believe I understand it now, I want to remove the 'Open Ticket' and just create a fresh new 'Contact Us'. Same goes for the "Announcements" too I guess.. WHMCS just assumes that this is only going to be used for logged-in clients I guess. THANK YOU SO MUCH for your time today! I'm following you on Twitter now, and may employ your services down the road. You made me very happy today.

can't delete posts for some reason.. - - - Updated - - -

It only shows the link if the client is logged in. I want the link to still point to the custom URL even when the client is logged out.

... can't edit my post properly..

I can edit the navbar links but it only shows when the client is logged in. When logged, the links point at default. { $navItem = $primaryNavbar->getChild('Open Ticket'); if (is_null($navItem)) { return; } $navItem->setUri('https://www.test.com/contact/'); } Where, or how, do I add a hook to make it so that a link points where I want, when the client is logged out? I appreciate any help in advance.

Same here. I'm waiting two days for an answer. I see I can "fast track" inquiries for $30 which.. seems.. not great. Very frustrating!

I am, but only integrating the KB. I directed my "contact support" to point to a contact form since I couldn't capture environmental data from the Kayako submit form.

How did you solve that? I can't seem to fix the links if the client is not logged in. I have this hook which only works if the client is logged in: { $navItem = $primaryNavbar->getChild('Open Ticket'); if (is_null($navItem)) { return; } $navItem->setUri('https://www.test.com/contact/'); } What change do I make to ensure the same shows if someone is not logged in? Thanks in advance for any direction here..

Ahhh, thank you! I knew it was .navbar-main but didn't think to look at that file. That also helps me determine the original font. Thanks again, big help brian!

I've tried in vain to figure out where and how to change the teal navbar colour (color) in the Six theme of WHMCS. How do I do this?

PsiGate used to be a great company, ten years ago. Even five years ago. But now they're owned by Home Trust and their support is awful, takes at least a week to get a response and up to a month to get any issues resolved. They don't seem to understand how the Internet works so it's even more of a headache to try to deal with them.

Unfortunately PsiGate is no longer the company it used to be. Home Trust bought them out. I was with them for well over ten years and there were just too many mistakes and odd charges taken from my account that continue to be unexplained. They change their policies a lot and fail to inform their customers of these changes. The biggest problem with PsiGate is that their support is awful. They only have one guy handling support inquiries and it takes weeks to get one reply; which is a big deal if you do a lot of billing transactions.

After waiting 24 hours for support to respond to my inquiry, it was explained by Matt that if you're using the old Kayako 3.7 client area integration, it will not work with the new V5 client area template due to the way Kayako's HTML output is structured without doing some HTML/CSS customisation on the Kayako side of things. This upgrade was a very trying experience; trying to figure out what isn't documented and waiting on support for a day to respond, yeesh!.. Having support tell me 'it's your code, you figure it out' a couple times, left me frustrated and in general, I have a bad taste in my mouth about WHMCS in general due to the lack of speedy support. For a lot of people, this billing software is crucial so keep in mind that upgrading may mean you're down for a day while you're left to solve things on your own, and not making any money in the meantime. That said, it's unlikely that I'll upgrade again. This upgrade caused needless stress.

Actually there is a major problem.. the Kayako CSS is conflicting with a few of the styles sets in the whmcs css files, and vice versa. This is what WHMCS support told me earlier, advised me to go through the whmcs.css and fix it... which is unhelpful.. because I don't know what I'm supposed to fix specifically. It's like I'm saying my car is broken, and support tells me to fix the car. Uh.. yeah.. that's why I'm contacting support! What in WHMCS.css am I supposed to fix so that the knowledgebase & tickets view works like every other page?

Anyone know if there's any conflicts with Kayako eSupport? Thanks