Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.While in certain circumstances it could be a security issue, it would be beneficial to be able to directly upload a new JS file from the admin rather than having to upload it & then change the variable; this would allow the task to be delegated to someone who was responsible for the Omniture configuration rather than the site developer.
Comments
Comment #1
gregglesAs long as the ability to do so is controlled by a permission on http://drupal.org/node/475848 - like "administer site configuration" - I see no problem with it.
Comment #2
greg.harveyThis would've been useful for me too. I was supplied with a JS file to host on the site - ended up putting it in the 'js' directory of another module, but it's "out of position", so to speak.
Comment #3
gregglesIt makes sense to me for the module to offer this.
The standard place is becoming sites/all/libraries/omniture/
@greg.harvey or DamienMcKenna - What was the name of the file?
Comment #4
DamienMcKennaThe file is normally named s_code.js.
Comment #5
gregglesComment #6
DamienMcKennaThe documentation might also want to be spruced up to explain how to use the s_account and s.dynamicAccountList variables in the s_code.js file in order to use one file for multiple sites:
Comment #7
egomac CreditAttribution: egomac commentedjust curious if s_code.js can be included using drupal_add_js() so that it becomes part of the aggregated js when the js aggregation is turned on.