Jump to content

Hadrian

Registered Users - Approved
  • Posts

    135
  • Joined

Posts posted by Hadrian

  1. Yeah this is a mess and I'm certainly not making changes to the .ini file every time it comes up since we have 34 recurring templates for MCC as well. I am virtualizing Lion or Mountain Lion and running it that way until PTI sorts this business out. Thanks for the help Dan and the effort on the workaround.
  2. Can you elaborate on how to edit the fonts.ini file? I'm having the same issues. What exactly needs to be changed? I can change the name in the first column, but then I can't select it from the font menu. It reverts back the previously selected font when I try.

     

    If someone could fill in the blanks here that would helpful. Having the same issue.

  3. You can call the ExternalDataFileEx() and comment it out. Marcom looks for that function in order to enable the External Data File area in the configuration tab in the manager. Once you upload a template that contains this function (even if commented out) you can associate your external .js file to the product.

     

    Nice. So I assume this is allowed since the External Data Files library allows us to upload javascript files?

  4. In theory one could have a dummy ExternalDataFileEx() in a callback rule and that would do the trick. Do not know if PTI would consider this a messy hack since I have never seen/heard of it being done until now.....Anyone from PTI care to chime in before a couple of us start using this method?????
  5. Figured out why it does not work for you all......I have two external files I am loading. One is a tab delimited file that looks up sku numbers and the other is the actual .js script file. I am mapping the first file because I am using ExternalDataFileEx() but the second file is a raw .js script and therfore cannot be read by itself...meaning you need to have an actual ExternalDataFileEx() function or object in a callback rule. The trick here is that since i am using an actual database file the rest of the External Data Files library becomes visible and therefore can be mapped. This is simply pointing the template to the .js file in the same manner the FP Creator would if you had the .js in the same directory as the template. Make sense?
  6. To be clear I have a bunch of functions in the .js file that are returned in a series of rules in the template.

     

    1. load the file using the OnJobStart in the FP template.

    //OnJobStart
    Load("Globals.js")
    

     

    2. I used the MC External Data Files library to upload. I loaded the .js file as is no changing the extension.

     

    3. Make sure you map the external data file in the configurations file tab in the Manager template.

     

     

    Make sense?

  7. Working on my end in Marcom Central. No issues that I can see. Loaded the .js file to the external data files library, made sure to map it in the configuration settings of the template, and tested the template with the javascript file mapped and unmapped to make certain it was not catching any legacy settings. Pretty cool to be able to load the bulk of my rules in case I need to make a some quick changes and not have to republish every time...Thanks PTI...
×
×
  • Create New...