Hi, I used the documentation to do the update from 1.2.1 to 1.3.2 (backup the albums, the anycontent.php and include/config.inc.php and afterwards running the update.php script)
the update.php script said that everything was okay, but when i clicked on 'Lets continue' i got the error
Fatal error :
There was an error while processing a database query
Anybody has an idea? How can I find this error, cause it is not possible for me to go to admin mode and start changing stuff in there.
If this is not possible, is there a way back to version 1.2.1?
thanks
klaas
Use a tool like phpMyAdmin to turn on debug_mode manually by browsing your coppermine config table and setting the debug_mode value to "1". Make sure you have uploaded all files - use versioncheck.php to find out more.
Joachim
I checked out every file and it seems that everything is changed except for some files which are still the old ones, I mean the files "anycontent.php", include/config.inc.php" and then also a file "include/lock.php" and sql/restore_config.sql"
I putted debug_mode on 1 didn't do anything, just gave the same error and also I looked at versioncheck.php but it gave again the same error.
Is there a way to do the update manually or an install manually in such a way that i don't have to reinsert every picture?
thanks
klaas
I just have taken a look at my mysql dbase and the tables are give by
cpg11d_albums
cg11d_banned
cpg11d_categories
cpg11d_comments
cpg11d_config
cpg11d_ecards
cpg11d_exif
cpg11d_filetypes
cpg11d_pictures
cpg11d_temp_data
cpg11d_usergroups
cpg11d_users
cpg11d_votes
is this okay for the 1.3.2??
turning on debug mode should give you additional info on what query actually fails. Please post the mySQL error message it produces.
Joachim
I turned on debug mode in the file phpinfo.php on line $CONFIG['debug_mode']=1; Or is it somewhere else I have to change this?
klaas
Quote from: GauGau on August 31, 2004, 06:58:54 AM
Use a tool like phpMyAdmin to turn on debug_mode manually by browsing your coppermine config table and setting the debug_mode value to "1"
You need to enable debug mode by going into the database as described above.
Okay that was my fault, just installed the phpMyAdmin thing and here is the error I got after putting debub_mode = 1
Fatal error :
There was an error while processing a database query.
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'
I hope that this is what you meant,
thanks in advance
did you actually run update.php, as suggested in the upgrade instructions within the docs?
Joachim
yes, i did it already 3 times.
I must say that my cpg and the forum (bb2) are in the same database.
so you think i can return to the old copermine without a problem by just copieing the old coppermine over it.
if you ran update.php and the field doesn't exist, your mySQL user probably doesn't have permission to use the ALTER command. Contact your webhost and ask them to grant your mySQL user this privilege. If they deny you having it, come back here, we'll find a workaround then (by creating a dump of that table, dropping the table, modifying the queries and restoring the modified table.
Joachim
Okay I will contact him (he is on a conference now) and I will keep you up2date.
Thanks a lot
klaas
Okay the webadmin didn't gave me authorization to use the ALTER command, (its for security reasons which I understand) so I asked him to give the user ALTER acces and that he does the update and then changes the ALTER again. Well to make it short it works.
So thanks for all the effort
coppermine still rocks!
Although it's good to hear that it works for you now, I don't think this solution really makes sense: denying you permanent ALTER permissions is silly if you have DELETE and UPDATE permissions, doesn't make things more or less secure, but will keep you from adequately using your database. I suggest you talk this over with your webhost, who you seem to know personally.
Joachim