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: [Invalid]: pnCPG 5.01 and cpg1.5.3  (Read 8339 times)

0 Members and 1 Guest are viewing this topic.

Mader6000

  • Coppermine newbie
  • Offline Offline
  • Posts: 2
[Invalid]: pnCPG 5.01 and cpg1.5.3
« on: April 30, 2010, 08:36:55 pm »

the plugin blocks don´t work right with new version.
Databasequery failed. ( .owner_name) failed any solutions? ???
pn .765 worked with cpg1.4.26
« Last Edit: May 01, 2010, 11:14:43 am by Joachim Müller »
Logged

phill104

  • Administrator
  • Coppermine addict
  • *****
  • Country: gb
  • Offline Offline
  • Gender: Male
  • Posts: 4886
    • Windsurf.me
Re: pnCPG 5.01 and cpg1.5.3
« Reply #1 on: April 30, 2010, 09:04:57 pm »

[Sarcastic Mode] I went to the doctor last week and said my mate was sick with this pain. Funnily enough he just couldn't work out what was wrong with him. [/Sarcastic Mode]

At least post a link - http://forum.coppermine-gallery.net/index.php/topic,55415.0.html
Logged
It is a mistake to think you can solve any major problems just with potatoes.

Mader6000

  • Coppermine newbie
  • Offline Offline
  • Posts: 2
Re: pnCPG 5.01 and cpg1.5.3
« Reply #2 on: April 30, 2010, 11:37:31 pm »

i can`t post a link becouse if i have enabled the block (random) complete site white with ^^error.
In release 1.5.3rc1 the owner_name field is dropped from table pictures
Code: [Select]
ALTER TABLE `CPG_pictures` DROP `owner_name`;so this querys failes in plugin blocks
Code: [Select]
if ($vars['nouser'] == 'y'){
$query = "SELECT $cpgprf"._pictures.".owner_name, $cpgprf"._albums.".title, $cpgprf"._pictures.".caption,$cpgprf"._pictures.".filepath,$cpgprf"._pictures.".filename,$cpgprf"._pictures.".hits,$cpgprf"._albums.".aid,$cpgprf"._pictures.".pid  from $cpgprf"._pictures.",$cpgprf"._albums."   WHERE $cpgprf"._pictures.".aid = $cpgprf"._albums.".aid and $cpgprf"._pictures.".approved = 'YES' and category < 10000  and find_in_set( visibility, '$view_list') > 0 and UPPER(RIGHT($cpgprf"._pictures.".filename,3))='JPG' order by RAND() limit 1 ";
} else {
$query = "SELECT $cpgprf"._pictures.".owner_name, $cpgprf"._albums.".title, $cpgprf"._pictures.".caption,$cpgprf"._pictures.".filepath,$cpgprf"._pictures.".filename,$cpgprf"._pictures.".hits,$cpgprf"._albums.".aid,$cpgprf"._pictures.".pid  from $cpgprf"._pictures.",$cpgprf"._albums."   WHERE $cpgprf"._pictures.".aid = $cpgprf"._albums.".aid and $cpgprf"._pictures.".approved = 'YES' and find_in_set( visibility, '$view_list') > 0 and UPPER(RIGHT($cpgprf"._pictures.".filename,3))='JPG' order by RAND() limit 1 ";
Logged

Joe Carver

  • Dev Team member
  • Coppermine addict
  • ****
  • Country: us
  • Offline Offline
  • Gender: Male
  • Posts: 1545
  • aka 'i-imagine'
    • Home Page
Re: pnCPG 5.01 and cpg1.5.3
« Reply #3 on: April 30, 2010, 11:54:12 pm »

n release 1.5.3rc1 the owner_name field is dropped from table pictures

There are many deep differences between cpg1.4.x and cpg1.5.x.

That also includes where the support requests should be posted. If you are using 1.5.x then you should be posting in that area of the support forum.

phill104

  • Administrator
  • Coppermine addict
  • *****
  • Country: gb
  • Offline Offline
  • Gender: Male
  • Posts: 4886
    • Windsurf.me
Re: pnCPG 5.01 and cpg1.5.3
« Reply #4 on: May 01, 2010, 09:47:48 am »

Why does that stop you posting a link?
Logged
It is a mistake to think you can solve any major problems just with potatoes.

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: pnCPG 5.01 and cpg1.5.3
« Reply #5 on: May 01, 2010, 11:14:32 am »

  • cpg1.5.x can't be used with pnCPG
  • The thread starter misbehaved by posting on the wrong board and failed to post a link although being told.

Subsequently, I'm closing and locking this thread.

@Mader6000: do as suggested per board rules in the future or don't bother posting at all.
Logged
Pages: [1]   Go Up
 

Page created in 0.026 seconds with 20 queries.