6

Upgrading to the latest version of LiveLinks

  1. DO NOT DELETE your DAP-WP-LiveLinks folder.
  2. DO NOT DISABLE or DE-ACTIVATE the DAP-WP-LiveLinks plugin.
  3. If you wish to make a back up of your existing DAP-WP-LiveLinks folder, DO NOT DO IT in the same folder, as WP will treat it as a duplicate copy of the plugin, and you can have unexpected results. If you wish to take a backup, then download it to your computer, or move it away from the wp-content/plugins/ folder. DO NOT KEEP more than one copy of the LiveLinks plugin files in the wp-content/plugins/ folder
  4. Download the latest version of DAP-WP-LiveLinks.zip from the members area.
  5. Unzip the zip file to your desktop.This will create a folder by name DAP-WP-LiveLinks on your desktop.
  6. Simply Upload the entire DAP-WP-LiveLinks folder (including the folder too) to your WordPress plugins directory (which is wp-content/plugins/). You are essentially over-writing your existing plugin files, that's all.

That's it!

Note: The above ALL-CAPS, that too in RED does not mean we're yelling at you :-). We just want to OVER-EMPHASIZE the importance of the text, that's all.

Click Here to Leave a Comment Below 6 comments
Upgrading to the latest version of DAP — DAP Documentation - October 15, 2010

[…] Upgrading to the latest version of LiveLinks → […]

Reply
JC - June 23, 2011

I upgraded to the DAP 4.1 final and got the following errors:

SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name ‘recurring_discount_amt’
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry ‘PAYPAL_PAYMENT_SUCC’ for key 2
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name ‘price_increment’
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name ‘price_increment_ceil’
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name ‘num_sales’
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name ‘num_days’
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name ‘timed_pricing_start_date’

Can you tell me if this is okay or if something’s wrong? Thanks!

Reply
Veena Prashanth - June 23, 2011

You can ignore the errors. It is reporting these errors because you already have some of these fields in your dap database (maybe you are upgrading to the latest version of 4.1 but you were already on an older version of 4.1 where some of these fields existed). These errors can be ignored.

Reply
JC - June 23, 2011

Thanks. that’s reassuring… although the site seems a little slower than usual after the upgrade. I do have another issue with the form, its not processing or rather it just shows a Please wait… on the submit button but does nothing at all. We’re using authorize.net.

Reply
Veena Prashanth - June 23, 2011

You mean the form is stuck on buy.php where the user enters CC info ? If yes, maybe your did not upload all the dap files correctly. Possible Javascript errors. If you test on Firefox, you can click on the Browser Tools -> Error Console to find any javascript errors.

Download dap 4.1 again from our site and upload it back to your site (overwrite the existing dap scripts).

See if things work ok after that.

Reply
JC - July 8, 2011

Hi Veena,

I upgraded to 4.2 and the form works, I made a test purchase and it went through. I wanted to use the merge tag for the checkout page and also to generate new buttons but when I tried to generate the buy it now button it would not generate. Also, the page is not formatted correctly, it does not have the tabbed menu for:
Paypal Standard
Auth.net & Paypal Pro
1ShoppingCart
ClickBank

instead it shows an unordered list and everything else. And although the payment went through and got added to DAP, I was sent to the buy-submit.php page and does not redirect back to the page I’ve set it to. I need to have this site up ASAP. Thank you so much!

Reply

Leave a Reply: