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: Some issues with CpmFetch 2.0  (Read 5617 times)

0 Members and 1 Guest are viewing this topic.

Sandrina

  • Coppermine novice
  • *
  • Offline Offline
  • Posts: 45
Some issues with CpmFetch 2.0
« on: March 16, 2014, 11:05:21 am »

Hi.
My friend have some issues with her site ans ask me to help her with шею

She has 1.5.24 version of Coppermine Gallery and latest version of CpmFetch.

But she has next error when i trying to install CpmFetch:

Code: [Select]
Strict Standards: Declaration of cpm::debugPrint() should be compatible with cpm_dao::debugPrint() in /home/evansch/public_html/images/cpmfetch/cpmfetch.php on line 50
and

Code: [Select]
Deprecated: Function split() is deprecated in /home/evansch/public_html/images/cpmfetch/install.php on line 312
Site adress http://evans-chris.com/

Can you help me to solve it? Thank you very much.
Logged

Sandrina

  • Coppermine novice
  • *
  • Offline Offline
  • Posts: 45
Re: Some issues with CpmFetch 2.0
« Reply #1 on: March 16, 2014, 12:20:38 pm »

Problem is solved!) ;)
Logged

Sandrina

  • Coppermine novice
  • *
  • Offline Offline
  • Posts: 45
Re: Some issues with CpmFetch 2.0
« Reply #2 on: March 16, 2014, 12:25:16 pm »

No, is normaly view only in Mozila Firefox. in Goggle Chrome is still have some errors.
Logged

phill104

  • Administrator
  • Coppermine addict
  • *****
  • Country: gb
  • Offline Offline
  • Gender: Male
  • Posts: 4885
    • Windsurf.me
Re: Some issues with CpmFetch 2.0
« Reply #3 on: March 16, 2014, 04:07:59 pm »

First, you should upgrade to 1.5.26 as this version has a security fix that should not be overlooked. It may even fix your problems. Having said that, strict standards errors are generated by your server as warnings. If they are now only showing in one browser and clear in the others then you probably have some cache switched on in that browser. Clear that and see if the error goes.

Also, please be aware that cpmfetch was never really released for CPG1.5.x and the version that you and many used is simply a quickly modified version which was designed for 1.4.x. We cannot fully support it as the chap who wrote it has not been around for quite some time, which is a real shame.
Logged
It is a mistake to think you can solve any major problems just with potatoes.

madaxeman

  • Coppermine newbie
  • Offline Offline
  • Posts: 12
Re: Some issues with CpmFetch 2.0
« Reply #4 on: April 27, 2014, 11:19:16 pm »

Not sure if this will help someone identify how to fix the 
Code: [Select]
Strict Standards: Declaration of cpm::debugPrint() should be compatible with cpm_dao::debugPrint() issue, however thought it might be relevant that I've got instances of cpmfetch running on different pages of my site .... some of which generate this error and some don't.

Where it doesn't seem to throw up the error message is here on my home page which is in the root directory. The cpmfetch code here is:

Code: [Select]
<?php
 
include "./GALLERYDIRECTORY/cpmfetch/cpmfetch.php";
 
$objCpm = new cpm("./GALLERYDIRECTORY/cpmfetch/cpmfetch_config.php");
 
$objCpm->cpm_viewRandomMedia(1,3);  
 
$objCpm->cpm_viewLastAddedMedia(1,3);
 
$objCpm->cpm_close();
?>


But on other pages like this one which sits in a different subdirectory the error message appears the first time a new cpm is called. On this page (in the subdirectory) the cpmfetch code is like this:

Code: [Select]
<?php 
include "../GALLERYDIRECTORY/cpmfetch/cpmfetch.php";                                                      
$objCpm = new cpm("../GALLERYDIRECTORY/cpmfetch/cpmfetch_config.php");                                                      
$objCpm->cpm_viewRandomMediaFrom("album=17",1,6);                                                        
  
?>


Is that useful to anyone ?
Logged

madaxeman

  • Coppermine newbie
  • Offline Offline
  • Posts: 12
Re: Some issues with CpmFetch 2.0
« Reply #5 on: May 03, 2014, 01:46:34 pm »

I've now got a rather blunt-instrument work-around.

1. Create a "hidden" class in the site CSS
Code: [Select]
.hidden {
visibility: hidden;
display: none;
}

2. Call the first instance of cpmfetch on the page inside a div using the new hidden class
Code: [Select]
<div class="hidden">
<?php include "../PATHTOCPM/cpmfetch/cpmfetch.php";
  
$objCpm = new cpm("../PATHTOCPM/cpmfetch/cpmfetch_config.php");
  
?>

</div>


3. Use the called instance to drive subsequent image placements on the same page
Code: [Select]
<?php 
  $objCpm
->cpm_viewRandomMediaFrom("cat=2",1,5);  
  
?>

Then any unsolved error message is hidden in the hidden div, which also calls cpmfetch for the rest of the page
Logged

dellos

  • Coppermine newbie
  • Offline Offline
  • Gender: Male
  • Posts: 3
    • elfpa - Europe Large Format Photographers Association
Re: Some issues with CpmFetch 2.0
« Reply #6 on: September 11, 2014, 02:13:05 pm »

I'm using the CpmFetch 2.1.1 and last stable cpg 1.4 I'm getting some errors:

Strict Standards: Declaration of cpm::debugPrint() should be compatible with that of cpm_dao::debugPrint() in /home/.../cpmfetch/cpmfetch.php on line 50
Strict Standards: Only variables should be assigned by reference in /home/.../cpmfetch/cpmfetch.php on line 419

Is there some sollution for this ??
Logged

phill104

  • Administrator
  • Coppermine addict
  • *****
  • Country: gb
  • Offline Offline
  • Gender: Male
  • Posts: 4885
    • Windsurf.me
Re: Some issues with CpmFetch 2.0
« Reply #7 on: September 11, 2014, 06:24:47 pm »

Yes, upgrade to 1.5.x. We have not supported 1.4.x for quite some times hence that error will not be fixed, sorry.
Logged
It is a mistake to think you can solve any major problems just with potatoes.
Pages: [1]   Go Up
 

Page created in 0.026 seconds with 19 queries.