Announcement:Materials and articles for ProductCart 5 can be found at our brand new support center.

Create an account to edit articles | See Formatting Syntax for Wiki syntax | We look forward to your contribution!

ProductCart v4 - Patch #2

Overview

This patch was released on 11/09/09. It addresses a few issues found in ProductCart v4.0 between 11/04/09 and 11/09/09. See the section below for details on which files were updated.

Do you need it?

  • If the zip file that you received when installing ProductCart v4 or to upgrade to v4 contains the date 110309, then this patch is for you.
  • If the zip file contains a later date, you do not need this patch.
  • If you ordered ProductCart or a ProductCart upgrade after 11.09.09, then you do not need this patch (confirm by looking at the date that is part of the ZIP file name that you downloaded).

Do you also need Patch #1?

Before applying Patch #2, see if you also need to apply patch #1. If you do, first apply Patch #1, then Patch #2. They both contain only a handful of files, so the FTP process only takes a few moments.

Updated Files

pc/ (23 files)

  • 404b.asp
    Added validation to prevent a transfer error when the Keyword Rich URLs feature has been turned on, but the 404 Error Page location has been incorrectly entered.
  • CustOrdInvoice.asp, CustViewPastD.asp
    Fixed issue related to orders placed prior to the upgrade to version 4, where is some cases the shipping address was incorrectly shown as the same as the billing address even if that was not the case. This did not affect orders placed after the version 4 upgrade.
  • gwProtx.asp
    Updated URLs used in the connection to the payment gateway (now “SagePay”, formerly “ProtX”)
  • All files starting with “opc_…”
    Fixed a character encoding issue that affected the way “One Page Checkout” handled special characters.
  • pcUPSTimeInTransit.asp
    Fixed issue with encrypted source code not being decoded properly.
  • prv_incshow.asp
    Fixed date formatting issue.

The file 404b.asp is overwritten by this patch. This should not affect any stores since this file does not need to be edited in version 4. However, if you manually edited the file to hardcode the location of your “404 - Page Not Found” page, go to Settings > Store Settings > Miscellaneous, turn on the Keyword Rich URls feature (if not already on) and enter the path to the file (e.g. ”/my404page.html”). You do not need to manually edit 404b.asp.

pcadmin/ (12 files)

  • AdminSettings.asp
    Fixed issue related to the detection of the Web server readiness to use keyword rich URLs. In some cases the test failed even if the Web server was indeed ready to use the feature.
  • adminaddfeedback.asp, adminviewallmsgs.asp
    Fixed issue with Help Desk not automatically selecting the order number for which a new Help Desk message was being posted. Instead, the first order in the drop-down was incorrectly being selected.
  • BatchPrint.asp
    Fixed issues related to the fact that the code had not been properly updated for v4.
  • delPrdAddImg.asp
    Minor code change. Edited the file name used in a redirect.
  • exportFroogle.asp, exportCashBack.asp
    In the Google Base and Microsoft Bing cashback data feed generation feature, when a product did not have an image specified for it, the link to the image of the previous product was used due to a variable not being reset. Now no image link is included.
  • menu.asp
    Fixed minor issue with sales chart overflowing the allotted space in some cases (now a scroll bar is shown).
  • ordInvoice.asp
    Fixed issue related to orders placed prior to the upgrade to version 4, where is some cases the shipping address was incorrectly shown as the same as the billing address even if that was not the case. This did not affect orders placed after the version 4 upgrade.
  • processOrder.asp
    Fixed issue when changing the shipping address for an order that previously used the same address for shipping and billing. A flag in the database was not properly being reset, and some pages still showed shipping address = billing.
  • prv_ManageRevPrds.asp
    Fixed date formatting issue.
  • sds_ShipOrderWizard3.asp
    Minor interface change (“success” message was using wrong CSS class).

Performing the update

Which files you need

If you are using…

  • A store without the Apparel Add-on: use the “Stores without Apparel Add-on” folder
  • A store with the Apparel Add-on: use the “Stores with Apparel Add-on” folder

If you are also using…

  • MailUp: Upload whichever files apply to your store (see above), then download the latest MailUp integration files and upload them to the corresponding folders as per the Add-on instructions.
  • Conflict Management Add-on: a separate file set is not needed
  • Synchronizer for QuickBooks: a separate file set is not needed
  • eBay Add-on: a separate file set is not needed

Other notes

  • You do not need to backup the database. The database will not be updated.
  • Always turn off your store before uploading the files. Turn it back on after the files have all been transferred successfully.

Uploading the updated files

Upload the files to their respective folders, overwriting the existing files.

  • Matching folders
    For instance, you will update the contents of the pc subfolder on your Web server with the files contained in the pc subfolder that is part of this patch.
  • pcadmin folder
    The pcadmin folder has likely been renamed on your store (if not, you should rename it). Rename the pcadmin folder in the update files locally on your computer so that when you FTP the files there is no chance that a new pcadmin folder is created, which would mean that some of your store files are not being updated.
  • Do not delete
    Do not delete any of the files that are currently on your Web server.
  • Confirm successful transfer
    FTP transfers sometimes fail. Make sure that once the process has finished, your FTP client reported a success message. Most FTP programs have a way to show you whether some files were not uploaded successfully. If that happens, make sure to upload them again until all files have been uploaded successfully. For example, Filezilla separately reports “Failed Transfers” and “Successful Transfers”. The “Failed Transfers” tab should be empty.

QR Code
QR Code ProductCart v4 - Patch #2 (generated for current page)