Production Release 8 Bugs

[wsmith]

Re: Production Release 8 Bugs

Unable to download list of available patches

This portion of the error message usually indicates the site is unable to communicate with our license manager. Can you upload our diagnostic tool to test the license manager call?

Diagnostic tool (diag6.mvc)

https://support.mivamerchant.com/supportsuite/index.php?/default_import/Knowledgebase/Article/View/1069/62/miva-diagnostic-application

Wayne

[skepticwebguy]

Re: Production Release 8 Bugs

I noticed running diag6.mvc that my License Manager Call is saying FAIL on these:

https://licensing.smallbusiness.miva.com/gateway/gateway.mv -> Unable to open URL 'https://licensing.smallbusiness.miva.com/gateway/gateway.mv': Error establishing SSL connection: certificate verify failed
https://licensing2.smallbusiness.miva.com/gateway/gateway.mv -> Unable to open URL 'https://licensing2.smallbusiness.miva.com/gateway/gateway.mv': Error establishing SSL connection: certificate verify failed
https://licensemgr.miva.com/gateway/gateway.mv -> Unable to open URL 'https://licensemgr.miva.com/gateway/gateway.mv': Error establishing SSL connection: certificate verify failed

I think the problem is with OpenSSL. I've uploaded these three folders to my certs directory:

openssl-0.9
openssl-1.0
raw

The top two openssl folders appear to be empty on my server and I see that they simply contain aliases or symbolic links to the raw folder. Perhaps the symlinks aren't being maintained when I FTP them from my had drive to my server...

I've updated my .conf file to point to the openssl-0.9 folder and then I tried pointing it to the openssl-1.0 folder. Neither one seemed to fix the License Manager Call FAIL.

Thoughts?

[Jim McCormick]

Re: Production Release 8 Bugs

openssl-0.9
openssl-1.0
raw

The top two openssl folders appear to be empty on my server and I see that they simply contain aliases or symbolic links to the raw folder. Perhaps the symlinks aren't being maintained when I FTP them from my had drive to my server...

Thoughts?

Either try to FTP the files from openssl-0.9 from your machine to the server or upload the entire engine .tar and uncompress it on the server. I've had the same problems with FTP at times and uploading the files again usually works.

[skepticwebguy]

Re: Production Release 8 Bugs

Either try to FTP the files from openssl-0.9 from your machine to the server or upload the entire engine .tar and uncompress it on the server. I've had the same problems with FTP at times and uploading the files again usually works.

Untarring on the server worked. Thank you!

What permissions should the "raw" and "openssl-0.9" folders have and what permission should the files with those folders have?

[osgd]

Re: Production Release 8 Bugs

Using Authorize.net payment module, am getting reports of customers using IE9 not able to see any credit card selections except the first one-Amex. It appears there is no other cards in the dropdown. I don't have Windows 7 therefore don't have IE9. I've tested this with Safari, FF, IE8, Chrome & Opera and haven't seen any issues.

[Rick Wilson]

Re: Production Release 8 Bugs

S. Conner,

Can you send me your URL, we'll have QA look at your store.

[osgd]

Re: Production Release 8 Bugs

http://wesqueak.net/mm5/merchant.mvc?Screen=SFNT&Store_Code=WS

[Rick Wilson]

Re: Production Release 8 Bugs

When we tested in IE9 we saw Amex, MasterCard and Visa.

[osgd]

Re: Production Release 8 Bugs

Ok thank you for checking. I'm puzzled as to why we are now getting random calls regarding this issue. It's not common, but about once a week is more often than I'd like. The code looks good to me, so I'm not sure what the gremlins are up to.

[Rick Wilson]

Re: Production Release 8 Bugs

Understood. If you track it down, or even get more clues, we'll keep digging.

[SteveG]

Re: Production Release 8 Bugs

Ok thank you for checking. I'm puzzled as to why we are now getting random calls regarding this issue. It's not common, but about once a week is more often than I'd like. The code looks good to me, so I'm not sure what the gremlins are up to.

It could simply be they are going past the payment select page, ie not making the selection before clicking the continue button and then gettig stuck on the next page where Amex is already selected for them - I get the occasional one too and put it down to this, I put a message on that page to go back one page to select a different card.

[Rick Wilson]

Re: Production Release 8 Bugs

One thing it could be is I've noticed a nasty drop down bug in Safari lately that sometimes won't let you drop down or see the select list a second time. This is not related to Miva at all as I see it all the time on non Miva sites.

You might see if they're all on Safari.

[jsisk]

Re: Production Release 8 Bugs

Had the same issue with customers calling because their credit card was not listed. Only showed American Express. Also had a few calls stating that only one shipping option was displayed.

Site has been running Miva Merchant since 1999 beginning with version 1.7 and upgraded several times over the years without a single phone call from a customer relating to the drop-down menu for credit card selection. The credit card selection page has never been modified. (until this problem)

As soon as we upgraded to Miva 5.5 version 8 (we skipped 7) the phone began to ring 1 to 3 times a week. Tested the site in IE6, IE7, IE8, Firefox 3, 4, and whatever the latest is and could not duplicate the problem yet the phone kept ringing.

Finally bought the WCW Sort Shipping module and replaced the drop-down menus with radio buttons and have not recieved a single call since. Conversion rate also went up, so obviously there were lots of customers that didn't call. Instead, they went somewhere else that accepted something other than just American Express.

There is definately a bug somewhere in the system. I would have to guess that it is somewhere in the way Miva is storing the checkout info. We take a lot of phone orders and simply process them through the website. One thing that I have noticed, is that in Miva 4 and prior if you hit the back button during checkout to correct a typo, it would clear and reset all the fields and you would have to start all over with the biliing and shipping name and address. Now with Miva 5 you can go back and forth between the checkout screens and the only fields that clear and reset are the credit card fields on the OPAY screen.

So Rick, if you look at the difference between how the credit card number field is being handled on the OPAY screen (on refresh) and how the payment/shipping option fields on the OSEL page are being handled you may find the problem.

[cwlale]

Re: Production Release 8 Bugs - UPS Ready Tools

I made the mistake of setting up the UPS Ready Tools. Because it had issues that may or may not have been problems, I disabled it and tried to go back to the Viking Modules that I had been using.

I now have NO SHIPPING rates. First, I tried to re-enable my Viking custom shipping - No Joy. Then, I tried to bring up the original MIVA UPS - still no joy. Then I tried USPS (Viking and MIVA) and they do not work now, either. And finally, I tried to re-enable UPS Ready Tools just so I'd have some rates. No rates there, either, now. Apparently, there is something in the UPS Ready Tools that was not completely disabled and is not being reset properly.

The rates ARE showing on the pull down, for all of the modules, on the OSEL page. But, no matter which rate you select, no rates are showing or adding in on the OPAY page. I haven't carried an order all the way to the INVC, but I suspect it doesn't have the rates, either. Also, strangely enough, Sale Tax doesn't show either, now.. Since the rates are apparently being calculated, the problem must be in the calcs for OPAY.

I have reported this problem to ebusiness Express who is my provider/host. They have been working on it all day, to no avail. I assume that they have an escalation path. But, in the meantime, my website is in "maintenance mode" as I have no shipping rates. This is not good.

When I first enabled UPS Ready, it did yield rates. However there were two problems.

1. The rates returned were much higher than Viking or UPS.com calculations. On an $8 charge, the new module returned $10.

2. Secondly, apparently, the module does not recognize the original standard for commercial rates (filling in company name on the Address Screen). It returns the same rate with or without the company name field being filled. (I don't know if this module uses the UPS API for Address/Street validation or not - maybe that's why it didn't calculate commercial rates as the address I used was residential).

In any event, I'd really appreciate any ideas as to how to get by this problem. I need to get my website back in business ASAP.

Thanks.

Wes Lucas
classic-peanuts.com

[Rick Wilson]

Re: Production Release 8 Bugs

1. The rate both come from UPS so they should be the same unless something is configured differently.
2. Using the Company field is exactly how you trigger a Commercial rate.