I am running Joomla 3.4.5 and Virtuemart 3.0.10. I try to create a paypal payment and it won't allow me to save it. It just sits there, without an error message on this screen.
When checking to make sure all my extensions are up to date, I see the following warning and I'm not sure if this is my problem or not.
Warning
Update: Could not open update site #18 "VirtueMart3 plg_vmpayment_skrill Update Site", URL: http://virtuemart.net/releases/vm3/plg_vmpayment_skrill_update.xml
How do I resolve this so I can save payment and shipment options?
skrill has nothing to do with it
One thing I have seen is Save sometimes not working in Chrome after an update
Perhaps restart the browser and clear cache
Check browser console for JS errors
I assume both methods are enabled in Joomla plugins?
I am using internet explorer - I cleared the cache and restarted it same thing. I also tried using Firefox as well.
I will only be using Paypal, and have that plug in enabled. I even tried to enable all payment types to see if I could have any payments type save, without luck. For the shipping, I have VM Shipment - By weight, ZIP and countries enabled and no luck saving shipping either.
I opened the page in Firefox and used Firebug. When I click on Console/errors....I get
ReferenceError: Joomla is not defined
Any thoughts?
are u using the standard Joomla Isis admin template?
I have tried using the templates that come when you install joomla and it won't work either. Ultimately I want to use I the Blue Seas template but will use anything to get it setup.
I just tried ISIS and it worked!!!! Thank you!!!
man oh man ... note for future.. as well as ask for the info they never give now, also ask what admin template they use..
Why can't you guys leave your sticky fingers out of the machinery and get on with making simple fast successful websites? :-\
I am in the same boat except I get 1075 errors for both payments and shipments. I am building a new site to replace my existing "old" site and am using xampp 1.8.2, Joomla 3.4.5, VM 3.0.10 with the ISIS admin template and the Captiva template from Joomla Designs. This is a clean install with the quickstart data being loaded.
I first noticed problems when I updated from VM 3.0.9 to 3.0.10 and the standard payment plug didn't load with the AIO because the PRIMARY KEY wasn't listed in the SQL. I manually loaded it, as suggested in another post with PHPMy Admin. I have also loaded 2 new extensions, the JCE editor and Shipping By Rules Advanced from Open Tools. I have added nothing else.
So here are the errors I get when I click on "Save" or "Save and Close". First is the Payments trying to save either PayPal or standard:
Incorrect table definition; there can be only one auto column and it must be defined as a key SQL=CREATE TABLE IF NOT EXISTS `zX19_virtuemart_payment_plg_paypal` ( `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT, `virtuemart_order_id` int(1) UNSIGNED, `order_number` char(64), `virtuemart_paymentmethod_id` mediumint(1) UNSIGNED, `payment_name` varchar(5000), `payment_order_total` decimal(15,5) NOT NULL, `payment_currency` smallint(1), `email_currency` smallint(1), `cost_per_transaction` decimal(10,2), `cost_percent_total` decimal(10,2), `tax_id` smallint(1), `paypal_custom` varchar(255), `paypal_method` varchar(200), `paypal_response_mc_gross` decimal(10,2), `paypal_response_mc_currency` char(10), `paypal_response_invoice` char(32), `paypal_response_protection_eligibility` char(128), `paypal_response_payer_id` char(13), `paypal_response_tax` decimal(10,2), `paypal_response_payment_date` char(28), `paypal_response_payment_status` char(50), `paypal_response_pending_reason` char(50), `paypal_response_mc_fee` decimal(10,2), `paypal_response_payer_email` char(128), `paypal_response_last_name` char(64), `paypal_response_first_name` char(64), `paypal_response_business` char(128), `paypal_response_receiver_email` char(128), `paypal_response_transaction_subject` char(128), `paypal_response_residence_country` char(2), `paypal_response_txn_id` char(32), `paypal_response_txn_type` char(32), `paypal_response_parent_txn_id` char(32), `paypal_response_case_creation_date` char(32), `paypal_response_case_id` char(32), `paypal_response_case_type` char(32), `paypal_response_reason_code` char(32), `paypalresponse_raw` varchar(512), `paypal_fullresponse` text, `created_on` datetime NOT NULL default '0000-00-00 00:00:00', `created_by` int(11) NOT NULL DEFAULT '0', `modified_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `modified_by` int(11) NOT NULL DEFAULT '0', `locked_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `locked_by` int(11) NOT NULL DEFAULT '0') ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
Next is Shipping:
Incorrect table definition; there can be only one auto column and it must be defined as a key SQL=CREATE TABLE IF NOT EXISTS `zX19_virtuemart_shipment_plg_rules_shipping_advanced` ( `id` int(1) UNSIGNED NOT NULL AUTO_INCREMENT, `virtuemart_order_id` int(11) UNSIGNED, `order_number` char(32), `virtuemart_shipmentmethod_id` mediumint(1) UNSIGNED, `shipment_name` varchar(5000), `rule_name` varchar(500), `order_weight` decimal(10,4), `order_articles` int(1), `order_products` int(1), `shipment_weight_unit` char(3) DEFAULT 'KG', `shipment_cost` decimal(10,2), `tax_id` smallint(1), `created_on` datetime NOT NULL default '0000-00-00 00:00:00', `created_by` int(11) NOT NULL DEFAULT '0', `modified_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `modified_by` int(11) NOT NULL DEFAULT '0', `locked_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `locked_by` int(11) NOT NULL DEFAULT '0') ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
The tables are created in the database and the data is saved in paymentmethods and shippingmethods but I get these errors everytime I try to make adjustments or changes.
What do I need to look for to correct this?
Thanks.
Did u update your AIO to 3.0.10 (3.0.12 is also now the current release .. test on a copy)
if so try the VM admin-> tools -> Install or if necessary update tables
I did all of the things you mentioned several times hoping to make it work. I even went backwards and installed 3.0.8 and updated through 3.0.10 again, including each AIO. I also did the tcPDF. Since its not a live site yet I'll try the .12.
Thanks
Ok. I updated to VM3.0.12 through the joomla installer. Just as in the 3.0.10 AIO update I got the following error for the same plugin, the standard payment plugin.
Warning
Incorrect table definition; there can be only one auto column and it must be defined as a key SQL=CREATE TABLE IF NOT EXISTS `zX19_virtuemart_payment_plg_standard` ( `id` int(1) UNSIGNED NOT NULL AUTO_INCREMENT, `virtuemart_order_id` int(1) UNSIGNED, `order_number` char(64), `virtuemart_paymentmethod_id` mediumint(1) UNSIGNED, `payment_name` varchar(5000), `payment_order_total` decimal(15,5) NOT NULL DEFAULT '0.00000', `payment_currency` char(3), `email_currency` char(3), `cost_per_transaction` decimal(10,2), `cost_min_transaction` decimal(10,2), `cost_percent_total` decimal(10,2), `tax_id` smallint(1), `created_on` datetime NOT NULL default '0000-00-00 00:00:00', `created_by` int(11) NOT NULL DEFAULT '0', `modified_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `modified_by` int(11) NOT NULL DEFAULT '0', `locked_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `locked_by` int(11) NOT NULL DEFAULT '0') ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
I can go ahead and run this through PHPMyAdmin and put in the PRIMARY KEY statement but that doesn't help me diagnose the problem.
Still throwing the 1075 errors in payments and shipping.
I've seen lots of similar posts from the past couple of years about the incorrect table definition, including from Milbo and Jenkin Hill, but I haven't yet found a resolution. Any thoughts?
For some reason, it does not add the Primary Keys, I have no clue, why
Milbo.
Thanks for your reply. I set up a completely clean install using the Captiva quickstart package. I wanted to test the original package against the updates. The original is built in J3.4.1 and VM 3.0.8 with K2 as an extension. Once installed I tested the shipments and the payments. I could edit and make changes without any problem.
I next loaded another clean installation of the same package and used the update features of joomla to update to J3.4.5 and VM 3.0.12. As always, the joomla update and the VM core updates went without a problem. As in the 3.0.10 AIO update though, the 3.0.12 AIO gave me the 1075 error code for the standard payment plugin. I manually updated it. I then tested the shipping and payments with the same 1075 error codes coming up on everything I tried to edit.
Somewhere between VM 3.0.8 and VM 3.0.10 something changed in the shipping and payments backend, I presume.
Any guidance would be appreciated.
As no one else reports this the obvious suspect is this quickstart thing.. why use it?
Install joomla, install VM, install your template.. job done
I even would say, use our fullinstaller and yes it seems to reasoned in your quickstarter Captiva. But I wonder myself how it makes trouble.