• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space

Update error 3.7.1

Status
Not open for further replies.

evilmoe2

Not needed
Hello,

I getting a error doing the update:
SQLSTATE[42000]: Syntax error or access violation: 1072 Key column 'like_content_user_id' doesn't exist in table

Before I got a error I have to run a SQL command on my own:

DROP TRIGGER IF EXISTS `album_insert`;
DROP TRIGGER IF EXISTS `album_delete`;
DROP TRIGGER IF EXISTS `follow_insert`;
DROP TRIGGER IF EXISTS `follow_delete`;
DROP TRIGGER IF EXISTS `image_insert`;
DROP TRIGGER IF EXISTS `image_update`;
DROP TRIGGER IF EXISTS `image_delete`;
DROP TRIGGER IF EXISTS `notification_insert`;
DROP TRIGGER IF EXISTS `notification_update`;
DROP TRIGGER IF EXISTS `like_insert`;
DROP TRIGGER IF EXISTS `like_delete`;
DROP TRIGGER IF EXISTS `notification_delete`;
DROP TRIGGER IF EXISTS `user_insert`;
DROP TRIGGER IF EXISTS `user_delete`;
 
Make sure your server isn't caching the install folder, otherwise you will need to do a manual install.
 
Then I do get the following error:

Make sure that the current database user DBUSER has ALL PRIVILEGES granted over the DBNAME table.


EDIT: The Databaseuser has all privilegs for this db
 
After refreshing I get again this error:

SQLSTATE[42000]: Syntax error or access violation: 1072 Key column 'like_content_user_id' doesn't exist in table
 
Debug shows this:

Code:
ALTER TABLE `chv_likes` ADD INDEX `like_content_user_id` (`like_content_user_id`);
ALTER TABLE `chv_notifications` ADD INDEX `notification_date_gmt` (`notification_date_gmt`);
ALTER TABLE `chv_notifications` ADD INDEX `notification_trigger_user_id` (`notification_trigger_user_id`);
UPDATE `chv_settings` SET `setting_value` = "3.7.1" WHERE `setting_name` = "chevereto_version_installed";

So run this before:
Code:
ALTER TABLE `chv_likes` ADD `like_content_user_id` bigint(32) DEFAULT NULL;
ALTER TABLE `chv_notifications` ADD `notification_trigger_user_id` bigint(32) DEFAULT NULL;

It is very odd that you didn't have that column, it was added in v3.7.0
 
Last edited:
I ran into same issue odd.

mysql> ALTER TABLE `chv_notifications` ADD INDEX `notification_date_gmt` (`notification_date_gmt`);
ERROR 1061 (42000): Duplicate key name 'notification_date_gmt'
mysql> ALTER TABLE `chv_notifications` ADD INDEX `notification_trigger_user_id` (`notification_trigger_user_id`);
ERROR 1072 (42000): Key column 'notification_trigger_user_id' doesn't exist in table
 
I executed this now:
Code:
ALTER TABLE `chv_likes` ADD `like_content_user_id` bigint(32) DEFAULT NULL;

But I still get thise error:
Code:
SQLSTATE[42000]: Syntax error or access violation: 1072 Key column 'notification_trigger_user_id' doesn't exist in table
 
Is the same old stuff, you are missing columns. Now you are missing notification_trigger_user_id. The only possible way to have those errors is that you used "bad" 3.7.0.
 
I always used the auto updater. I never did "a dirty workaround".
Do you have the missing columns for me to fix the issue?
 
There was a deprecated v3.7.0 because of the unsupported MySQL triggers in most servers out there. So I removed that "bad" version and replaced it with another one not based in triggers at all. That's why you are having issues.

By the way, I was about to issue the missing queries but it seems that you deleted my test account.
 
Would´t it be better way to release a update as a new version if this outdated?

Nope. Soon as I released the "bad" version I told everyone to rollback with specific instructions. Some users didn't rollback and I warned that such action will have problems in the future. v3.7.0 (bad) was totally wiped out of the official releases because it wasn't usable so it got recalled.
 
Status
Not open for further replies.
Back
Top