Uploading Big files... HELP Uploading Big files... HELP
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Uploading Big files... HELP

Started by heyimkay, June 21, 2006, 01:19:47 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

heyimkay

For some reason the version cpg1.4.8 won't let me upload big files. Like 1000x1000. It says something about the file include/picmgmt.inc.php

HELP PLEASE!

Vargha

if u want to upload a big file
u have to get access to ur php.ini
and find
post_max_size
and
upload_max_filesize
and set the values to higher
try and see if that works for u  :)
Haalaa Boro Ye Chayi Vasam Dorost Kon Ta Man Ye Fekri Be Halet Bokonam ;) Ye Hendooneye Shotoriham Biyar Bizahmat :)
Visit My Site www.Rangarang.co.nr
Check Out My Gallery
www.Rangarang.co.nr/buddies
(https://coppermine-gallery.com/forum/proxy.php?request=http%3A%2F%2Fimg157.imageshack.us%2Fimg157%2F838%2Frangarang4xn.jpg&hash=48b4c3087515cafe09fc6d3f7ee19dce86328d8e)

Paver

@Vargha: That's not the first thing to do.  It may be necessary, but there are a few other things to check first.

@heyimkay: Post the error message here.  And check your configuration settings for "Files and Thumbnails" - ensure you that you are allowing large files in the configuration.  A link to your site with a test user account (with upload privileges) may be helpful as well.

Joachim Müller


heyimkay

thanks for your help! i'm still confused... this is what i get when i try uploading big files:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 6528 bytes) in /home/heyimkay/public_html/brendasong/pictures/include/picmgmt.inc.php on line 262

Joachim Müller

Re-read the sticky I told you about - it contains details on your particular error message.

heyimkay


Paver

Quote from: heyimkay on June 21, 2006, 08:23:41 PM
where is the php.ini?

If you are asking that question, you most likely cannot edit it.  It is the PHP server configuration file.  You only have access to it if you are the server administrator, as the sticky thread says.

heyimkay


Paver

Then it should be in the main PHP directory.

heyimkay

would i find it in my files or like the actual place where my gallery is?

Paver

Are you sure you are the server administrator? 

I think you are thinking that being the Coppermine administrator is the same thing - it's not.

If I'm wrong, then you should know where your PHP directory is.  I cannot tell you for certain where it is on your server.

heyimkay

okay. my mistake. Is the server administrator have anything to do with whos hosting the site and such?

Paver

Yes.  PHP is run as an extension or module on the webserver, which is run by your webhost.

heyimkay

i'm so sorry for my stupidity, but i never had this problem before. and I do host the gallery and such. i'm still unclear.

Joachim Müller

So you're self-hosted? The server is yours to administer? Then you should know where php.ini resides. If you don't, then I strongly suggest reviewing the whole concept of self-hosting. It's not recommended to run your own webserver publicly if you have little idea what you're actually doing.

Sami

#16
- if you are not self hosted , there is a option chance for you
you can create a php.ini file and copy it to your gallery folder


[edit]:as GauGau suggested below
‍I don't answer to PM with support question
Please post your issue to related board

Joachim Müller

This only applies if your webhost allows you to do that. Most webhosts don't.

Paver

@heyimkay: You mentioned this didn't happen before.  If you are sure files of this size were fine before, then something happened to increase the memory footprint of Coppermine.  I'm not sure what would do this.  Have you installed any plugins?  You could try the classic theme, although I don't think the theme would create a much larger footprint unless you define a lot of user variables.

If you mean that this didn't happen in earlier versions before 1.4.8, then I'm also not sure what would have changed in 1.4.8 to give this larger memory footprint.  The changes are small - although they are large in impact having to do with security fixes - but I cannot think of one change that would do this.