Author Topic: nBill Quote/Order/HelpDesk Frontend Pages are Blank  (Read 191 times)

Offline pozo15

  • Jr. Member
  • **
  • Posts: 2
    • View Profile
nBill Quote/Order/HelpDesk Frontend Pages are Blank
« on: 29/May/2012, 07:38:35 PM »
I seem to be having an issue with my nBill.

Everything was working perfectly fine, I do not know at what point nBill stopped working properly so I cannot tie the issue to any event or change on the website.
Basically, when I did a live site check one day, all the frontend pages that used nBill were completely blank. On the backend everything seems to be just fine.
-My license is active
-I don't see any errors reported by nBill
-nBill on my other site works with no issues.

I was wondering if anyone else has had a similar issue or if the dev could weigh in on this as I am out of ideas.
Here is the site in question: http://tamlaser.com/services
You can click on either buttons and see what I'm talking about.

Thank you!

Offline netshine

  • Administrator
  • Hero Member
  • *****
  • Posts: 4,955
    • View Profile
Re: nBill Quote/Order/HelpDesk Frontend Pages are Blank
« Reply #1 on: 29/May/2012, 07:49:46 PM »
A blank screen is usually indicative of a PHP error - check the public_html or www folder of your account for a file named 'error_log' and see what it says, or if your web hosting control panel allows access to the error log, check that for error messages too. Also, if you use a custom php.ini file in your /administrator folder to load ionCube, copy that into the root folder as you might have ionCube installed in administrator but not in the front end. You could also try using the ionCube loader wizard (that comes with the ionCube loaders) in the root folder of your website to check for ionCube problems.

Failing all that, please submit a support ticket so I can login and take a look.

Offline pozo15

  • Jr. Member
  • **
  • Posts: 2
    • View Profile
Re: nBill Quote/Order/HelpDesk Frontend Pages are Blank
« Reply #2 on: 30/May/2012, 05:18:10 PM »
Fixed. It was the php.ini that was the issue.
It did not get properly ported over when my host moved me to a different server.
Thank you.