Notice: unserialize(): Error at offset OC Version 3.0.3.6

I am hoping someone will be able to point me in the right direction.
I am getting this error
Notice: unserialize(): Error at offset 0 of 30 bytes in store/system/library/cw/SagePayCw/SettingApi.php on line 207

when I try to edit extension> module > opayo base module
Similarly, when customers choose the credit option to make a payment on checkout, this error is displayed. (SagePay is now Opayo)

I have gone through previous threads and the solution seems to be on making changes to the "settings table".
I believe this is no longer used in 3.0.3.x and above.

What can I do?

There's no system/library/cw/SagePayCw/SettingApi.php file in default OC installation. Contact extension developer and ask him to solve the issue.

Thank you. I understand this and I have already contacted them. They won't be available until Monday. I am just looking for a direction I can try out myself. Previous and similar errors in the past have been resolved by making changes in the "settings table" what is the equivalent of this in the newer version of OpenCart.

psjrules wrote: ↑

Sun Nov 01, 2020 12:57 am

Thank you. I understand this and I have already contacted them. They won't be available until Monday. I am just looking for a direction I can try out myself. Previous and similar errors in the past have been resolved by making changes in the "settings table" what is the equivalent of this in the newer version of OpenCart.

If you're looking for a direction you can try out yourself, then you do not need to ask the forum about this issue.

How can one learn if experts can't point upcoming developers in right direction. I am sure there are one or two things that can be tried. I'd spent the whole day looking. A gentle nudge in right place and it will be done. Thanks anyway for your response.

Your best bet is to google the error, wait for the module support or hire a developer.

Sounds more like corrupted data. Plenty of stackoverflow info on what can cause this error and things you can try.

sw!tch wrote: ↑

Sun Nov 01, 2020 5:28 am

Your best bet is to google the error, wait for the module support or hire a developer.

Sounds more like corrupted data. Plenty of stackoverflow info on what can cause this error and things you can try.

Thank you. Trust me, when it comes to researching stuff like this, I am not lazy. I have googled but most resolutions are on an earlier version of opencart and not version 3.0.3.x or higher. Changes to the oc_settings table seem to be where the changes to be done to fix the error. I simply can't figure the equivalent of the table in the newer versions. I can't find the table.

psjrules wrote: ↑

Sun Nov 01, 2020 5:59 am

Thank you. Trust me, when it comes to researching stuff like this, I am not lazy. I have googled but most resolutions are on an earlier version of opencart and not version 3.0.3.x or higher. Changes to the oc_settings table seem to be where the changes to be done to fix the error. I simply can't figure the equivalent of the table in the newer versions. I can't find the table.

This is when you wait for Monday, when developer is available. Have a nice weekend.

psjrules wrote: ↑

Sat Oct 31, 2020 11:01 pm

I have gone through previous threads and the solution seems to be on making changes to the "settings table".

It sounds like the data in your settings table may have been corrupted but if you're not a developer it really would be best to wait until the extension developer can take a look or you risk really messing things up.