News:

Support the VirtueMart project and become a member

Main Menu

Can't edit payment method in BE

Started by patbe60, October 28, 2025, 17:14:10 PM

Previous topic - Next topic

patbe60

When I try to edit a payment method in BE I get the following error:

An error has occurred.

    1054 Unknown column 'Array' in 'WHERE'

I can create new payment methods. But after saving them I get this error:

info
Payment Method successfully saved
An error has occurred.

    1054 Unknown column 'Array' in 'where clause'

J 5.4.0
VM 4.6

patbe60

#1
I made some tests: It works with the following methods (editing and creating):

klarna
paypal
amazon
opctracking
opc_shipping_last
authorizenet

All other methods end in the above described error. Also older paypal method can't be edited.

Milbo

I thank you very much for this detailed bug report. I check it out.
Should I fix your bug, please support the VirtueMart project and become a member
______________________________________
Extensions approved by the core team: http://extensions.virtuemart.net/

Milbo

Hmmm, but I cannot reproduce it. Maybe the problem lies in a non core plugin? For example this opctracking? Maybe that interferes.
Should I fix your bug, please support the VirtueMart project and become a member
______________________________________
Extensions approved by the core team: http://extensions.virtuemart.net/

patbe60

Okay, I finally found the error in the virtuemart_vendors table. It works fine again.

Milbo

okey, ehrm, what was the error in the virtuemart_vendors table?
Should I fix your bug, please support the VirtueMart project and become a member
______________________________________
Extensions approved by the core team: http://extensions.virtuemart.net/

patbe60

It wouldn't have been necessary to check the database. The error was that there was no value in shop -> vendor tab -> List of accepted currencies.

This leaded to a wrong value in the table in vendor_accepted_currencies: "Array" instead of a currency ID (in my case swiss francs - ID = 27).

I don't know, why this field wasn't filled in any longer. As you know I'm using VM since years without this problem.