@micker opened this Issue on October 19th 2022

after update to 4.12.1
i have this error when i try to create a new site
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'description' in 'field list'
thanks for any help

@feralhawk commented on October 20th 2022

Same issue here when trying to create a new variable in tag manager. Database reupdate did not solve the problem.

@heurteph-ei commented on October 20th 2022
@MatomoForumNotifications commented on October 20th 2022

This issue has been mentioned on Matomo forums. There might be relevant details there:

https://forum.matomo.org/t/facebook-pixel-tag-manager-and-complianz/47927/2

@AltamashShaikh commented on October 21st 2022 Contributor

Hey everyone, Matomo 4.12.2 was released today and should fix the issue.
Closing the issue for now, please let us know here if you are still facing issues after upgrade

@thomasstr commented on October 21st 2022

After update this issue still persists. Also when trying to create triggers in Tag Manager.

@AltamashShaikh commented on October 21st 2022 Contributor

@thomasstr Did you run ./console core:update after the update ?

@thomasstr commented on October 21st 2022

Yes, It ran it through the automatically updater. If I can supply with anything else, let me know.

@AltamashShaikh commented on October 21st 2022 Contributor

Do you have access to your Mysql and command line ?

@thomasstr commented on October 21st 2022

Do you have access to your Mysql and command line ?

Yes I do.

@AltamashShaikh commented on October 21st 2022 Contributor

Do you have access to your Mysql and command line ?

Yes I do.

Please check the version of plugin using this query SELECT * FROM matomo_option where option_name='version_tagmanager'
If the option_value is 4.12.2 update it to 4.11.0 chances are that the update didn't run properly
Next execute this command in your cli ./console core:update and check if it fixes the issue or not

@thomasstr commented on October 21st 2022

It added the columns now. Thanks for the help.

`
./console core:update

*** Update ***

Database Upgrade Required

Your Matomo database is out-of-date, and must be upgraded before you can continue.

The following plugins will be updated: TagManager.

*** Note: this is a Dry Run ***

ALTER TABLE `matomo_tagmanager_tag` ADD COLUMN `description` VARCHAR(1000) NOT NULL DEFAULT '' AFTER `name`;
ALTER TABLE `matomo_tagmanager_trigger` ADD COLUMN `description` VARCHAR(1000) NOT NULL DEFAULT '' AFTER `name`;
ALTER TABLE `matomo_tagmanager_variable` ADD COLUMN `description` VARCHAR(1000) NOT NULL DEFAULT '' AFTER `name`;

*** End of Dry Run ***

A database upgrade is required. Execute update? (y/N) y

Starting the database upgrade process now. This may take a while, so please be patient.

*** Update ***

Database Upgrade Required

Your Matomo database is out-of-date, and must be upgraded before you can continue.

The following plugins will be updated: TagManager.

The database upgrade process may take a while, so please be patient.

Executing ALTER TABLE matomo_tagmanager_tag ADD COLUMN description VARCHAR(1000) NOT NULL DEFAULT '' AFTER name;... Done. [1 / 3]
Executing ALTER TABLE matomo_tagmanager_trigger ADD COLUMN description VARCHAR(1000) NOT NULL DEFAULT '' AFTER name;... Done. [2 / 3]
Executing ALTER TABLE matomo_tagmanager_variable ADD COLUMN description VARCHAR(1000) NOT NULL DEFAULT '' AFTER name;... Done. [3 / 3]

Matomo has been successfully updated!`

@MatomoForumNotifications commented on October 21st 2022

This issue has been mentioned on Matomo forums. There might be relevant details there:

https://forum.matomo.org/t/mysqli-prepare-error-unknown-column-description-in-field-list/47919/7

@develth commented on October 21st 2022

Please check the version of plugin using this query SELECT * FROM matomo_option where option_name='version_tagmanager' If the option_value is 4.12.2 update it to 4.11.0 chances are that the update didn't run properly Next execute this command in your cli ./console core:update and check if it fixes the issue or not

That solved it for now. Thanks!

This Issue was closed on October 21st 2022
Powered by GitHub Issue Mirror