from 1.3.x to 1.4.6 > Fatal error: read_entry() from 1.3.x to 1.4.6 > Fatal error: read_entry()
 

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]

Main Menu

from 1.3.x to 1.4.6 > Fatal error: read_entry()

Started by chriz, May 20, 2006, 10:32:46 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

chriz

May 20, 2006, 10:32:46 AM Last Edit: May 27, 2006, 11:57:36 AM by GauGau
Albums at http://belang.photoevents.nu

Clicking on thumbnail generates this error:

Fatal error: read_entry() [function.require]: Failed opening required 'makers/olympus.php' (include_path='.:') in /var/www/vhosts/photoevents.nu/subdomains/belang/httpdocs/include/exif.php on line 608

Please advice,

Thanks,
Chriz

chriz

#1
May 20, 2006, 01:02:37 PM
Looking further on this board I found this text:

QuoteJust few days ago upgraded from 1.3.5 to 1.4.3 and noticed this.

Files / paths seem to be correct so I guess it's the EXIF's are crappy.

Is there any other fix to this than disabling EXIF that I just now did.
And based on this, I disabled read EXIF and read ITPC info from files.
Now the albums work, but I would like to know if this issue has been resolved.

Thanks,
Chriz

Aditya Mooley

#2
May 20, 2006, 01:16:51 PM
Make sure you have uploaded all the files in include/makers folder to your coppermine installtion.
--- "Its Nice 2 BE Important but its more Important 2 Be NICE" ---
Follow Coppermine on Twitter

Joachim Müller

#3
May 20, 2006, 01:26:29 PM

chriz

#4
May 20, 2006, 04:03:50 PM
I uploaded all files in that folder:
canon.php
fujifilm.php
gps.php
nikon.php
olympus.php
sanyo.php

Mind you, this is not urgent, the site works, but it would be nice to turn EXIF reading on for my next upload.

Chriz

chriz

#5
May 22, 2006, 03:51:27 PM
Hey,

As I said, it is not urgent, but could someone confirm me whether this is a bug in coppermine (error handling perhaps too) and if it is, whether there is a fix in the makings?

Thanks,
Chriz

Joachim Müller

#6
May 22, 2006, 07:36:32 PM
Not sure, I doubt that this is a bug in coppermine, but rather an unknown or broken EXIF field. You have to understand that EXIF if a pseudo-standard - camera manufacturers constantly modify their own EXIF specifications. Generally speaking, EXIF works fine. However, with particular pics that contain certain EXIF data, things might break. It's hard for us as Coppermine developers to keep track of the changes in EXIF standards, particularly because the exif library used by coppermine doesn't get updated any longer.

chriz

#7
May 27, 2006, 11:13:56 AM
Thank you for your reply.

I guess I'll have to work with exif disabled.
Enjoy your weekend,

Chriz
Print
Go Up Pages1
User actions