springs

Hi CDJ, I'd welcome a better idea until WHMCS is able to change the original script to stop it from having any output (other than the email). Until then, this is the only solution that I know of to do.

Hi WIS hosting, Add the following to the end of the cron: > /dev/null 2>&1 That's what I had to do a while ago to get rid of the second email. And the format is now back to the way it was (and very much readable!) - Thanks!

Hi chhit, This was a bug that was fixed in the latest downloads for 5.2.2. Take out a ticket and they'll get you to the proper files.

Same - Chrome and Safari (iPad)

Your funny Phil. Have a great week!

Keeping an "open mind". Yup, that's it. Should be just as simple to implement so the daily report is easier to read.

Agreed. +1 to the old daily email format over the new.

I see the same issue with the cron job for crons/domainsync.com not working too just to confirm.

Can anyone else confirm that they do not have the "Lock / Unlock Domain" checkbox anymore under their domains tab for the customer in the admin area? I could have sworn it was there before this update, but maybe I'm just having a senior moment?

Same issue. Adding myself to this post in the hopes that someone has a fix.

Thanks Sparky. Had the same issue as described above and moved the version back to the one you've attached and it resolved the issue.

Hi Sheldon, Looking for something similar. Did you happen to overcome the limitation on when someting isn't an invoice generated by an order?

Hi John, We had it setup using the 12|1 Year originally. Unfortunately, this mean that when we had a customer buy one for multi-years it still only processed it for 1 year. The correct format that we were asked to change it to was: 1|1 Year 2|2 Year 3|3 Year and so on... Hope this helps John!

I know this is an old post, but I'm experiencing the same issue. Interestingly enough, I had it semi-working for a while and rebuilt the products and server and now it's producing the error listed above: exit signal Segmentation fault Did anyone figure out what was causing this? There have been no changes/updates to php between the times that it semi-worked and isn't working now. I thought it might be a wsdl caching problem, but that doesn't seem to be the issue. It's acting like a firewall issue, but the firewalls are completely open between the the servers. I'm not sure how or what I can do to debug the problem further. WSP 1.1.0 (DNP) and WHMCS 4.4.2

Resolved: There was a server listed that was no longer active that was hanging it up on Usage Stats Update System that it couldn't complete.