Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 3 of 3

Thread: How to add custom build number in page details

  1. #1
    addi is offline Junior Member
    Join Date
    Sep 2007
    Posts
    27

    Default How to add custom build number in page details

    All -

    I am using ML 7.0.1.1 (VB w/code) and have had some custom development work done, with more on the way We would like to add a variable, such as "Custom Build Number", such that we can track it once the release is deployed, similar to how it works out of the box with ASPDNSF under page source.

    <!--
    PAGE INVOCATION: /default.aspx
    PAGE REFERRER:
    STORE LOCALE: en-US
    STORE CURRENCY: USD
    CUSTOMER ID: 0
    AFFILIATE ID: 0
    CUSTOMER LOCALE: en-US
    CURRENCY SETTING: USD
    STORE VERSION: AspDotNetStorefront ML 7.0.0.7/7.0.0.7
    CACHE MENUS: true
    -->


    Where does this information come from? I have attached a sample image to help.
    Attached Images Attached Images  

  2. #2
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    That's stuck on the page by the (!PAGEINFO!) skin token. Changing that would require some changes in the Parser.cs class.

    You could always just use the (!STORE_VERSION!) token and change your StoreVersion AppConfig to something other than the default version number.

  3. #3
    addi is offline Junior Member
    Join Date
    Sep 2007
    Posts
    27

    Default

    Thanks Scott. Updating !STORE_VERSION! via Admin Master would do just fine. Less custom code, the better.