Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

[skepticwebguy]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

It sounds like you have the attribute template with inventory enabled but have not created the variants and assigned levels to them.

Thanks William. That was exactly it!

[jpatrickm]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

A customer called to order by phone after repeatedly getting a "session timed out" error during checkout after Customer Info page. Should have asked if it was after inputting cc info. Have noticed a number of abandoned carts. Could this be a bug or just a problem with Authorize.net?

A client called us this morning and reported the same problem, only on the final invoice confirmation page. I just thought I'd scan the forums here for any chatter on this and found this post.

We just upgraded them to Wombat about 3 weeks ago and since then there have been a bunch of duplicate orders submitted and calls from customers asking if their order was submitted becauses they just got a white screen timeout at checkout.

We do have popup surveys running but these have always been there. I'm not sure how to troubleshoot this but I thought I'd at least chime in and let you know this *may* be an issue someplace.

Thanks.
Joe

[RayYates]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

FYI
I had a client with this issue with PR6 (non - wombat). I moved all the external javascript to the bottom of the page and the situation improved.

[Laura Schindler]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

A client called us this morning and reported the same problem, only on the final invoice confirmation page. I just thought I'd scan the forums here for any chatter on this and found this post.

We just upgraded them to Wombat about 3 weeks ago and since then there have been a bunch of duplicate orders submitted and calls from customers asking if their order was submitted becauses they just got a white screen timeout at checkout.

We do have popup surveys running but these have always been there. I'm not sure how to troubleshoot this but I thought I'd at least chime in and let you know this *may* be an issue someplace.

Thanks.
Joe

Do they use Authnet? We had some merchants report that Authnet was having issues a couple of days ago with intermittent timeouts and multiple orders.

[crozon]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

We are getting the "Out of Memory" Line 137 as well.

The computer with the issue is running Windows Vista ultimate service pack 2 with IE version 8.

We were trying create a group of shipments and it would give us the error.

Then we tried to create a single shipment and add a tracking number and it would give us the error and it would keep giving us the error. After about 4-5 times of giving us the error in a row it would then allow us to put in the tracking number.

This happened for about an hour last night while we tried to enter about 20 tracking numbers.

It is already happening again this morning and all we did is open Miva.

We tried restarting the computer and clearing all the cookies and browsing history (just in case) but no luck.

[skepticwebguy]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

In PR7, how can I get the default Ship To Country on OCST to be "Select one"?

I see that "Select one" is an option in the Ship To menu. Why is it even there if it's not the default?

[wcw]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Inventory Variant Bug Leaves Orphaned Records

1) On a product edit screen create a radio attribute with options.
2) Make them inventory variants.
3) Assign stock levels to each variant.
4) Go to the admin > products and search "all" with the base product code. The base and all its variants should show.
5) Go back to the product edit screen and click Attributes. Delete the attribute and its options.
6) Check inventory variants and you will see they are gone.
7) Go to products and search on the base product with "all". You will see they are still there. Bug as the products database is containing orphaned records that cannot be deleted unless you do it manually. Also, the inventory database contains those records too.

I found this while experimenting with the Template Data Feed to see what kind of exports it could produce from the products database to help identify variants' inventory so they could be modified and imported back in with the built in product import. But alas, I ended up with a large number of variants which no longer exist in the base product.

Please fix this bug.

Any idea how we can clean out the orphaned records in the product and inventory databases?

[Rick Wilson]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Bill,

This is not a bug, since Variants can be used on multiple products, kits, etc...

The way to delete them is to go to All in the products selection (All simply shows the inactive product, which is all a Variant is) and then remove them the way you'd remove any other product.

[wcw]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

But the same variant is not use on more than one product. The variant ABC_BLUE_L would refer to the attribute option large blue of the product code ABC. There is no other product using that variant. So when you delete the large blue option in the ABC product edit screen the option goes away. But the variant is left in the products table.

Selecting ALL and looking for orphaned variants might be ok in a store with 20 products. But what about a store with 20,000 products. You'd have to go through a lot of screens looking for inactive products that don't need to be there any longer.

[Rick Wilson]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Bill,

That's not a true assumption. Yes if someone uses Auto-Generate and never cross pollinates those with a Kit, or in the future when you can import variants, use the same variant in multiple products.

However this was specifically designed with that flexibility. What you may be describing is the need for some additional tools to help manage all the new data in large stores, but it's certainly not a bug.

[RayYates]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

There are many new pages in Wombat for example ABUS. These are great except that they have been designated as admin screens and you can not change the page code. This makes sence for critical pages like PROD, CTGY, and the checkout pages but I request is that we be allowed to change the page code for non-critical pages like ABUS, FAQS, SMAP etc.

My client is moving from mm4 to mm5 / PT7 and they already have a page called "about"

http://www.somesite.com/Merchant2/me...c?Screen=about

this page is now

http://www.somesite.com/ABUS.html

In the .htaccess file I do a rewrite from /Merchant2/ to /mm5/
but must now also figure out how to re-write "screen=about' to "ABUS.html"

If I could just change the page code, I'd already be done. The thing is, they have a number of these pages that now exist inside Merchant by default, so we must re-write each of them. Andreas suggested I just copy ABUS to a new template called about, and that would work... it's just not elegant, and I do like elegant solutions.

[Rick Wilson]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Ray,

Why don't you just use our built in page and edit the Template?

[wcw]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

I think the plan was to have screens with preset page links (see bottom of http://www.pinemporium.com/SFNT.html ) so that newbies would not have to figure out how to change links for those pages.

[RayYates]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Ray,

Why don't you just use our built in page and edit the Template?

I did change the template, but I can not change the page code...

[Rick Wilson]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Ray,

You've lost me on this one, why not make your own page with the different page code and just ignore ours then?