STOP relying on email!

STOP relying on email!

Let WHMCS Notify Extended ensure that clients and staff get proper notifications of events!

Hackers are EVERYWHERE

Hackers are EVERYWHERE

Take control of your WHMCS installation with WHMCS  User and IP Control

WHMCS can be complicated

WHMCS can be complicated

Spend a few hours learning from a Guru! Training available

Don't get caught with your servers down!

Don't get caught with your servers down!

Let WHMCS Guru host your billing and support website, securely and remotely!

Importing from another billing client?

Importing from another billing client?

We can absolutely put together a script to take care of that for you

Need WHMCS Customized?

Need WHMCS Customized?

We’ve been developing addons, hooks and modules for WHMCS since 2007. Drop us a line

WHMCS Troubleshooting Tips and Tricks – Part 2 – WSOD!

If you’ve been around the Windows world long enough, you know what the BSOD is. It’s nasty, it’s ugly, and even though Microsoft claims to have gotten rid of it, it still exists in a very different way. I bet you didn’t know, however, that there is such a thing as the WSOD (white screen of death) that is referred to by php developers and users alike. How can one figure out these errors? With WHMCS, this can be kind of complicated, but that’s what the point of this is, helping you get past these issues.

Let’s start with the most common debugging tool available. In your admin area, go to setup -> general -> other. Tick the ‘Display PHP errors’ option.  Can’t get to your admin area because of the WSOD? No problem, you can also do this via phpmyadmin.

UPDATE tblconfiguration SET value='on' WHERE setting= 'DisplayErrors'

Just make sure to turn it back OFF when you’re done

UPDATE tblconfiguration SET value='off' WHERE setting= 'DisplayErrors'

So, we’re now able to see what the error is (or we should be). Try viewing the page again. The error should be sitting there, plain as day.

One of the most common errors when upgrading is memory limits. When moving from v5 to v6, WHMCS increased the system requirements, upping the memory limit from 32M to 64M (with the highly recommended value at 128M). If your front page shows a WSOD, but not the admin page, this is likely the issue. Try adding the following to your configuration.php file. That should straighten things up

ini_set("memory_limit", "128M");

Admin module page not loading? Loading partially, but not completely? Try turning on the error debugging. This will usually let you know which plugin is the problem. I say usually, because some addon developers choose to suppress errors , making debugging that much more difficult.

As always, if these tips didn’t help, please do contact us. We love helping individuals out!