Upgrading PHP causes display problems

[betterthanyours]

Hello, I tried to upgrade from 5.3 to a higher version. However, anytime I try to do so, it causes display problems.

Pre upgrading 5.3:
https://vborg.vbsupport.ru/external/2015/05/4.png
Post upgrading 5.3 (any version):
https://vborg.vbsupport.ru/external/2015/05/5.png

Any ideas how I can resolve this?

[Dave]

Are you sure that's not caused by one of your plugins? Does it also happen when you disable all plugins?

Also which PHP version is the upgraded one?

[Lynne]

What version of vBulletin? What version of PHP did you upgrade to?

[betterthanyours]

Hi. Sorry for the delay.

Using 4.2.0 PL3 and currently working PHP 5.3 (native) But soon as I upgrade or change to any version, including the 5.3 version that is custom compilable, it shows the above display. Does anyone know the full list of modules required? That might help to narrow down the issues.

Thanks in advance.

[ForceHSS]

If you upgrade php you also need to update your vb version as well this also means all skins and plugins

[Lynne]

Display problems are usually because of CSS. It's hard to tell exactly what is causing that block of images to move 'up' without being about to view the CSS for the site. But, you cannot run 4.2.0 with any higher version of PHP than 5.3. If you upgrade to PHP5.4, then you need to upgrade to vB4.2.2

[betterthanyours]

I understand the above from both your responses.

I am on a shared hosting system with cpanel and multiple php versions. The native version is 5.3. In the optionally listed versions, there are 5.4, 5.5, 5.6 and also 5.3. Meaning, I am able to select 5.3 as my version but choose custom modules. I hope this is clear and makes sense?

So, in the list are as above. 5.3 (native), 5.3, 5.4 etc etc. Even when I switch from.5.3 native to 5.3, it messes up....

[kh99]

You could view the html source of the page and see if there's some error message in the middle of the html somewhere.

[Lynne]

^^ Yep, what Kevin says. My guess is one of the css files is throwing an error.

Have you tried this using a totally default style, totally default files, and all modifications (including any .htaccess) disabled?