Store_Module_UI:code variable missing in admin

[wcw]

In runtime merchant.mvc the variable Store_Module_UI:code tells you if the store is running mmui or cssui. That seems to be working fine. However, in admin.mvc, there is no global variable to tell you what the store is using for the UI. I suppose we could do some database lookup, but I think it would be far better if that was a standard variable. Otherwise we could have dozens of different modules in a store admin having to do the same lookup. The admin screen and even the module install/update functions are dependent on which UI is in use so it is a variable most modules need. Please add it to the admin.

[wcw]

Re: Store_Module_UI:code variable missing in admin

I just realized, there is another problem with this. There is no layout tab or any other easy way for a store owner (or a developer working on a store) to know whether a store is using mmui or cssui. Since the templates are totally different I have to have two versions of example templates. But I can't just tell the owner/developer, "if your store has mmui, use this template and if your store has cssui, you that template." In 4x I was able to tell the owner to go to the layout tab and tell me which is assigned. So not only do we need Store_Module_UI:code to be available in admin, but we have to display somewhere in admin which UI is in use.

[Rick Wilson]

Re: Store_Module_UI:code variable missing in admin

It's under store settings.

[Kent Multer]

Re: Store_Module_UI:code variable missing in admin

BTW, the behavior that Bill describes is also true for some other global variables. g.Store_Module_Currency, I think, is another one that's an entire structure in merchant.mv, but a simple variable in admin.mv. It does get confusing, and I don't think there's any documentation for these anomalies. I suppose Store_Module_Tax might have the same issue?

Thanks --

[wcw]

Re: Store_Module_UI:code variable missing in admin

It's under store settings.

Never thought to look there. That solves the ability to ask the store owner what they have. Now if we could get that variable, we could have modules do certain tasks depending on the UI. With the built in modules there is a different component module installed based on the UI in the store. But I'd rather not write and sell two different modules that do the same thing with just UI differences. Two tool kits, two power search, etc. would get confusing. Folks would be buying the wrong one and need an exchange. Hence, all the code needs to be in one with branching depending on the UI. In merchant.mvc there is a global variable. I have not found one for admin.mvc.

[Rick Wilson]

Re: Store_Module_UI:code variable missing in admin

I'll find out from Jon tomorrow about getting a variable.

[wcw]

Re: Store_Module_UI:code variable missing in admin

Thanks.