Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Migrate File Naming Tokens on Upgrade

Kommentare

4 Kommentare

  • SFA

    Robert,

    The Output Recipes should store the naming conventions by tokens but if you were to change those for a specific recipe and not resave the recipe or use the changes to create a new recipe they may not be retained.

    There are some Dynamic settings that are set in the user related configuration files (plists for Mac users I believe) that may carry dynamic settings per user and per session/catalog. The settings are normally deployed when a session of catalog is opened in order to open it using the same settings as the last time it was closed. 

    I think it is likely that this active, dynamic personalisation is not carried forward on version change and maybe not on update release within a version especially if there could be compatibility issues somewhere.  

     It sounds like an interesting feature request to me. You may want to add it to the Feature Request section of the forum.

     

    0
  • www.shootmachine.co

    It could be an untested consequence of the export redesign, and depreciation of some fields. Token setups are stored in the recipe XML, but the naming and field IDs all changed - they maybe failed to migrate. Maybe make a support case... 

    0
  • Permanently deleted user

    I bet the field ID change had an impact. Thank you both for the backgrounder. It looks like I'm duplicating it by hand, but I'll add a request and hopefully it gets more attention in future versions.

    Cheers

    0
  • SFA

    There was certainly potential that some existing recipes could not work if certain Tokens had been employed in them.

    0

Post ist für Kommentare geschlossen.