Production Release 8 Bugs

[papi34]

Re: Production Release 8 Bugs

Correction. The PR8 Update only overwrites the existing Shipment Confirmation HTML Email, not the Back Order Confirmation HTML Email. Can you test the Shipment Email as well?

Note: I always edited those email templates directly from the link in Store Utility Settings. Could that be why I had the problem?

Didnt even realize they were also listed under Pages. What I have for emails under pages is:

BACKORDER_CONFIRMATION
RMA_ISSUED
RMA_RECEIVED
SHIPMENT_CONFIRMATION

SHIPMENT_CONFIRMATION is set at the "ORIGINAL" version. I can't recall the custom email that was created.

[DelMonico Hatter]

Re: Production Release 8 Bugs

Hello from Brandon at DelMonicoHatter.com:

This may or may not be a bug, but it is a compatibility issue with the Stone Edge order manager which may be solvable by tweaking code on Miva's end.

We're in the MM4 to MM5 transition. We're looking at the possible need for a MM5 custom module, or something like that. Perhaps you can advise us as to the best course of action to take, and if a custom-coded module is needed.

We're having an integration issue between Miva 5.5 and the Stone Edge Order Manager. It has to do with the MM5-native inventory manager. You'll have to bear with me, the issue is a bit complex and very specific to our systems:

I'm using Miva 5.5 PR8, and Stone Edge version 5.921. We're tracking quantities down to the attribute level. We use the "Auto-Generate" feature to create our product variants in Miva.

We have attribute codes like "S-Small", "XL-X_Large" and "BK001-Black", "SG230-Sea_Green", etc. This is because we want our order processing staff to see the attribute codes in plain English. However, the computer programs we use for our inventory management only need the first half to recognize an inventory item, which is everything before the "-" . Thus, Stone Edge is programmed to ignore everything after the "-" when creating its product variants (called sub-SKUs in Stone Edge parlance).

Example: When the variants are imported into Stone Edge, it truncates the codes to "S", "XL", "BK001" and "SG230" respectively. Everything after the "-" delimiter is cut off when it uses the Miva data to create its sub-SKUs.

If the master product code was PR123, an example variant created by Stone Edge would be:
PR123-XL-SEGR

Previously, this worked fine when we were using Viking Coders' Inventory Manager in Miva 4.22. The Viking Inventory Module was designed specifically to work well with Stone Edge.

However, in Miva 5.5's native inventory manager, there is a problem... Miva's inventory system creates product variants which look like this:
PR123-XL-X-Large-SEGR-Sea_Green

Meanwhile, Stone Edge still truncates the data when it makes its Sub-SKUs. But, that makes it so that the variants in Stone Edge do not match verbatim the same variants in MM5. Therefore, inventory quantity data cannot pass correctly from Miva to Stone Edge. Miva tries to send Stone Edge the non-truncated vairant code, while Stone Edge is looking for the truncated code.

This might require a custom module, but is there a way to make it so that the "Auto-Generate" feature of MM5 recognizes our "-" delimiter, and truncates the variant codes in the same way as Stone Edge when creating product variants? This only needs to be done for the Attribute Codes, not the master Product Code of an item.

If a module could be made to perform this simple task when Miva auto-generates, it might save us loads of time in the long run since our systems are already geared to incorporate it.

What do you think could be done? Is there something off-the-shelf which could handle it, or is it a custom job?

Best,
Brandon Moreau
DelMonicoHatter.com

[lesliekirk]

Re: Production Release 8 Bugs

Attempting to resort the Manage Orders > Customer order and got the following error:

Miva Merchant returned an invalid response.
Function: OrderList_Load_Query
Response: {
"success": 1,
"data":
[
{

...private customer info removed from error...

[Rick Wilson]

Re: Production Release 8 Bugs

Leslie,

Can you email me the whole response? Dev needs to see it.

[Rick Wilson]

Re: Production Release 8 Bugs

DelMonico Hatter,

I had a quick chat with StoneEdge about this (this AM) and here's the only option if you want to use our Inventory System:

"Eliminate the use of the WebOptionCodeDelimiter in his Option Code field. This would require modification of all his options. Definitely not a welcome manual process - could be done via SQL Update Statement rather quickly depending on the size of his DB. "

[lesliekirk]

Re: Production Release 8 Bugs

Leslie,

Can you email me the whole response? Dev needs to see it.

Let me see if I can get it again. I knew I should have saved it to a text file.

Leslie

[DelMonico Hatter]

Re: Production Release 8 Bugs

DelMonico Hatter,

I had a quick chat with StoneEdge about this (this AM) and here's the only option if you want to use our Inventory System:

"Eliminate the use of the WebOptionCodeDelimiter in his Option Code field. This would require modification of all his options. Definitely not a welcome manual process - could be done via SQL Update Statement rather quickly depending on the size of his DB. "

Hi Rick,

Thank you for the quick response. This is unfortunate, but that's that.

You sent me that module before which was designed to get around the MM5 PR7 flaw of "you can't choose the inventory delimiter." With PR8 installed it's not needed of course, though I still have that module. Could I use that same module, or another data-upload module, to help automate the changes which Stone Edge advocated?

If I can get all the Miva product attribute data exported into an .xls file, I can use a simple "find and replace" operation in MS Excel to purge the attribute codes of everything after the "-" character, as a one-time thing. If I can then upload this change to MM5 to alter all product attributes at once, I might be up for that.

Would that work?

Otherwise I'll have to wear me fingers to the bone with the manual change, which ain't the funnest thing to do I s'pose, so hopefully I won't have to.

Brandon

[oldsportbiker]

Re: Production Release 8 Bugs-Picklist error

After the PR8 update the shipping method used in the SHIPMENT_PICKLIST page displays only for the first order, (most recent date), in the set selected for the picklist. While we have modified this page , (10 months ago), I don't believe that our mods have caused this PR8 issue. The array in the page is as follows:

<mvt:foreach iterator="ordershipment" array="shipment:shipments">

The other items displayed in the picklist seem to be there, it's just the shipping method that seems to be missing

[oldsportbiker]

Re: Production Release 8 Bugs-Capture Error

The recent release of PR8 contained a bug fix, http://bugzilla.mivamerchant.com/show_bug.cgi?id=5974, that was supposed to address a very serious funds capture problem on my clients site. After upgrading to PR8, I was extremely disappointed to learn that we still have the problem. Here's how the problem manifests itself:

1. Client processes an Order using Magic Metal's "Card Magic" Credit Card on File product.

2. Authorization type=1 OrderPayment record gets stored at checkout with a pay_id value = 173 (I believe that for regular CC orders run through Authorize.net, that the pay_id value is 57)

3. Client overlooks the order in batching authorize requests to Authorize.net inside the Card Magic product

4. Client changes the order status from Pending to Processing by creating a shipment in Miva Admin

5. Warehouse creates Picklist and ships the order marking them as shipped in Miva Admin

6. Client selects the order in Miva Admin and clicks Capture button

7. Miva Admin records successful capture instead of flagging it as invalid.

a. I believe that Miva uses the OrderPayment type 1 record attached to the order to determine how to capture
b. The OrderPayment type 1 record for this order still has pay_id=173
c. My guess is that Miva , in failing to recognize 173 as pointing to a known payment processor, accepts the capture request instead of rejecting it

8. Client runs "Shipped not Captured" report and order does not show up so he believes that order settlement is complete.

This has been extremely impactful for my client as these orders , (incorrectly tagged by Miva as funds captured), totaled over $40,000 before some custom financial audit reports uncovered the issue. Not being able to rely upon Miva Admin's "Shipped but not Captured" report has created significant concerns about the reliability of other critical Miva Admin reports.

Have other Miva customers experienced a similar capture problem and what have you done to resolve or address it?

[Rick Wilson]

Re: Production Release 8 Bugs

So somehow Kent's module is altering the PayID value? Or am I missing something in the equation?

When we discussed this prior to PR8 there was never any mention of using Kent's module in this process and I don't know if that will turn out to be meaningful or not but I need to understand if it's playing a role?

[oldsportbiker]

Re: Production Release 8 Bugs

It was only after a lot of database analysis that I determined the facts outlined in my thread. I don't know if the pay_id value is an issue or not. I do know that Miva reads the existing OrderPayment type 1 record which has a pay_id value of 173 and Miva Admin copies that value into the Type 2 record it stores during capture and in the process marks the funds as captured. In my opinion, if Miva sees a pay_id value that it can't reference, it should reject the funds capture request. If these rejects appeared sooner we would have had a heads up to resolve any potential Card Magic/Miva inconsistency.

[ians1234]

Re: Production Release 8 Bugs

After upgrade to 5.12, Iexplorer 9 shoves the last column of products down to next row and leaves blank space where last column should be. This didn't happen with Miva 5.09. No problem in Firefox, Safari, or Iexplorer 8.

[wmgilligan]

Re: Production Release 8 Bugs

Brand new install from scratch. 64bit empressa.
Everything is functional, no errors generated in diag or in admin screens.

I am just beginning testing of the latest release of merchant. So far, its looking pretty good.

One issue I have found - I can't figure out how to get images to show in the basket page.

I checked the mini box, and I also created a type, and then checked it.
But there doesn't seem to be any code change, not any indication of what code I may need to manually change.

What to do?
Bill

[lesliekirk]

Re: Production Release 8 Bugs

Bill - I was thinking there is an item that needs to be assigned to the screen - but when I looked at the items - it was one for the search...

srch_imagemachine

Leslie

[Rick Wilson]

Re: Production Release 8 Bugs

Page 23 in here covers it: http://www.mivamerchant.com/pdf/Miva...e_06-21-11.pdf