[Solved]: Fatal Error in the gallery. [Solved]: Fatal Error in the gallery.
 

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

[Solved]: Fatal Error in the gallery.

Started by zamirzamir, February 17, 2008, 07:44:51 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

zamirzamir

Hello,

My web host (bluehost) did some sort of security update on the server and since that moment my gallery does not work. Unfortunately I have no idea where even to start looking for the problem. all the files are there, but nothing works.
I have contacted the provider, but they said it's not really their consern, since it was a third party application.
Gallery was updated to latest version.
Here is the link if you want to take a look www.adygaunion.com.gallery

PLease advice on where to start looking for the problem.



Joachim Müller

Enable debug mode in coppermine's config if you can access it. If not, enable it manually as suggested in http://coppermine-gallery.net/tutorial/debug_mode.php
This should give you an advanced error message that tells you what actually goes wrong. Post the error message (not the debug_output) here.

zamirzamir

Thanks for your help, but my friend fixed it. One of my SQL tables went bad.

zamirzamir

Nother problem came up. When I try to open any image this message comes up

There was an error while processing a database query


What should i do next ?

Joachim Müller

The very same advice I posted above applies:
Quote from: Joachim Müller on February 17, 2008, 02:10:13 PM
Enable debug mode in coppermine's config if you can access it. If not, enable it manually as suggested in http://coppermine-gallery.net/tutorial/debug_mode.php
This should give you an advanced error message that tells you what actually goes wrong. Post the error message (not the debug_output) here.

zamirzamir

I ran debug mode for administrator. No error message was in the output.
While logged in I could click and see images full size.
As soon as I log out , only thumbnails are availible and the critical error message appears when I click on images.

Joachim Müller

Let me repeat: enable debug_mode for everyone, then try to replicate the error message. Post a link to the page that displays the error message.

zamirzamir

While executing query "INSERT INTO cpg133_hit_stats
                          SET
                            pid = 10552,
                            search_phrase = '',
                            Ip   = '*.*.*.*',
                            sdate = '1203581138',
                            referer='http%3A%2F%2Fwww.adygaunion.us%2Fgallery%2Findex.php',
                            browser = 'Unknown',
                            os = 'Windows XP'" on 0

mySQL error: Table 'adygauni_coppermine.cpg133_hit_stats' doesn't exist

Joachim Müller

The error message should be pretty self-explanatory, don't you agree? The table doesn't exist. I have run update.php for you - check if this solves your issues, i.e. if the missing table has been created. If it hasn't been created, review the permissions of your mysql user account.

zamirzamir

the problem did get solved after your update, now I can return to my work. Soon will be moving the gallery to a better hosting provider, this host caused a lot of issues in all php applications on the site and they refused to help solve them.
Thank you for help Admin.

Joachim Müller

The issues you had have most likely not been caused by your webhost. You can't expect your webhost to solve issues with third party apps for you. Imo you ask a bit much from your webhost - something that you won't find someplace else, so your move might not solve your PEBKAC-issues. Your webhost may or may not be bad, but I just wanted to let you know that this sort of webhost-bashing doesn't sound very wise. It appears that you (or something that you're responsible for, like an application update) have made a mistake imo.