bsmither

I cannot reproduce it on CC6110, and if, as you say, this was happening with CC618, then I should be able to see something. PM sent.

This situation is quite probably the result of the Merchant having enabled Authorize.net's "Advanced Fraud Detection Suite" (AFDS). Here are some links that discuss it: https://support.authorize.net/authkb/index?page=content&id=A509&pmv=print&impressions=false https://community.developer.authorize.net/t5/Integration-and-Testing/Held-for-Review-Status-to-do/td-p/29840 https://community.developer.authorize.net/t5/Integration-and-Testing/Are-quot-held-for-review-quot-transactions-included-in-the-batch/td-p/48673

We can certainly modify the module's code. But as I said, the Authorize AIM Developer's Guide (Oct 2015) says the '4' is "Held for Review". I surmise there is some reason Authorize.net determined that this transaction needs further review. Someone will need to examine these "4|1|256" orders within the Merchant Account Settings Panel at Authorize.net to discover why Authorize.net flagged them as such.

The Authorize AIM Developer's Guide (Oct 2015) says the '4' is "Held for Review". Maybe in your Authorize.net Account Settings Panel, there are conditions of the transaction not being met that prompts this response. Still, CubeCart should not flag it as an error. On the other hand, maybe so - but the response is up to the merchant. The docs say that the Merchant can change the textual response (defaults to "Your order has been received. Thank you for your business!") in the Merchant Account Settings Panel.

If Authorize.net is returning "4|1|252", then, based on earlier conversation, it seems the module is sending an "Authorize Only" request. Please verify. Also, try switching to Authorize Only, Save, then immediately switch back to "Authorize and Capture", Save.

I tested this on CC6110, and I had the browser show me a "Print Preview". This (supposedly) will show what the actual printed document will look like. (And I have actually modified the template just a bit to not print an extra blank page.) If the order has notes to print, there will be that page containing the overall template (logo, store address) an also the Note - but no other data. All other pages do show the customer address block. Do you recall if this just started happening with CC6111? Please verify with your browser's Print Preview. The Customer Address block is in a floating div, and may get repositioned when the width of the document's outer-most boundaries are narrowed to the width of your printer's printable area.

In this case, no, it isn't anything to be overly concerned about. This error would indicate that the shipping was attempted to be calculated on an empty shopping basket.

Welcome 6502CPU! Glad to see you made it to the forums. Currently, no "common carrier" shipping module uses that carrier's COD product. For example, the United States Postal Service has a COD service product. But CubeCart's USPS module is not coded to calculate the costs and manage the paperwork required. As a tedious work-around, you can print the order's invoice and take it with you when you drop the box off at the post office. Thus, you will have some info at hand to fill out the COD paperwork. The common carrier (e.g., USPS) could have an online API to create a printable COD ticket. Even so, getting that coded into the module would be an effort.

I have this just about figured out. Does WA tax shipping? Not all states do, and some states only tax that amount of shipping charged in excess of the actual costs of shipping (which you will need to figure out after the fact). Some states don't have any argument against charging tax on shipping even if its not required - as long as you submit the taxes collected.

It is best to override CSS rules that may be difficult, if not impossible to find in the CSS that comes with the Foundation. So, in the file cubecart.default.css, add: a {color: #CB5B06;} a:hover, a:focus {color: #AB3B06;} button, .button {background-color: #CB5B06; border-color: #AB3B06;} button:hover, button:focus, .button:hover, .button:focus { background-color: #AB3B06;}

Depends. Later versions of CC6 give the frontside seven days of a session (PHP keeps a record of the cookie). Prior to that, frontside was one day (if I recall), and even earlier, one hour. However, the provider of your hosting platform may have an internal PHP setting of a more aggressive session management.

Wow! I really missed the mark. You ask about taxes and I give you shipping. We will need to develop a "tax by zipcode" capability.

Well, that sucks. Unless Washington State has an online API where, given the zipcode (and that is not at all a definitive special district boundary identifier), returns a list of who gets what pennies on the dollar. It seems the All in One Shipping module has the ability to create shipping zones based on postal codes. When creating a new Shipping Zone, you will be able to specify a collection of zip codes that are to be included in this zone.

Is this your understanding of Washington's tax rules, or is it your CPA's understanding. I know of only two states, and neither require complicated tax calculations. Just get the base rate for the state and the state will be happy with that. I also follow the "Amazon Tax" brouhaha that several states are arguing, and so far, I have only read about Amazon to collect the base state rate - not each and every dog catcher district.

Having followed my instruction to add a specific instance of the BXSlider into the Homepage document, you may have this: In admin, Documents, click the Edit icon for the document identified as the homepage document. On the Content tab, switch to Source mode. Find something similar to: <ul class="bxslider_homepage"> Change this by adding only the style="display:none;" part: <ul class="bxslider_homepage" style="display:none;"> Find something similar to: $(window).load(function(){ $('.bxslider_homepage').bxSlider({auto:true,captions:true}); }); Change this by adding only the .show() part: $(window).load(function(){ $('.bxslider_homepage').show().bxSlider({auto:true,captions:true}); }); We initially tell the browser to suppress showing the list of images. After the window loads, the BXSlider functionality is triggered, which converts the list to a slider. But, since the images for the slider are not shown, the added show() is used to make them visible then instantly converted to a slider.

Customers do not get an email when the order goes to Pending (exception: the POS gateway could send a reminder email). The config setting is for when the Administrators get an email. If the customer does not get an email when the order goes to Processing, that will be the issue to solve. Upgrading to 6.1.1, or 6.1.10?

The emails are in CubeCart's admin, Email Templates. Click the flag of the email translation you want to edit: probably Admin: Order Received. On the next screen, view the HTML Content and Plain Text Content tabs. You should see lines for Subtotal, Discount, Shipping, Taxes, and Order Total.

For the 505 issue, I think a web server error log (as opposed to a PHP error log) should show the error. For the blank page, try creating the error log file.

The 2.0.3 part of EBS 2.0.3 is CubeCart's versioning and does not necessarily reflect the EBS API version. That said, comparing the EBS documentation against what CubeCart's module sends has a few differences. Do you have the ability to examine web access logs from your hosting accounts control panel (Cpanel, perhaps)?

Welcome The Home Depo! Glad to see you made it to the forums. According to the EBS Integration Guide, the choice of the Merchant Name or Merchant Domain Name is made on the Merchant Payment Page Preferences (at EBS - not configurable at the CubeCart integration). The docs say the Merchant can have up to five payment pages, each with distinct design and content, and the page to use (page_id) can be specified in the data sent to EBS for making payment.

Welcome DeanDM! Glad to see you made it to the forums. Depending on the version installed, CubeCart will require two PHP extensions that are not always enabled: Multi-Byte Strings, and ZipArchive. You may be able to enable them in the CPanel option of configuring your PHP installation. Please see this post about how to create an error log file.

That's bizarre. An HTTP response of 505 is "HTTP Version not supported". That would probably be a case of the browser wanting to make a page request using a weird HTTP protocol version. The only thing I can think of is that CC606's admin.js javascript file has some sort of ajax request to start a backup, and the ajax request is configured badly. But that is such a long shot. (I haven't looked at CC606's javascript to confirm.)

Yes, it would be nice to know. I could probably find out, but would need access to the admin side of the store - in order to view the HTML and discern what the faulty HTML happens to be that causes the button to be mis-located.

The Save button is definitely in the wrong place. That tells me there is a rogue </div> tag somewhere in the admin skin templates. Or "possibly" the contents of the Offline Message or Copyright content has something that is confusing the browser in how to render the HTML. You can certainly re-upload the admin skin, then manually delete all files in the /cache/skins/ directory. A storefront skin (theme) cannot affect the admin skin, or v.v.

I do not have an answer for the Chrome vs Edge difference. I do not have an answer for this site versus your other site difference, other than the version of CubeCart may be different? The latest version of CubeCart is really wanting to pass back and forth a security token. So much so that I think it is a bug. Please try this: in the CleanSkin config.xml file, make this edit: Find: </info> Add ABOVE: <csrf>true</csrf> In CubeCart's admin, Maintenance, Rebuild tab, clear the cache. This will have CubeCart re-fetch the skin configuration. Now, CubeCart will add the code necessary to pass back to CubeCart the Security Token when submitting a form, such as Add to Basket, Login, and Register.