Announcement

**lesliekirk** · 07-03-11, 11:41 AM

Re: Production Release 8 Bugs

The MMUI store doesn't seem to have the same screen layout referenced on page - I don't see a drop down select for an image on the Search Results Layout screen.

I do have the Image Machine srch_imagemachine assigned to the page, so I am seeing the tabs related to it. And I'm wondering if the template code itself needs to be edited to get this to function. I have added

<mvt:item name="srch_imagemachine" param="head" /> to the <head> but that was just a wild guess.

**Rick Wilson** · 07-03-11, 11:58 AM

Re: Production Release 8 Bugs

I asked Brennan to chime in, it'll probably be tomorrow, since he's travelling today.

**wmgilligan** · 07-03-11, 12:20 PM

Re: Production Release 8 Bugs

Originally posted by Rick Wilson View Post

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

Maybe its the long weekend or something - but I just don't see it.
As far as I can tell the image machine is not enabled on the basket page (but honestly, how would I even tell?)

And the page referenced in the pdf discusses the search page, not the basket...

Do I sound confused?
Bill

**lesliekirk** · 07-03-11, 01:35 PM

Re: Production Release 8 Bugs

I was going to mention that it didn't cover the BASK screen - but I wasn't sure if I just missed something.

**Devpro** · 07-04-11, 08:32 AM

Re: Production Release 8 Bugs

Adding items to basket overeride the first item. Can only add 1 item. Thisonly happens in Safari. I'm using 4.0.5 Works fine in IE and Firefox

Tom Dean
Web Maintain

**Rick Wilson** · 07-04-11, 08:47 AM

Re: Production Release 8 Bugs

Tom,

Something is wrong with your setup, I use Safari almost exclusively and just double checked it's not happening on any of my PR8 stores.

Have you tried other copies of Safari? On other machines?

**burch** · 07-05-11, 07:14 AM

Re: Production Release 8 Bugs-Capture Error

Originally posted by oldsportbiker View Post

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

This is close, but not entirely correct. pay_id tells us which payment module to use to capture the payment. The underlying code will call this module, telling it to perform the capture operation. It appears that when you process a payment using Card Magic, its module ID (173) is recorded instead of the underlying payment module. We don't skip the capture operation or do anything differently if the pay_id does not point to a module we recognize, but it does sound as if Card Magic is not properly routing the capture request to the underlying payment module, and is just blindly returning success.

We will attempt to get a copy of Card Magic set up in our QA environment so we can look further into its behavior.

**Brennan** · 07-05-11, 08:14 AM

Re: Production Release 8 Bugs

Here are the instructions for adding the image machine image to the basket page:

1. You first need to turn on the Custom Image Fields under utilities. You need image types in order to do this and it order to be able to assign image types to pages like the basket page this setting must be turned on. Click the plus next to utilities and check the box next to Product Image Custom Fields

2. Next you need to create an image type for the basket page. This can be done on any product page or the main Products screen.

3. Go to BASK page then basket contents tab. Assign the image type you want to show up here to this page by checking the box next to the image type. This is similar to how regular custom fields work on CTGY or PROD.

4. Modify the code. Any image type assigned to a page automatically becomes available on the page via SMT. You can reference it by using this entity:

&mvte:item:imagetypes:ndx; Where ndx would be the code for the image type you created in step 2.

If you are using image machine with inventory variants and you have the correct color image defined for your image type, the store morph entity &mvte:item:imagetypes:XXX; will automatically contain the correct image for the attribute combination that was selected.

**papi34** · 07-05-11, 09:54 AM

Re: Production Release 8 Bugs

After upgrading to PR8 it seems that Related Products has gone haywire. Click on any product from one of our category pages and seems every other product in that category is listed as a related product - totally ignoring the item's real related products (if any).

**Brennan** · 07-05-11, 09:58 AM

Re: Production Release 8 Bugs

papi34 -

Do you use Category Template Manager? Some versions have issues with related products. Try upgrading the module and see if that fixes it for you.

**papi34** · 07-05-11, 10:10 AM

Re: Production Release 8 Bugs

Originally posted by Brennan View Post

papi34 -

Do you use Category Template Manager? Some versions have issues with related products. Try upgrading the module and see if that fixes it for you.

Funny you should mention that. I renewed my Sebenza License for Category Template Manager prior to PR7 and it is about to expire in a week or two. So just a few days ago, I checked for updates and saw one was available for PR8, so I downloaded/installed it.

| Version 5.45 05/25/2011
| - Updated made for PR8-beta
|
| Version 5.44 12/09/2010
| - Added default sorting by custom product field.
|
| Version 5.43 08/09/2010
| - Added sorting support for "sku" field.

So I went from version 5.43 to 5.45 and it basically broke my related products function. What was Version 5.45 supposed to fix and what do I do now?

**papi34** · 07-05-11, 11:11 AM

Re: Production Release 8 Bugs

I opened a support ticket (DCK-719109) with Sebenza a little while ago. Meanwhile, I confirmed thru a dev site that Version 5.43 of the Category Template Manager was working OK. Version 5.45 (Updated made for PR8-beta) is causing the problem. So think twice before getting the latest version of Sebenza's module if you are on PR8. While I'm waiting to hear back from Scott on this open ticket, does anyone know if it would cause a problem if I reinstall Version 5.43 over Version 5.45? I don't want to corrupt any files.

Edit: Or is there an item that I can unassign on my PROD page to disable the related products until this is fixed?

**Geographicus** · 07-06-11, 02:57 PM

Re: CSV Import

I must say, one of features I was most looking forward to was a better CSV Product import. I had hoped that we would be able to assign default fields for importing products. What I found is completely disappointing. Unless I am missing something, the new CSV import does allow you to set fields, but only within the New CSV import. They are not retained during regular csv import. Most dissapointingly, the new CSV import cannot handle common data that I use every day and which the old CSV still handles without problems. Every time I upload a flat file in the NEW system, I get messages about data errors relating to too long product codes, parsing errors regarding the use of quotations, and more futz ups. None of this happened in the past. Really disappointing guys.

Kevin

**Rick Wilson** · 07-06-11, 02:59 PM

Re: Production Release 8 Bugs

Kevin,

What do you mean they are not retained? Are you mixing the new system and old system?

**Rick Wilson** · 07-06-11, 02:59 PM

Re: Production Release 8 Bugs

Also can you send me some sample files so we can test?

Announcement

Production Release 8 Bugs

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment