Merchant Version 2.0

Question:  Will the he Miva engine or whatever still support Miva 1.25 for the people who don't upgrade to 2.0?

Answer: Yes, Miva will still support Miva.

Answered by Johnathan Wray
 

Question:  How do I upgrade to Merchant 2.0 without erasing the product lists from 1.25?

Answer:  When you install 2.0 it installs to a completely  independent directory hierarchy and leaves your  existing 1.x Miva Merchant as is. You then create  your store in the 2.0 and use the import utility  to import all the products, categories, attributes,  fonts and color settings, etc. to your new store from your old one.

Answered by Jeff Huber @ Miva Corp.

Question: I noticed that Merchant 2.0 comes with its own Authorize.Net 3.0 payment module.   Should I stick with SB21's module? Will SB21's module even work in 2.0 since it's a 1.x module?

Answer: Our SB21 AuthorizeNet v3 payment module only works with Merchant v1.x and due to Miva including a v2.x version, we won't be upgrading this module of ours. Also, Miva has based their new module on the Commerce Library which will allow it to interface even better and it should work with no problems with v2.

Answered by Darren Ehlers @ STARBASE-21

Question:  Updated to v2.0 and now when trying to add the subtotal.mv module for  shipping I get this: /Merchant2/modules/shipping/SUBTOTAL.MV: Line 1: Expression Error: Call to undefined function  'Module_API_Version'
I take it to mean that this module will not work under 2.0? If so, has  anyone come up with a fix ... or can tell me how to?

Answer: You cannot use modules written for Merchant 1.x in Merchant 2.x without
modification. Miva Corp specifically wrote their new code to prevent
that. Multiple function names within each module have been changed.
Additionally, the way modules are added and registered into the mall and
stores has changed. This was done to provide the tabbed look and feel.

Take a look at my notes at the top of the product description for CIM
Tool Kit 3 in my store (link below). Then compare the licenses between
Merchant version 1 and 2; re: DEVELOPER vs LICENSEE word swapped.
You'll also note that all of my modules were converted and most are
available under this change in licensing terminology. They are
available for the CIM TK 3. Unfortunately, the shipping modules,
although converted, cannot be distributed at this time. They are
pending.

I specifically asked Miva Corp which parts of the shipping modules, eg
subtot_z.mv (which I sent to Joe), have to be changed to comply with
their license without destroying the look and feel in the administrative
interface and creating a different interface that the customer sees when
shopping. I have not received a response. When I get a response I will
know what needs to be done to get the six shipping modules usable in
Merchant version 2. I prefer NOT to create a cobbled appearance to make
them work.

I would have responded to you in private, as I have with many others, if
you had written me in private. But since you posted to the users lists,
I think others need to know this information also. It is not that the
3rd party developers have abandoned their user base, it is that we are
awaiting guidance from Miva on how much of a standard Miva module can be
used in a modified module in order to perform new functions yet maintain
the Merchant look and feel. If you are contemplating upgrading to
Merchant version 2, you should make sure that ALL of the third party
modules you are using in your version 1 are available before you
upgrade. That goes for anybody contemplating upgrading.

Answered by William Weiland @ http://wcw.simplenet.com/merchant/merchant.mv

Question:  I run an Antique store, once item is sold we want it to disappear from
> thte database entirely. That way we do not have to manually remove the item.

Answer: As promised, I've added that capability to Inventory Management (IM) in the CIM Tool Kit 3 for Merchant version 2.x.

Answered by William Weiland @ http://wcw.simplenet.com/tk3/custprod.htm

Question:  I am intermittently dropping bits of data files when making updates to the  settings in the edit store screen of admin. For example, I just changed the  body font, and after I clicked update the paths to two graphics, along with  the category list footer were gone. Earlier, I added the path to a search  graphic, and the path to a category tree graphic disappeared. This sort of  thing has happened on 5 or 6 occasions since I started working with a fresh  2.0 store a week ago. Has anyone else experienced this?

Answer: I experienced the same thing until I started Packing the Mall and Store after each change.

Answered by Luray @ Santafemall.com

Question:  What I need to know is what do I need to do to save all of my current stuff, so that it is not lost when I do the upgrade?

Answer: Just follow the directions and you will import your version 1.x store and all of its contents into version 2.0.

Version 2.0 installs as Merchant2. This allows you to get it set up the way
you want while still using version 1.x. I have had version 2.0 installed for
about two weeks and haven't started using it yet.

Answered by Luray @ http://www.santafemall.com

Question:  Why doesn't the "Upload" button work using IE 4.5 for Macintosh?

Answer: The file upload problems with the mac and ie 4.5 is a known
bug that will be fixed in the next release of Empresa. You
can work around the problem by using a different browser.

Answered by Jeff Hubber @ Miva

Question:   How do I upgrade from Version 2.0 to Version 2.01?

Answer: The procedure for upgrading is just how it was if you upgraded from 1.24 to .25.

1)BACK UP both Merchant2 directories.
2)Install Merchant 2.01 onto your local computer, naming the directory
Merchant2.
3) You will then want to FTP the NEW Merchant2 directory onto the server, overwriting the other Merchant2(script) directory. NOTE: MAKE ABSOLUTELY POSITIVE YOU ARE OVERWRITING THE SCRIPT DIRECTORY. It will be in a directory called something like html, www, web, etc...
4)Run the Upgrade script. - www.yourdomain.com/Merchant2/upgrade.mv.
5)Go from there.

Emily Rose Nichols @ Miva Corporation

Question:  What changes have been incorporated into Version 2.01?

Answer:  Miva Merchant v2.01 has the following fixes and features:

-------------------
1. Added code to strip non-numeric characters from the pagination edit
fields in administration.

2. Fixed typos in the Privilege_Delete and Privilege_Find functions
in error cases.

3. Fixed a bug which prevented the secure module root directory from
being saved during initial setup.

4. Fixed a bug in the Anacom payment module which prevented users from placing orders.

5. License agreements are now displayed with the READONLY attribute set in their TEXTAREAS.

6. Fixed a missing '$' on line 2204 of mm1impt.mv, which caused a syntax error in an error case.

7. Fixed a bug in the Anacom payment module which caused accepted credit card settings not to be saved.

8. Fixed a bug in the Anacom payment module which caused a syntax error when processing orders.

9. Added an informational message to the Anacom payment module which provides a link to Anacom's order processing system.

10. Removed some unused code from the Authorize.Net payment module.

11. Product thumbnails are now hyperlinked to the product description page in the Miva Merchant Look & Feel.

12. Fixed a bug which allowed a customer to create a customer account with the same login id as an existing account.

13. Order totals are now padded to two decimal places on the order edit
screen in administration.

14. The "Fax" field in the "Owner" tab of the store edit screen is now the
same width as the "Phone" field.

15. Fixed a bug in the KoolCat Look & Feel which caused a syntax error if a customer purchased an upsold product but did not select all required attributes.

16. The "State/Province" field in the Customer edit screen in administration is now a drop-down select list.

17. Fixed a bug which would sometimes cause a fatal error to be displayed when a module was deleted from the domain using Netscape.

18. Fixed a bug which caused a runtime error when a module was added to  the domain with a leading slash in the module path.

19. The "Pagination" fields of the store edit screen when using the Miva
Merchant Look & Feel are now properly validated.

20. Fixed a bug which caused an error message to be displayed when uploading a currency module.

21. Fixed a bug which caused a syntax error if the user specified a secure
module root that did not begin with a slash.

22. The secure root directory for modules and secure base URL fields are now

required if either the secure URL to Miva Merchant or secure URL to
Administration are specified.

23. Fixed JavaScript errors when viewing the layout preview for the Miva Merchant Look & Feel under Netscape 3.x.

24. Fixed a bug in the Cardservice/LinkPoint Payment Gateway payment module that prevented an order from being authorized if a product contained a checkbox or text-entry attribute.

25. Added additional code to prevent a user from switching tabs in the
administration before a page has completely loaded.

26. Changed license agreement to say v2.x instead of v2.0.

27. Fixed a harmless typo in the function Action_Customer_EmailPassword  in merchant.mv.

28. The Authorize.Net payment module now specifies a value of 3.0 for the x_Version variable. This should enable it to work correctly with merchants who are configured for version 2.5 of Authorize.Net's service.
 
29. Fixed several typos in the Miva Merchant v1.x Import module which
prevented importing settings from the Shopper Selected sales tax
module.

The above and future fixes that were accomplished in prior releases are
documented in the CHANGELOG.txt included with the release.

Information provided by Miva Corporation

Question: I want to set up a different price structure for wholesale.  Do I have to set up a whole new store?

Answer: No, you don't.

Just enter them as a customer and create a price group. Then add them to the price group. They'll see different prices.

Answered by:  Pamela

Question: Is there a UPS Shipping Module Available for 2.X?

Answer: If your problem is related to the extra zip code digits, then you should know that there is a UPS module at the Miva Exchange that has corrected this problem. Since you have no control over how many digits a customer will input, you may want to look at it. The name of the module is the UPS2.5 shipping module.

Answered by M. Seaforth @ http://innovationhouse.com

Question: Why am I calling up another customers information when I try to Log In?

Answer: Actually, this problem has existed since v2.0 was released.

We have our LoginTimeout OpenUI extension that expires the login when the browser closes.

For those that are still using the mmui.mv, if you place these lines right
after the </HEAD> line in the Begin_Screen function, it will do the same
thing:

<MvASSIGN NAME="l.q" VALUE="{ asciichar(34) }">
<MvEVAL EXPR="{ asciichar(60) $ 'META HTTP-EQUIV=' $ l.q $ 'Set-Cookie' $ l.q $ ' CONTENT=' $ l.q $ 'htscallerid=' $ encodeattribute(s.callerid) $ '; path=/' $ l.q $ asciichar(62) }">

Basically, this overwrites the existing Miva Engine caller id cookie and
sets it to expire when the browser closes.

Answered by Darren Ehlers @ http://www.starbase21.com/

Question:   How do I install the Commerce Library on a Server?

Answer: We have a website that Communitech sent us that will help you install your Commerce Library on the server. The url is

http://www.fgiweb.com/support/text_files/miva_libraries.htm

Answered by Laurie @ Miva Corporation

Question:  On a couple of occassions, I have  visited my site and that message is displayed with a customer's name in it  (not my own). This is a security problem because with the click of a button and no password, that customer's personal profile then becomes available to me. What is the cause and solution to this problem?

Answer: Somewhere, on your main web page, or within your store, is a link that contains a Session_ID A Session_ID, contains other customers info, and when copied, it uses that same info.

To fix this, go to the links that have been created, and hover over them. If
you find a Session_ID, remove the link.

For correct links into your store front, in admin, click on your store name,
and in the top right corner, click on the link button. This will display the
links you can use, without a Session_ID.

In your store front, the checkout, and account button will contain the
Session_ID, that's O.K., they belong there.

Answered by Josh @ Miva Support

Question:  How can I place the Log Out button in Merchant 2.22 in another location?

Answer: You can just take that link at logout : (IE -http://www.yourdomain.com/Merchant2/merchant.mv?Action=LOGO& Screen=SFNT&Store_Code=STORECODE) and make LOGOUT buttons all over the place if you want to.
 

Answered by: Jeremy Russell @ Support Technician - Miva Corporation

Question:  Why can customers only use their login once and it just disappears in Merchant 2.24?

Answer: I haven't seen this reported yet, something I just ran into this morning. There is a serious bug in 2.24 which will prevent a customer from using their login more than one time. What is happening is when the order information is saved, the login for the customer is being blown out, which results in permanently disabling their account.

One of the fixes in 2.24 (and 3.01) was that the logins could not be changed from the account screen before. This has been fixed, but in fixing it they introduced this new bug. This only effects the 2.24 upgrade, not the 3.01 upgrade. The fix is below.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In the Action_Save_OrderInformation function of merchant.mv (line 1485) this line

<MvDO FILE = "{ g.Library_DB }" NAME = "l.ok" VALUE =
Customer_Update( BasketList.d.cust_id, g.Customer_Login, ....

needs to be changed to

<MvDO FILE = "{ g.Library_DB }" NAME = "l.ok" VALUE =
Customer_Update( BasketList.d.cust_id, Customers.d.login ....

That is, g.Customer_Login should be changed to Customers.d.login

Note that there are 3 places this line occurs in merchant.mv. Only the one
in the Action_Save_OrderInformation function needs to be changed. This can
also be fixed with a system module, instead of manually changing
merchant.mv.
 

Answered by Adam Denning