keliix06

I updated our dev environment to 6.0.1 and it completely breaks the Kayako API. v5 running on the same server runs flawlessly, but under v6 there's all kinds of strict standards errors, plus the API doesn't work.

I just had the same issue. I noticed when I did a message preview there were some odd characters inserted throughout my text, mostly in spaces before or after links or punctuation. If I deleted and retyped a few characters I could get those to go away in the preview window. Once there were no more odd characters in the preview the message would send. The original message was typed completely in WHMCS in TinyMCE.

Not to be a jackass, but if you're looking for support why not contact support?

I would think more than some number of questions about deprecated messages (if you're a host who needs to contact your billing software vendor about a deprecated error message then I feel really badly for your customers), would be losing support for PHP 5.2, which I assume a lot of people still have their install running on. Though I do agree 5.3.3 would have been a great place to switch over and make WHMCS require 5.3.

Yes, it still works.

When hiding a config option, it still showing on all order forms for that product. When going back to the group in configuration options it still shows as hidden, and in the DB the hidden field is set to 1.

I can't say we've run into any Kayako bugs in a very long time, and while the integration with WHMCS isn't great it certainly does what it needs to do without any problems. With v4 having a full API, developing something that is way more complete should be doable.

PayPal allows for subscriptions to be created with free trial periods. WHMCS just doesn't show any payment option if there isn't an invoice due. The limitation here is on the WHMCS end, not PayPal.

Since it's within the {$ispaid} section, it will only ever show if an invoice has been paid, which won't be the case if Google is just trying to verify.

WHMCS won't show you this info automatically. We developed a small module that stores info on which site has which IP and which client owns it. Then it shows the clients their assigned IPs in WHMCS too.

http://forum.whmcs.com/showthread.php?t=23797&highlight=decrypt

Seriously, if a host doesn't know if they support 3 exceedingly basic features then run as fast as you can in the other direction. My guess is GoDaddy does support cURL SSL, GD and Ioncube, but if they don't know that's a really, really bad sign.

Simple SQL query, assuming you're moving all of the clients. Search for packages on server id x and change them to server id y.

I think I made the same mistake as CrimsonGT, but none of the buy links point to fiberelephant.com. I created an account there and submitted the ticket to sales.

Automated submission doesn't do any harm, as long as you're not doing it over and over, but submission of any type does zero good. Getting one link from an indexed page will get your page indexed faster than submitting ever could, and without backlinks being indexed doesn't do you any good anyway.

It's been resolved.

I got the free book and 24 karat module, then 24 hours later was charged $94. I have given you 2 days to resolve this before bringing it here, but everyone should beware before requesting these products.

That's how you'd have to do it, but I imagine it would need to be a much more complex query joining tables in based on client ids, package ids, etc.

So enom was really slow earlier this week, so bad that I had to remove our code provided by the enom addon to get our account summary just to get into the WHMCS homepage. I knew I should be able to get to all of the data with ajax so as to keep WHMCS fast. This is the code I used. I also load the PayPal balance using this, but that's mostly someone elses code so I won't include that here. In /admin/templates/v4/header.tpl Find {literal}<script> $(document).ready(function(){ and just below that add $("#financeajax").load("finance_ajax.php"); In /admin/templates/v4/homepage.tpl Find <div class="contentbox" style="font-size:18px;"><a href="transactions.php"><img src="images/icons/transactions.png" align="absmiddle" border="0"> <b>Income</b></a> Today: <span class="textgreen"><b>{$stats.income.today}</b></span> This Month: <span class="textred"><b>{$stats.income.thismonth}</b></span> This Year: <span class="textblack"><b>{$stats.income.thisyear}</b></span></div> and just below that add <br /> <div id="financeajax"></div> Create a new file at /admin/finance_ajax.php and use the following code <?php include('enomajax.php'); ?> <link href="../modules/admin/enom_extended/templates/eestyle.css" rel="stylesheet" type="text/css" /> <div class="errorbox">eNom Summary » <span style="color:#000000;"> Balance: <?php echo $enom->Balance; ?> - Available Balance: <?php echo $enom->AvailableBalance; ?> - Active Domains: <?php echo $enom->DomainCount; ?></span></div> Create a new file at /admin/enomajax.php and use the following code. Replace YOURUID and YOURPW accordingly. This would be better with cURL, which I'll probably work on today, but I threw this together in about 20 minutes, most of which was spent learning the enom API. This also uses simplexml, which I believe is PHP5 only, but it gets rid of about 50 lines of parsing code. <?php $write = file_get_contents('https://reseller.enom.com/interface.asp?command=GetBalance&uid=YOURUID&pw=YOURPW&responsetype=xml'); $fp = fopen('enom.xml','w'); fwrite($fp,$write); fclose($fp); $enom = simplexml_load_file('enom.xml'); ?> Now you should be able to go into your WHMCS homepage and after a couple of seconds you'll see the enom data load. Those are seconds that normally everything would have been waiting to load which is highly annoying. So in 10 lines of code life should now be better

Not necessarily. File hosting sites can use huge amounts of bandwidth and storage while using almost no CPU. Doesn't take a lot of processing power to start a file download.

Open a ticket, I'm sure they can tell you what you need to do to verify. It can obviously be done since they do it for the system. And HostOrca is right, it's MD5 with a salt

I believe all I needed to change was header.tpl to include the .js files and tutorials.tpl to setup the html.

Some servers require the use of "localhost" as the mail server instead of mail.yourdomain.com. Have you tried that?

You can look at the source of ours. I actually just got rid of the accordion effect that we had as well: http://account.buyhttp.com/tutorials.php

You cannot upgrade from 4.0.0 to 4.0.2 with the patch file. You would just use the full download of 4.0.2.