Miva Merchant 9.0004 Bug Reports

[Rick Wilson]

Re: Miva Merchant 9.0004 Bug Reports

See my post in the other thread, we've identified the issue.

[Leanne]

Re: Miva Merchant 9.0004 Bug Reports

After updating to 9.0004, store is failing to set the mm5-storecode-checkout-session cookie on the OSEL page and the shopper is kicked back to OCST with a message that their session has timed out. A ticket has been opened but not responded to. [#NBI-709-40749]

[widgetsupply]

Re: Miva Merchant 9.0004 Bug Reports

See my post in the other thread, we've identified the issue.

Which post/thread?

[Rick Wilson]

Re: Miva Merchant 9.0004 Bug Reports

I was talking to Candy about FedEx, sorry.

John your issue is the same as what was posted above. You can manually fix it, or wait for the patch today.

[widgetsupply]

Re: Miva Merchant 9.0004 Bug Reports

I was talking to Candy about FedEx, sorry.

John your issue is the same as what was posted above. You can manually fix it, or wait for the patch today.

I tried to fix it, but couldn't figure it out. :(

[Rick Wilson]

Re: Miva Merchant 9.0004 Bug Reports

Leanne,

Dev doesn't believe this issue is tied to 9.4, but would like to know what the lcpoppedup cookie is for?

[Leanne]

Re: Miva Merchant 9.0004 Bug Reports

Determining whether or not to launch an email signup popup

[Rick Wilson]

Re: Miva Merchant 9.0004 Bug Reports

Leanne,

According to Dev that cookie is somehow "stepping on" our cookie, they don't believe it's 9.4 related but are testing to be certain.

[Leanne]

Re: Miva Merchant 9.0004 Bug Reports

That was it. I disabled it and it's working now. Since it started at the same time as the update, I assumed they were connected.

[widgetsupply]

Re: Miva Merchant 9.0004 Bug Reports

I was talking to Candy about FedEx, sorry.

John your issue is the same as what was posted above. You can manually fix it, or wait for the patch today.

I gave it another go and I think I fixed it. For anyone else on SRCH, here is what I used:

&mvte:urls:_self:auto_sep;&mvte:search_results:pag e_links:prev_link_params;
&mvte:urls:_self:auto_sep;&mvte:search_results:pag e_links:next_link_params;
&mvte:urls:_self:auto_sep;&mvte:search_results:pag e_links:first_link_params;
&mvte:urls:_self:auto_sep;&mvte:pages:link_para ms;
&mvte:urls:_self:auto_sep;&mvte:search_results:pag e_links:last_link_params;

[Rick Wilson]

Re: Miva Merchant 9.0004 Bug Reports

FYI - Bug Fix 1 is now out and should fix all the issues presented thus far in this thread.

[mikey]

Re: Miva Merchant 9.0004 Bug Reports

Everything looks good on my end Rick. (FedEx and Category issue)

Thanks to you and the team.

FYI - Bug Fix 1 is now out and should fix all the issues presented thus far in this thread.

[jpatrickm]

Re: Miva Merchant 9.0004 Bug Reports

Since upgrading today no notification emails are being sent. We use an external SMTP server and are getting the following error:

One or more notification emails could not be sent at this time: Error connecting to 'smtp.sendgrid.net': Error connecting to smtp.sendgrid.net on port 587: Connection timed out

Customers are seeing that when checkout is complete and we get the same error when trying to manually send order emails via Order Processing screen.

I've reset the credentials under Domain Settings but still get the error.

We upgraded the Empresa engine at the same time. The SMTP server is functioning as we are able to send non-Miva emails successfully.

Any thoughts would be appreciated.

[rajnishsi]

Re: Miva Merchant 9.0004 Bug Reports

Hi,

Not sure if this belongs here or not, but I just logged into miva admin for upgrade to 9.0004. It showed me upgrade window, and when I started upgrade, it first installed the patch that was released for 9.0004 and then upgraded the store to new version.
Is this intended behavior? I thought, first, it would upgrade to the new version and then install the patch for it.

[lesliekirk]

Re: Miva Merchant 9.0004 Bug Reports

Hi,

Not sure if this belongs here or not, but I just logged into miva admin for upgrade to 9.0004. It showed me upgrade window, and when I started upgrade, it first installed the patch that was released for 9.0004 and then upgraded the store to new version.
Is this intended behavior? I thought, first, it would upgrade to the new version and then install the patch for it.

While not an official answer, it makes sense since the upgrade to 9.0004 seemed to have caused a minor disruption.