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: php.ini setting 'register_long_arrays' is enabled  (Read 7418 times)

0 Members and 1 Guest are viewing this topic.

axisdata.network

  • Coppermine newbie
  • Offline Offline
  • Posts: 8
php.ini setting 'register_long_arrays' is enabled
« on: November 24, 2005, 03:38:53 pm »

hello everybody! I'm trying to setup to coppermine script for the first time, I got all the hosting server information to be able to setup it, but when I submit I always got the following error. I was looking at the forums here, and I found that the webhost should do this task, isn't it any other way to setup this variable muy ourselves?

Thanks very much in advance and the best regards,
Carlos
« Last Edit: November 25, 2005, 10:26:17 am by GauGau »
Logged

kegobeer

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 4637
  • Beer - it does a body good!
    • The Kazebeer Family Website
Re: php.ini setting 'register_long_arrays' is enabled
« Reply #1 on: November 24, 2005, 03:43:45 pm »

If you are using 1.4, long arrays are not required and should not interfere with installation.  If you are using 1.3.5, you must enable long arrays.  Only your webhost can do that, as it means editing php.ini.
Logged
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

axisdata.network

  • Coppermine newbie
  • Offline Offline
  • Posts: 8
Re: php.ini setting 'register_long_arrays' is enabled
« Reply #2 on: November 25, 2005, 10:21:13 am »

Ok, thank you very much...

Rega,
Logged
Pages: [1]   Go Up
 

Page created in 0.016 seconds with 15 queries.