PhotoPlog - Blank page after upgrading vBulletin

PhotoPlog (http://www.photoplog.com/forum/index.php)

- Troubleshooting & Problems (http://www.photoplog.com/forum/forumdisplay.php?f=6)

- - Blank page after upgrading vBulletin (http://www.photoplog.com/forum/showthread.php?t=2954)

Blank page after upgrading vBulletin

Hi Morgan,

I have Photoplog Pro 2.1.4.8 installed on my forums. I recently upgraded vBulletin to 3.8.4 from 3.8.2 and the gallery no longer works. I've uninstalled / reinstalled several times now and it just gives me a blank page 500 error on IE8 and blank page on Firefox.

I've checked all the paths and they're exactly the same as they were before I upgraded and none of the other mods are broken.

Checking my forum error log file I get the following two errors every time I try to access the gallery.

Code:



mysite.co.uk [Fri Sep 18 21:23:29 2009] [error] [client 81.109.65.42] File does not exist: /home/sites/mysite.co.uk/public_html/forums/js, referer: http://www.mysite.co.uk/forums/index.php



telcontarshope.co.uk [Fri Sep 18 21:23:29 2009] [error] [client 81.109.65.42] File does not exist: /home/sites/mysite.co.uk/public_html/forums/css, referer: http://www.mysite.co.uk/forums/index.php

Any help would be appreciated. :)

Regards,
Renada

Try checking the PhotoPlog config.php file: http://www.photoplog.com/forum/showthread.php?t=1725

Quote:

Originally Posted by Morgan (Post 19844)

Try checking the PhotoPlog config.php file: http://www.photoplog.com/forum/showthread.php?t=1725

Yes, have already checked that and I still get the white page. It's very strange since it was working perfectly but stopped after upgrading vBulletin.

I've even tried turning off every other plugin I have in case one was now interfering with the gallery and that didn't work either.

Quite frankly I'm baffled and am hoping you have a magical answer somewhere :)

Regards,
Renada

When there is no error message, just a blank page, there is no clue for me to determine whether this is a PhotoPlog problem or a problem related to another modification. Here are some things to try if you receive another blank page:

Add a plugin to the photoplog_upload_start hook with the following code and see if an error message shows on screen (how to add a plugin):

Code:

ini_set('display_errors', true);
Have your host set display_errors to on in the php.ini file.
Temporarily disable all modifications except PhotoPlog and see if the problem goes away.
Check your server error log for error messages.

Quote:

Originally Posted by Morgan (Post 19848)

Add a plugin to the photoplog_upload_start hook with the following code and see if an error message shows on screen (how to add a plugin):

Code:

ini_set('display_errors', true);
Have your host set display_errors to on in the php.ini file.
Temporarily disable all modifications except PhotoPlog and see if the problem goes away.
Check your server error log for error messages.

Hi Morgan,

I've really no idea what's going on here. The gallery worked flawlessly until I upgraded to vBulletin 3.8.4.

This is what I've tried so far:

1) checked the config file
2) checked the gallery paths
3) switched off all plugins, uninstalled and reinstalled
4) added the plugin you suggested which gives this error:

Code:

The website cannot display the page 

 HTTP 500  

   Most likely causes:

•The website is under maintenance.

•The website has a programming error.

 

   What you can try: 

     Refresh the page. 

 

     Go back to the previous page.

5) What DOES show up are the thumbnails on forum home if I put $photoplog[thumbnails] in the template.

I'm quite happy to give you ftp and admin access if you think you could figure out what went wrong here. :)

Regards,
Renada

Did you delete the vbulletin_textedit.js file from inside the PhotoPlog /images directory if present? Do NOT delete the vbulletin_textedit.js file inside the vB /clientscript directory. If that doesn't work, try asking your host if they can tell what is going on. A 500 Internal Server Error gives me no clue as to the problem, especially as there are others out there running both scripts without that error.