Weird issues with only some php pages

[Shill360]

I am having a very strange issue that has only happened since 2 days ago. No pages have been modified and no templates changed. Nothing installed.

The issue is that some php pages are just not being displayed, there is no error message however on the browser, just a white page saying done. My host says there are no error messages on the apache server.

I have tried changing templates to see if thats the issue but it isnt, the same thing happens on the default vbulletin template. I have also tried replacing the files with original ones but to no avail.

The pages in question are as follows

/forums/online.php
/forums/member.php?u=xx
/forums/blog.php (mod)
/forums/staff.php (mod)

All other php pages work correctly and load fine, both standard vbulletin and addons.

Anybody else ever had this problem, and if so how did you fix it.

I am currently on version 3.7.2

An example of this page is here - http://www.onlinearsenal.com/forums/staff.php permissions are set to allow this page viewable to everyone and anyone.

[Infopro]

That link you've posted returns a 500 Internal Error. Your host should see this in his log I would think.

http://www.checkupdown.com/status/E500.html

Ask your host if they're using SuPHP and if so, be sure all files that do not work like this, have permissions of 644 and folders 755

You might also go to your vbadmin page > Maintenence section > Diagnostics > Suspect File Versions tool and use it to check your vb files for issues.

[Shill360]

Thanks for the reply. I will ask my host.

All folders do have 755 and all files do have 644 permissions.

I will use the diagnostics tool now.

[Lynne]

Here is a page from the manual about troubleshooting blank or 'white' pages: http://www.vbulletin.com/docs/html/blank_pages

[Shill360]

Thanks Lynne, I have tried everything on that page but to no avail. It seems that page focuses on either the index page or all pages not visible. I am finding this really bizarre that it is only the 4 pages i mention above that are affected, especially as I havent changed or modified anything for over 2-3 months.

--------------- Added [DATE]1263831302[/DATE] at [TIME]1263831302[/TIME] ---------------

I might have to upgrade to see if that fixes the issue.

[Lynne]

Have you tried....
Create a new style with no parent:

• Styles & Templates > Style Manager > Add New Style
• Parent Style: No Parent Style
• Title: Default vBulletin
• Allow User Selection: Yes
• Save

Then browse the site using that totally default vbulletin style - do you still get a blank page on those four pages?

If it is still happening - Try disabling your modifications/plugins and see if you still have this problem.
Note: To temporarily disable the plugin system, edit config.php and add this line right under <?php

PHP Code:

define('DISABLE_HOOKS', true); 


[Shill360]

Yep, I have tried doing everything you have mentioned there but still those pages wont load or show a blank white page.

The one thing I have noticed is that I have some version mismatches since re-uploading those pages. On the diagnostics tool it outputs this :

member.php File version mismatch: found 3.7.2 Patch Level 2, expected 3.7.2

I cant seem to download version 3.7.2 without patch 2 from vbulletin.com

[Lynne]

patch levels don't show up in the suspect file... or rather, they always get marked as suspect because you didn't update the md5 for them (or rather, vbulletin doesn't update the md5 for them for you).

What is in your error_logs? There must be something there. (If you don't know where they are, ask your host.)

[Shill360]

Hi Lynne, thanks for your help, I have now found the issue. It looks like the account was compromised as /includes/functions_online.php contained no data as well as blog.php

Now I am on my home PC I had a backup so was able to replace these files with my backup ones and everything is back to normal.

I cant believe I didnt see this when looking today, anyway apologies for wasting your time. I am now off to change my FTP password

[Lynne]

If I were you, I still think it would be a good idea to look through your error_logs (and perhaps access_logs). Both are usually in the same place. You might find something in there to help you figure out what happened.