&mvt:global:Merchant_API_Version; is showing 5.51. It would be of great help if this number would reflect a new API version.
I am trying to modify modules to work with the new API (address 2 at present). But having to test the structure of databases to see if the API has changed is highly inefficient. The API global variable needs to be changed so we can have a quick switch in our code to run functions based on the current features.
For things like display of line 2 it can be done with a simple test of the variable value. But when you are doing things like order export to flat file, it is imperative you know up front if there is a addr2 in the database. The export has to setup a column for the 2nd address line.
For merchant.mvc I can fake it with a tool kit variable assign in the global header. But that is not the case with admin.mvc. Help guys. Can we get the Merchant_API_Version incremented to a new number ASAP? What will that number be so I can start writing code to use it?
I am trying to modify modules to work with the new API (address 2 at present). But having to test the structure of databases to see if the API has changed is highly inefficient. The API global variable needs to be changed so we can have a quick switch in our code to run functions based on the current features.
For things like display of line 2 it can be done with a simple test of the variable value. But when you are doing things like order export to flat file, it is imperative you know up front if there is a addr2 in the database. The export has to setup a column for the 2nd address line.
For merchant.mvc I can fake it with a tool kit variable assign in the global header. But that is not the case with admin.mvc. Help guys. Can we get the Merchant_API_Version incremented to a new number ASAP? What will that number be so I can start writing code to use it?
Comment