Announcement

Collapse
No announcement yet.

UI versions and releases

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    UI versions and releases

    Hi folks,

    I'm working on a set of custom modules that interface a Miva store to the client's back-end server. We have products and categories coming in, and orders going out, as well as some special discounts and product-grouping features. All this requires a lot of changes to the page templates. We're designing it all to work with an out-of-the-box Miva store using CSSUI and the Suivant theme. If the end-users want to customize the look of the store, they'll do it after our customizations are in place.

    I did the installation for the first end-user store in April, and I'm now working on the second one. I've noticed a few differences in the page templates between the first store and the second one. Both stores have the same version numbers for Merchant, as well as for the CSSUI and ReadyTheme modules. So I'm wondering why all the templates aren't identical. Maybe some other user made some changes; I might even have made a few myself, back in April, and forgotten to keep notes. Or, is it possible that some changes have been made to the default, out-of-the-box templates, which wouldn't be indicated by changes to the version numbers?

    As we add more stores, we'd like to be able to streamline or automate the process of adding our customizations, possibly by creating a framework that we can install with a few clicks. But we need to keep track of any changes that occur to the default templates, so we can keep our custom code in synch.

    I suppose the default templates are defined by a number of component modules, not just by MM, CSSUI, and ReadyTheme. Do I have to check the version numbers on all of them in order to know when changes might occur? Are template changes included in release notes?

    Thanks --
    Kent Multer
    Magic Metal Productions
    http://TheMagicM.com
    * Web developer/designer
    * E-commerce and Miva
    * Author, The Official Miva Web Scripting Book -- available on-line:
    http://www.amazon.com/exec/obidos/IS...icmetalproducA

    #2
    Re: UI versions and releases

    Kent Just to chime in, I do wish framework titles contained some kind of version number or creation date.

    I've had the same problem and never found a way to consistently know if I'm using the latest version of the page templates, however, the templates provided with the LSK are usually close to if not the latest version. LSK 9.00004 is available
    Ray Yates
    "If I have seen further, it is by standing on the shoulders of giants."
    --- Sir Isaac Newton

    Comment


      #3
      Re: UI versions and releases

      I guess the best approach is what I suggested already: keep track of which templates my package uses, and watch the version numbers of all the component modules that create them. I assume that, if Miva changes the default template of any component module, they'll bump the version number, just like they would for a change to the Miva Script code. So any time a version number changes, I have to look to see if the template was modified; and if so, update my package to match. Not terribly efficient, but it should get the job done.

      Thanks --
      Kent Multer
      Magic Metal Productions
      http://TheMagicM.com
      * Web developer/designer
      * E-commerce and Miva
      * Author, The Official Miva Web Scripting Book -- available on-line:
      http://www.amazon.com/exec/obidos/IS...icmetalproducA

      Comment

      Working...
      X