Who Me Too'd this topic

Who Me Too'd this topic

Silver Contributor
Silver Contributor

Hi,

 

The new javascript code extension has changed the way things get published. I get the changes and it is a nice addition but the workflow brings a nuissance with it.

I have created a tag (Doubleclick) which fires on each page. I also created a new javascript code extension scoped to this tag which does some basic things. The first publish works fine and the code gets executed. The problems start whenever I make a change to the extension(and add this change into the publish queue) and publish a new version (using save as). In the publish dialog it allreay mentionnes that no changes are to be published. After the publish is done I never get the updated extension code. It seems that the tag where this extension is scoped to needs to be updated in order for Tealium to see the changes for this extension. If I make a trivial change in the tag (clicking the edit button after which the publish button turns orange) and then publish , only then the updated extension code is available. The tag is not bundled so it would request the new utag.id.js file when doing the publish but this does not seem to hppen unless the tag itself is updated.

I am not sure if this is intended behavior but it really is inconvenient from a workflow perspective.

I hope this either gets fixed or that this gets documented somewhere so that other users are aware of this problem and don't loose precious time figuring this out by themselves.

 

Grts

Who Me Too'd this topic