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: CPG 1.4.3  (Read 2176 times)

0 Members and 1 Guest are viewing this topic.

can93

  • Coppermine novice
  • *
  • Offline Offline
  • Posts: 38
CPG 1.4.3
« on: March 17, 2005, 11:27:29 pm »

Hello,

I can't post on the official forum, so i do it there...

I want to ask if i already update the 1.3.2 to 1.4.3 ?

For sure i'll make i back up, and i wan't know if they're more sql tables or they are the same ?

Only files will be overwriten ? Or i mus make some other sql tables ? Use the update utility present into coppermine ?

Thanks for all response.
Logged

kegobeer

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 4637
  • Beer - it does a body good!
    • The Kazebeer Family Website
Re: CPG 1.4.3
« Reply #1 on: March 18, 2005, 01:20:04 am »

1.4 hasn't been released for public use.  Don't use it on a production site.  If you want to try the anonymous CVS version, read the documentation before attempting to upgrade.
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

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: CPG 1.4.3
« Reply #2 on: March 18, 2005, 10:04:25 am »

there's no such thing as cpg1.4.3 yet anyway, the version count currently is at cpg1.4.1
This is all being described in the thread Important (must read!): "cpg1.4 testing/bugs board" rules and regs. Don't the words "must read!" ring a bell?

Joachim
Logged
Pages: [1]   Go Up
 

Page created in 0.015 seconds with 20 queries.