coppermine-gallery.com/forum

Support => cpg1.3.x Support => Older/other versions => cpg1.3 Installation & Setup => Topic started by: med20 on July 10, 2004, 10:14:16 PM

Title: Fatal error : There was an error while processing a database query
Post by: med20 on July 10, 2004, 10:14:16 PM
After following the manual several times (and downloaded the upgrade a couple of times), with the same error, I tried these
Upgrade steps:
1. Backed up working version 1.2.1
2. Removed cpg directory
3. Copied 1.3.0 to cpg
4. Removed cpg/albums directory
5. Copied old albums directory to cpg
6. Copied old config.inc.php to cpg/include
7. Copied old anyconfig.php to cpg for good measure
8. Chown -R owner:group cpg
9. Chmod -R 755 cpg (tried without this then with)
(This was all done via ssh and I verified that the update.php file was the same size as the new downloaded file, and different from the one in 1.2.1)
10. Ran cpg/update.php with browser, got these results:
http://loudennis.com/cpg/update.php.htm

Clicked on "Let's continue !" and got this error:
http://loudennis.com/cpg/index.php.htm

I then remove cpg and copy 1.2.1 back and it works as before the upgrade.

Am I missing something?
Mark
Title: Re: Fatal error : There was an error while processing a database query
Post by: Joachim Müller on July 11, 2004, 12:35:45 AM
this may be a language issue, but the steps you describe are not the steps from the documentation.

GauGau
Title: Re: Fatal error : There was an error while processing a database query
Post by: med20 on July 11, 2004, 06:36:57 AM
You are correct, this list is not the same as the docs, I was anticipating someone suggesting that some files may not have actually been overwritten and eliminated that possibility.  But again, this is only because the original install didn't work.

btw: I just started over and followed the docs to the letter, with the same results.

Mark

Title: Re: Fatal error : There was an error while processing a database query
Post by: Joachim Müller on July 11, 2004, 10:10:47 AM
ok, please switch debug_mode on in coppermine config to see what query actually fails. If you can't access coppermine config, use a tool like phpMyAdmin to directly access your database, browse coppermne's config table and set debug mode to "1" there. Post the query that fails here.

GauGau
Title: Re: Fatal error : There was an error while processing a database query
Post by: med20 on July 11, 2004, 04:16:48 PM
While executing query "SELECT MAX(group_quota) as disk_max, MIN(group_quota) as disk_min, MAX(can_rate_pictures) as can_rate_pictures, MAX(can_send_ecards) as can_send_ecards, MAX(upload_form_config) as ufc_max, MIN(upload_form_config) as ufc_min, MAX(custom_user_upload) as custom_user_upload, MAX(num_file_upload) as num_file_upload, MAX(num_URI_upload) as num_URI_upload, MAX(can_post_comments) as can_post_comments, MAX(can_upload_pictures) as can_upload_pictures, MAX(can_create_albums) as can_create_albums, MAX(has_admin_access) as has_admin_access, MIN(pub_upl_need_approval) as pub_upl_need_approval, MIN( priv_upl_need_approval) as  priv_upl_need_approval FROM cpg11d_usergroups WHERE group_id in (3)" on 0

mySQL error: Unknown column 'upload_form_config' in 'field list'
Title: Re: Fatal error : There was an error while processing a database query
Post by: Casper on July 11, 2004, 09:02:01 PM
Use your db tool to check the usergroups table, to see if the field 'upload_form_config' actually exists.  If not, create it, to these specs;
Quoteupload_form_config,  tinyint(4),   Not nul,l default= 3
Title: Re: Fatal error : There was an error while processing a database query
Post by: med20 on July 12, 2004, 12:40:56 AM
Thank you very much, that finally pushed me in the right direction.

After making that modification I got the same errors with:
'custom_user_upload'
'num_file_upload'
'num_URI_upload'

I added each field with the same specs then the template came up with this:

FROM cpg11d_categories WHERE parent = ''  ORDER BY pos" on 0

mySQL error: Unknown column 'thumb' in 'field list'


So I added the field 'thumb' to cpg11d_categroies with int(11), not null, and default=3.

That seems to have taken care of it so far, but it makes me wonder if I have the permissions wrong on the mysql database to keep the update script from adding these fields - and if there may be more that I could run into later.

Like: Notice: Undefined index: user_group_list in /home/virtual/loudennis.com/cpg/include/init.inc.php on line 273