Redsign

I've posted a quick tutorial on my site that explains integrating Olark live chat with WHMCS. Beyond the basic code it populates the chat users name if they're logged in. If you're not using Olark, it's pretty nifty as it allows you to use existing IM clients to chat with visitors to your website, so you can use desktop and mobile clients. Guide here - http://bencollier.net/2014/03/integrate-olark-live-chat-with-whmcs/

With all the recent patches, I think a full upgrade is definitely the safest route - it ensures you have *everything* up to date and correct.But, as with any release, you'll still need to do a diff/compare on the templates/language files to merge your files. If you're on a Mac you can point FileMerge at your directory and the upgrade files to merge things together - http://smokingapples.com/software/reviews/filemerge-review/

I wish instead of patching these issues, the requests would also be blocked. If someone tries to do this, why not block the update instead of confusing admins and worrying them something bad has happened?

Using IFTTT you can get an email whenever WHMCS posts any blog post. Details here - http://forum.whmcs.com/showthread.php?80622-How-to-Receive-an-Instant-Email-whenever-WHMCS-adds-a-new-blog-post&p=344010#post344010

Using If This Then That (http://ifttt.com), a service that can trigger events based on circumstances we've made a recipe that'll send you an email whenever WHMCS adds a new blog post. Sign up to IFTTT here and get the recipe - https://ifttt.com/recipes/124486

GoCardless is capped at £2, but 1% otherwise. So a £1.00 transaction only costs 1p to process, a £200 transaction costs £2 and a £5,000 transaction still only costs £2.

Thanks for the quick reply. How come the other versions get a patch? What about users who rely on a reseller to get the update? I understand not wanting the full version publicly available, but delaying a security release isn't great... Does 5.2.6 roll in any other bug fixes fixed since 5.2.5? Thanks.

As per - http://blog.whmcs.com/?t=76310 There are patches for every other version, but no patch for 5.2.5 to 5.2.6. For customers who get their licenses from resellers, or for those with heavily modded installs, a full installation (requiring member ares login), doesn't seem to cut it for a security update.

Pop us in too please!

Agreed! </10char>

Good to have! I'd like an easy way of seeing what's scheduled for the next release from the homepage though

I've had this problem too ever since the forced password reset.

You'll need to update the path of the cron instead of setting anything in the config file.

To follow this up.. why does the file need to output to the browser in the first place?

Just to let you know this still works with v5.1.2.