CiviCRM Community Forums (archive)

I resolved the database issue blocking 1.9 > 2.0 in yesterday's post concerning FK error and missing civcrm_acl table. The Step Four process stated "shell > mysqldump -u crm_db_username -pcrm_db_password -c -e -n -t civicrm19 > dumpFile"

mysql/databases are unique to each site, we know that. I skipped using the options, (-c -e -n -t) and that did it. although the contribution_import table refused to be imported from civicrm_41, I had to manually add it from another database we have.

URGENT QUESTION THOUGH....

Getting errors on payment pages asking for the "API URL". In the Payment Processor settings page, where we have Paypal Pro chose, "API URL" is nowhere. I tried setting mode as "paypal express" and "paypal standard", no "API URL".   

rather odd.

kindly advise.

douglas

THANK YOU FOR QUICK REPLY! WE HAVE 18 PAYMENT PAGES.

So the fix is to run this sql query on the civicrm_payment_processor_type table? I tried and got this error. Below is fix and error I got.

--------------------------------------------------------------------------------------


FIX:   This is a bug in the upgrade script and we'll fix for 2.0.4

the relevant issue is here: http://issues.civicrm.org/jira/browse/CRM-3142

the diff is here: http://biryani.osuosl.org:8181/browse/CiviCRM/branches/v2.0/CRM/Upgrade/TwoZero/sql/others.mysql?r1=14189&r2=14625

(i..e u need to execute those two sql lines in the db)

---------------------------------

Error
SQL query:

ADD `url_api_default` varchar( 255 ) NULL DEFAULT NULL COMMENT '' COLLATE utf8_unicode_ci AFTER url_site_default, ADD `url_api_test_default` varchar( 255 ) NULL DEFAULT NULL COMMENT '' COLLATE utf8_unicode_ci AFTER url_site_test_default

MySQL said: 

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ADD `url_api_default` varchar(255) NULL DEFAULT NULL COMMENT '' COLLATE utf8_uni' at line 1

---------------------------------------------------------------------------------------

yes. you're right. tried wrong part of code. thanks dave. site is fully upgraded to 2.0.

douglas

Nevermind... after it was added to the database, you then need to go into the settings page for the Paypal processor and set the API URLs there. Then it works fine.