Problems from web host server upgrade

[bojangles]

I'm having problems after my web host upgraded the PHP on my account. I don't know what they had on before but lowest version of supported PHP is now 5.3... And now some of my code is broken.

Awaiting advice from you on how to proceed. Please help!

[Beverleyh]

Can you see any error messages when you view your web pages in a browser?

[bojangles]

Hey, thanks for answering.

No I do not see any error messages. Some of my code just stopped working and I don't know what to do. My website 'friend' abandoned me once this mess started with the web host and I have no one else to ask who knows this stuff.

Can you help me please?

[Beverleyh]

We can try to give you a few pointers but we need to see the error messages first.

First step = get the specific PHP error messages that say what's wrong
Second step = you can then act upon the error messages one by one

You need to turn PHP errors on first though - you can do that in a few ways and it may be that you have them already without realising. Check in your control panel for error logging. Errors may be printed to a master file or they may be generated in a log file inside individual folders where the scripts run. Have a look and report back with your findings.

[bojangles]

I have error reports at my web host CP but I'm having problems opening them. They are crashing my browser cuz they are so big. Is there another way? You said something about errors in the browser?

[Beverleyh]

Maybe. Do you have access to your php.ini file? You can normally turn errors on there and see them in your browser;
display_errors = onif you can, pop that line in (or check if the line is there but set to 'off', and if so, change it to 'on'), save and view the offending page in a browser.

[bojangles]

No I do not have access to my php.ini file. I tried to make one but my whole site went down so I guess that was a no-no, right?

I feel like all my doors are closing. Is there anything else I can change or it seems like my website is doomed to die.

[Beverleyh]

The good thing is that errors are being logged. If the file size of your CP error log is a problem, try asking your web host to clear it or extract the last few lines for you and send it on via email.

You might also have the option of setting up reporting via an .htaccess file. Can you find out if you can use .htaccess?

[bojangles]

I really appreciate your helping me with this. I don't have answers yet but I have emailed my host support desk for assistance with the error report and htaccess. I thank you for your patience and will be back soon.

[Beverleyh]

No problem. Let us know what your web host says.

[bojangles]

Yet more doors are closing. I can't use htaccess and the support desk won't touch my error report cuz they say it will clear itself at the start of each calendar month. I can't wait that long. Is there nothing else to try to get me out of this mess? I can't afford to get a new website :(

Your the only person who is willing to help me. Please help me. I need your help.

[Beverleyh]

I can try to help but I have my own work too I'm afraid. I only volunteer here.

The last thing you can do as far as I'm aware is to try to turn errors on at run time. That means to give an instruction at the start of a PHP script. Try this at the top of your PHP file. If you have lots of PHP files working together, put it in either a header file or functions file - you'll need to have a look around your website folders to find a suitable spot.
error_reporting(E_ALL);
ini_set('display_errors', '1');be aware that this won't show *all* PHP errors, but it should show enough to point you in the right direction.

[bojangles]

YES! It works! I can see errors on my website but they're kinda hiding behind stuff so how do I get them 'out' to the foreground?

Thank you for your help here. I REALLY appreciate what you're doing for me.

[james438]

Can you post a link to your website or even a test page where you are seeing the errors?

[Beverleyh]

The quickest way would be to try to highlight and copy the errors from your screen and then paste them in to Notepad or Word.

You could also use the Developer Toolbar (F12 in most browsers) to select the elements that are blocking your view and set them to display:none; in the style/CSS pane.

Once you have the errors in front of you they'll tell you what the problem is, and in which file it lies. A line number will also be given to help you pin-point the offending piece of code.

[bojangles]

Okay I can see the errors now and can find the files where they reside, but the line numbers are a problem for me. What do I do to count them out? Some are as far on as line 412

[Beverleyh]

Download this freebie and view your problematic script file inside it https://notepad-plus-plus.org/download/v6.8.8.html Numbers display down the left.

[bojangles]

Thanks again!

Looks like I have my work cut out for me fixing all of these errors!

[Beverleyh]

Im glad it worked :)

You can usually Google the errors to find answers, but you can also start a new thread here for further help if you need it.