Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

[RayYates]

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

K

Missing semicolon &mvte:global:Search should be &mvte:global:Search;

_gaq.push(['_trackPageview', '/search.html?search=&mvte:global:Search;']);

[kayakbabe]

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

Ray,
I'm hanging my head in embarrasement. Something so obvious! I do know better too.

Wish I could go delete the posting I just made. I should stop working at the wee hours of the morning.

Kelly

[RayYates]

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

lol

alas I've made a few posts I wish I could take back.

[p4k]

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

When an item is canceled from an order in Manage Orders and the confirmation emails are sent again through Order Fullfillment Modules, both Merchant and Customer, the canceled item is still listed on the email confirmation order. Also, if the original shipping option is removed, it still appears in the confirmation email, although it is listed with a $0.00 value.

[midi73]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues-tracking table error

Hi all. I am upgrading to the PR7 but got the error below. Any ideas on what to do? Thanks. Sylvia


Incomplete installation of patch 'production-7' detected.
A patch that has been partially installed was found in your list of available patches.
The following error caused this patch to abort: Pre-install validation failed. No modifications have been made to the existing installation. The following issue must be resolved before installation can continue:
New table 'TrackingLinks' already exists.
After this issue has been resolved, please select Restart Failed Installation

To resume from the point you left off, select Resume Installation. To delete the upgrade patch scripts for the failed installation and close the Upgrade Wizard, select Discard Failed Installation. To restart the installation from the beginning of the failed patch, select Restart Failed Installation. Finally, you may select Submit a ticket to Miva Merchant Support to request assistance.
Please select an option and click Continue.
Resume Installation (recommended) Restart Failed Installation Discard Failed Installation Submit a Ticket to Miva Merchant Support

[Rick Wilson]

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

You need to contact our support department you have an aborted upgrade.

[midi73]

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

Thanks for the quick reply on the tracking links error on the upgrade.

I did put in a ticket. I hope they can fix that. Thanks. Sylvia

[kayakbabe]

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

I searched to see if someone posted in here but couldn't find it. So maybe this is a duplicate but maybe not.

attributes that are not marked required are still required.

Notes:

• I'm using cssui.
• I did setup the product initially with required and inventory for the attribute.
• I do have inventory variants listed for the product for each of the attribute/options I have for the master product.
• I then turned off required, and still I am forced to pick something when I try to add the product to the cart (even though nothing is required.)
• Inventory tracking is turned off for this product
• Inventory tracking is turned on for the variants
  

Example product: We sell a plain straw hat. We also sell a wildly customized limited editions of the same hat.
So we can sell unlimited numbers of the plain hat (sku:HAT) but we only make 10 of each limited edition. I want them all to be HAT, but only some of them to have inventory tracking. And I want to sell them all under product HAT. So it isn't required to track HAT.

HAT
HAT-FUEGO
HAT-DOMINO
HAT-PICANTE

[oldsportbiker]

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

I searched to see if someone posted in here but couldn't find it. So maybe this is a duplicate but maybe not.

attributes that are not marked required are still required.


Notes:

• I'm using cssui.
• I did setup the product initially with required and inventory for the attribute.
• I do have inventory variants listed for the product for each of the attribute/options I have for the master product.
• I then turned off required, and still I am forced to pick something when I try to add the product to the cart (even though nothing is required.)
• Inventory tracking is turned off for this product
• Inventory tracking is turned on for the variants
  

Example product: We sell a plain straw hat. We also sell a wildly customized limited editions of the same hat.
So we can sell unlimited numbers of the plain hat (sku:HAT) but we only make 10 of each limited edition. I want them all to be HAT, but only some of them to have inventory tracking. And I want to sell them all under product HAT. So it isn't required to track HAT.

HAT
HAT-FUEGO
HAT-DOMINO
HAT-PICANTE

If I'm reading the template code correctly there is a <mvt:if ...Required>
do this
followed by a <mvt:else>
do the same thing.

I don't know if it's a bug but it certainly looks like it. I ran across it today as I'm trying to customize the attribute display by making one of the attribute inputs hidden.

[kayakbabe]

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

On the BACKORDER_CONFIRMATION template
The value stored for the back ordered date is not accessible in miva's time format. It is being stored as a UTC and being pulled from the database at UTC instead of miva's default format which
I think looks more like 10/11/2010 18:05:11

So I can't have the backorder notifications show the estimated time of arrive that I set in the admin to the customer. a number like 1286773200 means nothing to them.

l.settings:item:dt_instock &mvt:item:dt_instock;

should be using the same time method as all the other dates throughout miva merchant for the display of time such as on the invoice template.

NOTE: also have the same issue where the backordered status is displayed as a number instead of the word that would make sense to the customer.


I'm curious why you aren't using mysql datetime instead of varchar(10) on that field ?

[kayakbabe]

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

I could write some mvt:if statements if I knew what the status numbers corresponded to.
I'm seeing 200, 201, 300 and 400 so far.

Can we get a list of what these indicate in words?

[kayakbabe]

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

For others trying to do modify the BACKORDER_CONFIRMATION template
I was able to convert the dt_instock (I found a global variable g.date_instock to a usable time by using toolbelt.

Right after &mvt:item:code; in inserted the following and it's working for me for now.

<mvt:item name="ry_toolbelt" param="datetime_format|g.return|g.date_instock|SHORTDATE" />
<mvt:if expr="NOT ISNULL g.date_instock"> - Expected Arrival: <mvt:item name="ry_toolbelt" param="eval|g.return" /></mvt:if>

Though for the record I still think it's a bug that it isn't already in the normal miva time format like is used on the invoice.

[kayakbabe]

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

bug: editing customer information in the admin, requires me to know the customer's password. Which of course.. I do not know.

Administrators should not have to know the customers password in order to edit the customer account from within the admin of the store.

[ILoveHostasaurus]

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

bug: editing customer information in the admin, requires me to know the customer's password. Which of course.. I do not know.

Administrators should not have to know the customers password in order to edit the customer account from within the admin of the store.

Are you sure your browser isn't filling a value in the password box and leaving the confirm password box blank, so the store thinks you're trying to change the customer's password?

[kayakbabe]

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

Well I"ll be.. I have been using a new machine.. new browser... etc. I"ll wipe the little stars in the first field and see what happens.... :-)