Advanced search  

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

Pages: [1]   Go Down

Author Topic: Updating from 1.2.0final to 1.3.0  (Read 2964 times)

0 Members and 1 Guest are viewing this topic.

Briard

  • Coppermine newbie
  • Offline Offline
  • Posts: 13
    • http://www.briard-at.com
Updating from 1.2.0final to 1.3.0
« on: July 02, 2004, 09:12:34 pm »

Hi,

I want to upgrade  my photo gallery to the latest version (I am running 1.2.0final) - and I have of course read the upgrading instruction in the package. My question (sorry, but I am really not sure what to do):

The instruction says:
Quote
If the file install.php exists in the root directory, delete it.
Is it meant to delete this file on the server or in my local directory?

Thanks in advance for an input.

Kind regards
Gerda
Logged

Casper

  • VIP
  • Coppermine addict
  • ***
  • Country: 00
  • Offline Offline
  • Gender: Male
  • Posts: 5231
Re: Updating from 1.2.0final to 1.3.0
« Reply #1 on: July 02, 2004, 09:15:42 pm »

as you are upgrading, not installing, you don't need this file.  The instruction is actually refering to the one on your hard drive, not the server, but it doesn't really matter, as long as your include folder(on the server) has a file called install.lock in it, others cannot run a malicious install.
Logged
It has been a long time now since I did my little bit here, and have done no coding or any other such stuff since. I'm back to being a noob here

Briard

  • Coppermine newbie
  • Offline Offline
  • Posts: 13
    • http://www.briard-at.com
Re: Updating from 1.2.0final to 1.3.0
« Reply #2 on: July 03, 2004, 12:12:41 am »

Hi,

as you are upgrading, not installing, you don't need this file.  The instruction is actually refering to the one on your hard drive, not the server, but it doesn't really matter, as long as your include folder(on the server) has a file called install.lock in it, others cannot run a malicious install.

THANKS Casper!!!

Best regards & have a nice weekend
Gerda
Logged
Pages: [1]   Go Up
 

Page created in 0.027 seconds with 20 queries.