Categories

Authors

Pages

Recent posts

Recent comments

Archives

Code version H.21.1 released

Thursday, 22 July 2010 @ 20:49, by Ben Gaines

Some of you may have noticed that code SiteCatalyst version H.21.1 is now available in the Admin Console. (Fewer of you die-hards may have even noticed that JavaScript version history has been added to the release notes!) I have documented some details around the last two JavaScript code updates that we have put out on this blog, and will continue to do so going forward. When I was in our ClientCare organization, a common question that we heard was, “Should I upgrade my implementation to the latest code version, or am I okay to stay put?” Hopefully these posts will help answer that question by explaining the changes clearly.

There were two minor updates in code version H.21.1:

  • We improved ClickMap data accuracy in cases where multi-suite tagging is in use.
  • We improved the way URL encoding and decoding occur in the case of multi-byte characters, in order to work around a bug in older browser versions in the Android OS.

So, how do you know whether you should consider upgrading to H.21.1? You should consider upgrading if:

  • You use multi-suite tagging (see explanation here) and also rely heavily on ClickMap.
  • You have a mobile site that uses multi-byte characters and receives traffic from Android devices.

There you have it. As always, please feel free to submit JavaScript code suggestions at the Idea Exchange; we’re listening! And if you have any questions about this code release or anything else related to the Adobe Online Marketing Suite, leave me a comment or send me a tweet (@benjamingaines).

  • on  
  • Bookmark at  

respond to post

responses

  1. Mitchell Teixeira 2010/7/23 @ 11:12 am

    Hi - thanks for this info and insight! Is there a way to find a change history for all tag versions going back to the beginning?
  2. Ben Gaines 2010/7/23 @ 2:46 pm

    Mitchell,

    Going all the way back to 1996? :) Currently, there isn’t a publicly available single history of JavaScript code updates going all the way back, but if you give me a sense of how far back you need to go, I’ll see what I can do. Your Account Manager should be able to provide information on this as well. Also note that the code history section that we added to the release notes (as of this past release) shows history for the last 10 code releases, I believe.

    Thanks,
    Ben
  3. sibel 2010/8/19 @ 2:22 pm

    Hi Ben,
    When I saw this post, I checked my version. Opppss it is H17. I felt like very old :)
    If I upgrade my code in JS file to this one, I suppose I will not need any change in my tags that I already collect. Do I suppose correct?

    Thanks
  4. Ben Gaines 2010/8/19 @ 4:18 pm

    Sibel,

    Correct. You can swap out the s_code.js file to go from H.17 to H.21.1 without changing your individual page tags.

    Thanks,
    Ben
  5. Stefanie 2011/5/11 @ 10:14 am

    Hello
    Is upgrading tags a simple job of copy and paste or does it require more thought?
    Regards
    Stefanie
  6. Ben Gaines 2011/5/13 @ 10:22 pm

    Hi Stefanie,

    In most cases, you can upgrade to the latest version of code by copying and pasting any customizations you’ve made in your s_code.js file into a newer version, then saving and publishing. (There are exceptions to this rule, which I may cover in a future blog post.)

    We strongly recommend testing all JavaScript code upgrades prior to publishing in a live environment, to ensure compatibility. We also typically recommend not upgrading unless there are features/fixes that are relevant to your business in the newer version.

    Thanks,
    Ben