Page 1 of 1

Error msg after update to 2.0.370

PostPosted: Fri Oct 12, 2018 6:33 am
by Candy.Yang
Hello,

I have just update RuposTel OPC from 2.0.348.210917 to latest version.
I get 1054 Unknown column 'c.state' in 'field list' in OPC backend and VM control panel. (however, VM product panel is still good.)
There's no error msg before I updated, and if I disable "System - RuposTel One Page Checkout Master Plugin (OPC)", everything back to normal again.

The environment:
Joomla 3.8.13
VM 3.4.2
PHP 7.0.32

Do you know what causes the issue? Thank you.

Re: Error msg after update to 2.0.370

PostPosted: Thu Oct 25, 2018 12:41 pm
by admin
hello, i checked my demo install for keyword search "c.state" and it's available in 2 extensions:
- awo coupons
- com_finder

since opc loads awocoupons if it's used, the issue may be there - maybe your awo tables are not properly updated and thus you may want to update awo to get it working properly.

for com_finder you may want to check "database" section in extentensions at joomla menu to see if your joomla's DB tables are all OK.

i believe you can get this working by disabling all awo plugins, or updating them which should update the table structures as well.

best regards, stan

Re: Error msg after update to 2.0.370

PostPosted: Mon Nov 26, 2018 11:34 am
by mile2
Hi,
I did all of this and still got an error: 1054 Unknown column 'c.state' in 'field list'
This error is on the front of the website and on the back under components-one page checkout

Re: Error msg after update to 2.0.370

PostPosted: Wed Nov 28, 2018 1:20 pm
by mile2
When i disable this plugin everything is working:

System - RuposTel One Page Checkout Master Plugin (OPC)

What can be the problem?

Re: Error msg after update to 2.0.370

PostPosted: Wed Nov 28, 2018 1:25 pm
by admin
hello, "c.state" is not part of any opc file, or any opc extension and thus this error is triggered from some other part of the sytem.

i suggest to check Joomla's database schema state at joomla backend and see if you can "fix db structure" per latest DB scheme of your installed joomla.

if it still gives an error then you may want to install our "fatal catcher" plugin + configure your email there + enable it and reproduce the error to see which part of the code triggers the error. (when xdebug is available, this will also provide a full backtrace)

best regards, stan