jochar Posted February 11, 2005 Report Share Posted February 11, 2005 Folgende Fehlermeldung bekomme ich beim Abschluss des BEstellvorgangs und kann mir da keinen Reim drauf machen: 1054 - Unknown column 'customers_vat_id' in 'field list' insert into orders (customers_id, customers_name, customers_cid, customers_vat_id, customers_company, customers_status, customers_status_name, customers_status_image, customers_status_discount, customers_street_address, customers_suburb, customers_city, customers_postcode, customers_state, customers_country, customers_telephone, customers_email_address, customers_address_format_id, delivery_name, delivery_company, delivery_street_address, delivery_suburb, delivery_city, delivery_postcode, delivery_state, delivery_country, delivery_address_format_id, billing_name, billing_company, billing_street_address, billing_suburb, billing_city, billing_postcode, billing_state, billing_country, billing_address_format_id, payment_method, payment_class, shipping_method, shipping_class, cc_type, cc_owner, cc_number, cc_expires, cc_start, cc_cvv, cc_issue, date_purchased, orders_status, currency, currency_value, customers_ip, language, comments) *** Hier folgen dann die eingegebenen pers. Daten des Bestellers) [XT SQL Error] Link to comment Share on other sites More sharing options...
RDS Posted February 12, 2005 Report Share Posted February 12, 2005 Originally posted by jochar@Feb 11 2005, 09:49 AM Folgende Fehlermeldung bekomme ich beim Abschluss des BEstellvorgangs und kann mir da keinen Reim drauf machen: Hallo, das liest sich wie ein Datenbankfehler. Hast Du eine? J?rgen Link to comment Share on other sites More sharing options...
HomDau Posted February 15, 2005 Report Share Posted February 15, 2005 Hallo, Das ist ein Datenbankfehler. Kontrolliere deine Datenbank mit phpmyadmin Table "orders" eintr?ge kontrollieren Tabelle customers_vat_id varchar(20) Nein hinzuf?hgen. dann m?sste es klappen. ciao Christian Link to comment Share on other sites More sharing options...
jochar Posted February 15, 2005 Author Report Share Posted February 15, 2005 Sorry, hatte vergessen zu erw?hnen, dass das Problem schon lange behoben ist. Es war in der Tat ein Datenbankproblem (ausgel?st durch menschliches Versagen beim Update V2 -> V3) :stupid: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.