Inconsistent use of bold tag

[wcw]

In previous versions of Merchant on the product page the labels code, quantity in basket price, etc were standard weight. Then the value was bold. In the 5.5 css framework, it is exactly opposite. The labels are bold. The values are standard. Was this a mistake? Will it be fixed? Was this intentional? Is there a variable that will return the API version?

[Dave Slifka]

Re: Inconsistent use of bold tag

Bill,
This is an intentional design choice.

Is there a variable that will return the API version?

Can you clarify this question please?

[wcw]

Re: Inconsistent use of bold tag

What variable in merchant.mvc and admin.mvc can we check to see what api version the store is using. When I put this on the page:
TEST: &mvt:global:Merchant_API_Version;
it reports 5.00.

[wcw]

Re: Inconsistent use of bold tag

In addition to needing the correct value for the Merchant_API_Version, can you make a global variable that reports which framework is installed?

[Alex Kruglyak]

Re: Inconsistent use of bold tag

Hi Bill,

Merchant_API_Version is the variable you'd use to check the API version.
Currently it should report 5.00.

As we discussed at the conference, aside from the Frameworks/Dreamweaver features, the admin/merchant API should not change with MM5.5 release.

If you were referring to runtime, the CSS framework will not be released at MM5.5 launch and we will continue to adjust it until it's consistent with MMUI.

Thanks,

Alex

[Alex Kruglyak]

Re: Inconsistent use of bold tag

In addition to needing the correct value for the Merchant_API_Version, can you make a global variable that reports which framework is installed?

This is something that we are still working on. It probably won't be available at launch, however it will be available when the CSS Framework is released.

[wcw]

Re: Inconsistent use of bold tag

I thought the API version was going to be used to determine if modules contained new functions which would be used in 5.5 so it would not try to run those functions in a module that listed 5.0 as its API.

Since the installed framework effects what example code a module might put in its templates when it is installed, it is necessary to know what that framework is. Hence, the need for a variable. It would be nice to know what that variable is now so that we can make changes in module code as we update them before the beta is over and the css framework is released. We have a nice lead time now, but won't a month from now.