Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: [FIXED] White Screen After Upload  (Read 3314 times)

0 Members and 1 Guest are viewing this topic.

darvenger

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
[FIXED] White Screen After Upload
« on: March 05, 2006, 05:12:11 am »

Hope I'm posting in the right forum ;) Anyways... I recently installed Coppermine (absolutely great add-on!) and every time I uploaded a large pic I would receive the message that the file was uploaded, then when I clicked on continue, I would receive a white screen. I searched through the help and couldn't find an answer. I fixed it, and I am posting my resolutions so that others may (or may not) benefit.

First, my board is phpBBFM... so it's fantastic that this runs fairly independent since the thing has 250 or so phpBB2 modifications made to it. This solution may only apply to phpBB2 boards.

Second, if you get a white screen, try to recall if you've made any modifications to your board. If you have error notifications turned off, you will only receive a white screen. In my case I had a security modification installed, which apparently had some major errors in it. However, because my php error notification was turned OFF, I didn't know where the error was. In this case, it WAS NOT related to Coppemine... the error was an error carried forward and was affecting the operation of Coppermine. Strange, because I didn't think this mod would mess it up... but it did.

I went to my php.ini file, and modified it per the below bold highlights. You may have to contact your host company to do these changes, in my case I did it myself, then restarted the server. My php.ini file is located in ftp/usr/lib path.

[PHP]


; Print out errors (as a part of the output).  For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below).  Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = On
<---

After I edited that portion of my php.ini file, I was able to troubleshoot my existing board errors, and that intern fixed Coppermine. I didn't think that a collission existed... but it did and turning error reporting on helped me hone in on the problem.

If you haven't worked on your php.ini file before, make sure you make a backup copy in the event you mess it up.
« Last Edit: March 05, 2006, 10:39:27 am by GauGau »
Logged
Pages: [1]   Go Up
 

Page created in 0.031 seconds with 19 queries.