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: Getting an error  (Read 2932 times)

0 Members and 1 Guest are viewing this topic.

Corrupted

  • Coppermine novice
  • *
  • Offline Offline
  • Posts: 26
Getting an error
« on: July 04, 2008, 09:20:22 pm »

Ok hopefully this is the right spot to post this.

I just started gettin an error out of the blue not sure what is going on but this is the error


Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 4000 bytes) in /home/touring/public_html/gallery/include/picmgmt.inc.php on line 262


Any ideas?  Thx's
Logged

Nibbler

  • Guest
Logged

diablo74

  • Coppermine newbie
  • Offline Offline
  • Posts: 1
    • Llanelli Underground
Re: Getting an error
« Reply #2 on: August 06, 2008, 12:28:28 pm »

I'm getting the same problem and it can be resolved by resizing photos before uploading but the files do have to be quite small to get them up. I've got the upload limit set at a width of 2000 pixles and a file size of 1.5MB but I tried uploading a photo with a width of 1500 pixles and a file size of 500kb and was still giving me the same error message.
I'm using GD 2.0.28 compatible, it it worth me installing imagemagick or won't that make any difference? Any other tips for uploading lager images (I can't access the php.ini file) or do I stick to resizing everything first?
Thanks
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: Getting an error
« Reply #3 on: August 06, 2008, 01:29:41 pm »

If you can't access php.ini then you won't be able to install ImageMagick neither. Those are server-sided restrictions, i.e. they have been imposed by your webhost. Talk to your webhost, not us.
Logged
Pages: [1]   Go Up
 

Page created in 0.026 seconds with 19 queries.