Error adding attribute to product in J4

[spotlinks]

Hello. I'm using J4.4.13 and Phoca Cart v4.0.6
When trying to add attribute to a product, I am getting the following:

error 1054 Unknown column 'published' in 'field list'

I have tried installing Phoca Cart v4.0.11 and get an installation error. (both images of errors linked below). Phoca Cart was installed with the Electronics Store template. I don't see any debug info when error is up.

Any help would greatly be appreciated. Thanks!

https://imgur.com/a/wjhIIIK

[Jan]

Hi, you should check if your installation was correct in database. Somewhere in some table, the published field is missing, unfortunately in your screenshot, the line of attribute library file where the query is located is cut, so the number of the line is not there. So it is hard to say which table this is.

Jan

[spotlinks]

Hi Jan,

I have tried re-installing the core files and checked/repaired the database, but don't even know where to look. This error is beyond my understanding and I am scared to experiment with this database, as it has hundreds of items already successfully listed in it. We only have a couple of items that will have attributes and I hate to do a workaround and list the attributes as separate items.

This is the db that comes with the free "Electronics" template and none of the demo items use attributes. I have a more complete screenshot here: https://imgur.com/a/pYylIif

Thanks so much for your help.

[Jan]

Are you sure, the table #__phocacart_attribute_values has published column in your database?



The published column is a part of this table since version 4.0.8:
administrator/components/com_phocacart/update/sql/mysql/4.0.8.sql

Jan

[spotlinks]

I have tried installing the update v4.0.11 and cannot get it to install.
Here is the error message I'm getting: https://imgur.com/a/MBpyZnO

I'm hesitant to manually mess with the database, but keep getting stopped at every step here. I appreciate your guidance on this.

[spotlinks]

Okay, I manually got the database updated for the 4.0.8.sql file and the issue has disappeared. But I'm concerned about getting the rest of that update into the system. Should I try again? Or will that complicate matters?