Cannot upload larger animated GIF files Cannot upload larger animated GIF files
 

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]

Main Menu

Cannot upload larger animated GIF files

Started by SonKitty, September 27, 2014, 09:58:59 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

SonKitty

Hello,

The problem boils down to that I can upload some files, such as smaller animated GIFs or pics that are not animated GIFs but are small or large .jpg files, but if I want to upload a GIF that's about over 200KB, most of my attempts are 500KB - 2MB, I am having trouble. My gallery can be found here: http://www.animecentral.net/gallery/

I contacted my host first about this issue recently and because I was also having trouble with Wordpress and getting similar errors.

-I explained my predicament to my host, and, skipping over my separate Wordpress issues, they told me there were some strict standards errors in my php_error_log.
-I searched on here how to fix that (http://forum.coppermine-gallery.net/index.php/topic,75836.msg365730.html#msg365730). There were multiple topics I found, but the one linked is the example I used and stated to be sure to restart my Apache server. Also, during all of this, I did upgrade my Coppermine gallery, just in case, but have the same problem as before, nothing seems to have really changed.
-I asked my host to restart the Apache server, as was advised in the topic here, since I did not have the necessary access. I was denied with them stating that things are set up for my site and their service so that I don't have to do that
-For reasons I do not know, my php_error_log stopped logging errors altogether last night, even when I changed it back to how things were before. So I've changed it back to what was advised on this forum so that the suggested change is already in effect (barring if my host is lying to me about not needing to restart the server). For now, I still have "error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT" in my php.ini to make it clear that change is in effect before coming here.

Today, I have spent a very long time going through the troubleshooting before posting this topic.
-I checked my permissions on the albums folders and updated them to what was suggested even though the uploads were already working for some files but not others.
-I cleared my cache for my gallery and still had the same issues.
-If I use the simple upload method, I just get a generic error message:
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@animecentral.net to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


-If I use the flash driven, it says a lot of stuff but the error part appears to be here:
SWF DEBUG: Event: uploadError: HTTP ERROR : File ID: SWFUpload_0_0. HTTP Status: 500.
Error Code: HTTP Error, File name: DaxterHeeHee.gif, Message: 500


Here's the test user account data:
    Username: Tester
    Password: test0123

Here's an example image, the main one, I've been trying:
http://38.media.tumblr.com/08d56255c973e7e4ad9de618de3f2910/tumblr_nbwxqmxBlp1qi4ajvo1_500.gif

There was one topic I found about calling an ISP to clear a cache regarding one's own website. Sadly, I cannot test that without going to the library and would rather not call them if that is not the issue as it appears to be under very specific circumstances (larger, animated GIF files).

Some php.ini settings that may be of some use:
max_execution_time = 60     ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
max_input_vars = 1000
memory_limit = 128M      ; Maximum amount of memory a script may consume (32MB)


It is not taking me over 60 seconds to receive the error messages. I receive them after a little over 30 seconds for the example file.

ron4mac

I suspect that you are not getting enough server memory for the thumb and intermediate files to be created.
If you are able to, place a plain text file titled ".user.ini" in the root of your CPG installation with the contents:

[PHP]
memory_limit = 256M


See if that will make a difference.

SonKitty

I seem to have resolved it partially while typing up the post below so I am noting it in case someone else comes across this topic.

~~~
I tried it, and things still didn't work, but a few different things happened at first before the 500 errors came back to what they were doing.

At first, I put it in the Coppermine root gallery, like I think you meant, but that didn't change anything. Then tried my web root (public_html) as well.

I got this error a couple of times:
http://www.animecentral.net/gallery/albums/userpics/10001/gallery_other_error.png

Then I tried it in Google Chrome (I usually use Firefox) to make sure it was consistent. It was not. The 500 error started happening again.

For my webhost, there is something where I can look at error logs, but it doesn't appear to log all of them and even the one that I saw around the time of working on this issue did not make much sense since it said it failed to find the file wp-login.php (a Wordpress file) in my root folder. I was not working in Wordpress at all. It looked like this: "File does not exist: /home/pathinfo/public_html/wp-login.php"

I tried setting up a custom 500 error page to tell me more information in but am too inexperienced to have given it any meaningful information, so I ended up deleting it, assuming the default page would come back. It didn't, so now the error that happens if you use a single upload takes you to a page that says the same error as my linked image above with a slightly different format:

Template error
Failed to find block 'output_buffer' (#<!-- BEGIN output_buffer -->(.*?)<!-- END output_buffer -->#s) in :

                    <div class="{CSS_CLASS}">
                        <h2>{HEADER_TXT}</h2>
                        <span class="cpg_user_message">{MESSAGE}</span>
<!-- BEGIN file_line -->
                        <br />
                        <br />
                        {FILE_TXT}{FILE} - {LINE_TXT}{LINE}
<!-- END file_line -->

                        <br /><br />
                    </div>


I was getting that error consistently for a simple upload.

I did find this topic (http://forum.coppermine-gallery.net/index.php?topic=65331.0), but repairing cpg_pictures had no effect.

While typing this up, I decided to check if the files were actually being uploaded. They were, and I noticed that intermediate files were being made. I usually have that option off. I turned it back off, and the flash-driven uploads started to work. Now I get the generic 500 error again (the one that says Internal Server Error) if I use the simple upload.

If you have any suggestions for how to fix things for simple upload, I'd like to know, in case I need it in the future, but the flash-driven upload is otherwise good enough for me.

ron4mac

#3
The problem with the simple file upload appears to be an issue with your theme not defining the "output_buffer" block. See how it is defined in themes/sample/theme.php. Try to use one of the standard themes (curve,rainy_day) to see if the majority of your issues clear up.

You may want to try this upload plugin too:
http://forum.coppermine-gallery.net/index.php/topic,75927.0.html

SonKitty

My theme was mainly based on water_drop with a few minor changes, so I just copied that theme.php over once I confirmed that the default water_drop theme worked properly. Thank you for all your help, everyone. I will mark this topic as solved once I finish this post.