Adding file content overlays by script

Comments

• rbtwhiz Posts: 2,179

  September 2013 edited September 2013

  // The absolute path of the source file
  var sSourceFileAbsPath = "";
  
  // The absolute path of the loader file
  var sLoaderFileAbsPath = "";
  
  // Create a db content instance object
  var oContentInstance = new DzDBContentInstanceTable();
  // Fetch db content instance objects for the source file
  var oDBObjectList = oContentInstance.fetchByPath( sSourceFileAbsPath );
  // If there are any instances
  if( oDBObjectList.length > 0 ){
   // Get the first one
   oContentInstance = oDBObjectList.at( 0 );
   // Get the content object that this is an instance of
   var oContent = oContentInstance.getContent();
   // Fetch the record
   oContent.fetch();
   // Get the content type id
   var nTypeId = oContent.contentType;
   
   // Create the instance record for the loader file; creates the content record if needed
   oContentInstance = oContentInstance.createFromPath( sLoaderFileAbsPath );
   // If we have a database object; the CMS is running
   if( oContentInstance ){
    // Get the content object that this is an instance of
    oContent = oContentInstance.getContent();
    // Set the type on the file
    oContent.contentType = nTypeId;
    // Notify everything that is listening of updates
    oContent.update();
   }
  }

  -Rob

  NOTE: You will need to refresh the Content Library Asset View to see the change.

  Post edited by rbtwhiz on September 2013
• Richard Haseltine Posts: 96,849

  September 2013 edited December 1969

  Thank you, I was expecting it to be much more complex.
• Richard Haseltine Posts: 96,849

  September 2013 edited December 1969

  OK, that works - but as feared from having to feed in the absolute paths, it works only if the content is in the content folder I installed to, which it isn't a I install to a working folder, make sure everything is working, and then move to the real folder (the intent being to keep relative paths intact). That's a bit of a pain, though for myself I could live with uninstalling and reinstalling after testing (assuming there were no bugs I needed to fix, at least) but that's a bit of a performance to make available to others. If I add the original absolute path to my loader script, so that the script for copying the overlay has both the original, stored in the DB path and the current, obtained from DzContentMgr via the relative path, locations is there a way to update the record for the main file so that it points to the current location and not to the temp install folder? That is

  Given:
  install content directory
  current content directory
  relative path

  Can I:
  update CMS to use current content directory/relative path instead of install content directory/relative path without breaking the rest of the CMS record?
• rbtwhiz Posts: 2,179

  September 2013 edited December 1969

  // The original base path of the file(s)
  var sSourceBasePath = "";
  // The new base path of the file(s)
  var sTargetBasePath = "";
  
  // Create a db content folders object
  var oDBContentFolder = new DzDBContentFoldersTable();
  // Get a content folder for the source base path; don't create it if it doesn't exist
  var oDBSourceContentFolder = oDBContentFolder.findContentFolder(sSourceBasePath, false);
  // Get a content folder for the target base path; don't create it if it doesn't exist
  var oDBTargetContentFolder = oDBContentFolder.findContentFolder(sTargetBasePath, false);
  // If we've got a source content folder and a target content folder
  if( oDBSourceContentFolder && oDBTargetContentFolder ){
   // Replace all occurances of the source base path with the target base path
   oDBContentFolder.replaceAllMatchingBasePaths(oDBSourceContentFolder.basePathID, sTargetBasePath.basePathID);
  }

  This is equivalent to navigating to a Category or Product in the Content Library pane, right clicking in the Asset View and choosing Database > Edit Base Path(s)...

  -Rob
• Richard Haseltine Posts: 96,849

  September 2013 edited December 1969

  OK, thank you, that should help - though it does appear that it will be a universal replace, which would work OK for me but might not be for other users.
• rbtwhiz Posts: 2,179

  September 2013 edited December 1969

  The question prompted me to look at the DzDB* wrapper classes. I noticed that the DzDBContentFoldersTable wrapper was missing a few more recent functions that provide individual file/directory access. I've added those functions to the wrapper, but you being able to access them obviously requires a new build. Right now that means it won't be available until a build after the 4.6.1.14 Release Candidate transitions to General Release. As the additions pose very little risk, IF we end up needing to address any show-stopper bugs in the RC, I'll merge them into the 4.6.1.x branch for the build... otherwise you'll have to wait for the next release cycle. Obviously, once you have that build and you use said function(s), the users of your script must be running the version [or later] that provides the access... which means you should guard against an earlier version; see this example.

  -Rob
• Richard Haseltine Posts: 96,849

  September 2013 edited December 1969

  Thanks Rob - I was wondering the other day how to get a human-friendly version number from the raw value.