| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| primer:errors [2012/09/13 00:52] – fixing links foxybrett | primer:errors [2019/11/05 13:49] (current) – [What They Are] marija |
|---|
| ====== Errors, and What To Do About Them ====== | ====== Errors, and What To Do About Them ====== |
| |
| If you are have a website, you likely will have problems arise with your site. If you have an e-commerce site, those problems may impact your ability to do sales. There are no perfect systems, but it is important to understand the errors that are common and expected, as well as signs that an error might be more serious. This section of the //FoxyCart E-Commerce Primer for Everybody// will focus mainly on errors you will almost definitely see. | If you have a website, you likely will have problems arise with your site. If you have an e-commerce site, those problems may impact your ability to do sales. There are no perfect systems, but it is important to understand the errors that are common and expected, as well as signs that an error might be more serious. This section of the //FoxyCart E-Commerce Primer for Everybody// will focus mainly on errors you will almost definitely see. |
| |
| ===== Gateway Errors ===== | ===== Gateway Errors ===== |
| In this case, Googling finds us [[http://www.zen-cart.com/forum/showthread.php?t=82393|this page]], explaining that AmEx and Discover cards aren't accepted using a Canadian PayPal Payments Pro. (Oddly enough, that ''10558'' error isn't on the previously linked PayPal documentation page, but Google to the rescue.) | In this case, Googling finds us [[http://www.zen-cart.com/forum/showthread.php?t=82393|this page]], explaining that AmEx and Discover cards aren't accepted using a Canadian PayPal Payments Pro. (Oddly enough, that ''10558'' error isn't on the previously linked PayPal documentation page, but Google to the rescue.) |
| |
| The gateway errors you see in your store error log will no doubt be different than the examples above, but most likely they will accurate describe errors. | The gateway errors you see in your store error log will no doubt be different than the examples above, but most likely they will accurately describe errors. |
| |
| ==== What Might Be Serious ==== | ==== What Might Be Serious ==== |
| [[http://www.foxycart.com/features/feature/integration/datafeeds|See this page]] for more information on the datafeeds. | [[http://www.foxycart.com/features/feature/integration/datafeeds|See this page]] for more information on the datafeeds. |
| |
| <WRAP center round info 60%> | <WRAP center round info 90%> |
| An important thing to note with datafeed errors is that although the datafeed failed to process for the relevant transaction, the actual transaction itself still would have processed successfully, meaning that the customer would have still seen their receipt (although they may not have received a receipt email if you're sending that from your datafeed endpoint), and the customer would have been successfully charged for their order. On the other side though, part or all of the functionality in your datafeed endpoint may not have completed successfully. | An important thing to note with datafeed errors is that although the datafeed failed to process for the relevant transaction, the actual transaction itself still would have processed successfully, meaning that the customer would have still seen their receipt (although they may not have received a receipt email if you're sending that from your datafeed endpoint), and the customer would have been successfully charged for their order. On the other side though, part or all of the functionality in your datafeed endpoint may not have completed successfully. |
| </WRAP> | </WRAP> |
| |
| | <WRAP center round info 90%> |
| | If you're using our other webhooks, we don't expect a response of 'foxy', just a 200 HTTP Response Code. |
| | </WRAP> |
| |
| ==== What They Look Like ==== | ==== What They Look Like ==== |
| <blockquote>DataFeed Failed: (TRANSACTION_ID) 0000-00-00 00:00:00 ERROR_MESSAGE [HTTP_RESPONSE_CODE]</blockquote> | <blockquote>DataFeed Failed: (TRANSACTION_ID) 0000-00-00 00:00:00 ERROR_MESSAGE [HTTP_RESPONSE_CODE]</blockquote> |
| |
| While note all pieces may be present in a given error message, that is the general makeup. The Transaction ID will be present for all transaction based datafeed failures to show you which transaction it relates to specifically. The error message will generally give you an idea of what exactly went wrong, and where it doesn't, you can glean some specific server based information by the HTTP response code that was returned. If your endpoint fails with an error message of it's own, this will be carried through into the error log in the administration - allowing you to find out what's going wrong easier. For information on HTTP response codes, [[http://en.wikipedia.org/wiki/List_of_HTTP_status_codes|Wikipedia is your friend]]. | While not all pieces may be present in a given error message, that is the general makeup. The Transaction ID will be present for all transaction based datafeed failures to show you which transaction it relates to specifically. The error message will generally give you an idea of what exactly went wrong, and where it doesn't, you can glean some specific server based information by the HTTP response code that was returned. If your endpoint fails with an error message of it's own, this will be carried through into the error log in the administration - allowing you to find out what's going wrong easier. For information on HTTP response codes, [[http://en.wikipedia.org/wiki/List_of_HTTP_status_codes|Wikipedia is your friend]]. |
| |
| === Some common error messages === | === Some common error messages === |
| **Endpoint Error** | **Endpoint Error** |
| <blockquote>DataFeed Failed: (123456) 0000-00-00 00:00:00 Datafeed Returned: <br /> <b>Parse error</b>: syntax error, unexpected '=' in <b>/foxycart/datafeed.php</b> on line <b>16</b><br /></blockquote> | <blockquote>DataFeed Failed: (123456) 0000-00-00 00:00:00 Datafeed Returned: <br /> <b>Parse error</b>: syntax error, unexpected '=' in <b>/foxycart/datafeed.php</b> on line <b>16</b><br /></blockquote> |
| This type of error shows that your endpoint is being reached successfully, but the actual endpoint is breaking somewhere in it's execution. Generally the error message here will be a good indicator of what might be going awry, but for in depth debugging, we recommend doing some local testing with the [[:integration|scripts found here]] | This type of error shows that your endpoint is being reached successfully, but the actual endpoint is breaking somewhere in its execution. Generally the error message here will be a good indicator of what might be going awry, but for in depth debugging, we recommend doing some local testing with the [[:integration|scripts found here]] |
| |
| **Taking Too Long** | **Taking Too Long** |
| Shipping errors occur when a customer's address (as entered on the checkout) doesn't return any shipping options. This generally occurs if a store is using live shipping rates (from UPS, USPS, FedEx, etc.) but hasn't selected enough options. For example, if Ground is the only method selected and a customer attempts to order from a different country or continent (or Alaska or Hawaii) then the customer would see a shipping error like "No Shipping Options Available". | Shipping errors occur when a customer's address (as entered on the checkout) doesn't return any shipping options. This generally occurs if a store is using live shipping rates (from UPS, USPS, FedEx, etc.) but hasn't selected enough options. For example, if Ground is the only method selected and a customer attempts to order from a different country or continent (or Alaska or Hawaii) then the customer would see a shipping error like "No Shipping Options Available". |
| |
| They can also occur if no options are returned by the shipping carrier, which can happen if the shipping carrier's rate request system is unavailable for any reason (such as scheduled maintenance). Worth noting is that FedEx provides notice of their scheduled maintenance, but UPS does not seem to (at least, not that we've seen). When choosing a shipping carrier you should make sure to ask them whether or not you'll received notice when their rate request system is unavailable for any reason, as the lack of shipping options can prevent a sale. | They can also occur if no options are returned by the shipping carrier, which can happen if the shipping carrier's rate request system is unavailable for any reason (such as scheduled maintenance). Worth noting is that FedEx provides notice of their scheduled maintenance, but UPS does not seem to (at least, not that we've seen). When choosing a shipping carrier you should make sure to ask them whether or not you'll receive notice when their rate request system is unavailable for any reason, as the lack of shipping options can prevent a sale. |
| |
| ==== What They Look Like ==== | ==== What They Look Like ==== |
