shawn Posted October 29, 2010 Report Share Posted October 29, 2010 I've recently created a couple new jobs for apps that don't have exposed versions. I posted on this same issue recently on another thread, but can't find it. I'm trying to use the datestamp of the file from the URL to compose a version number, which I use for file naming. The issue is that on NEW jobs, before the app is downloaded the first time, this pattern will not work in the version variable assignment: {f:yyyy}{f:MM}{f:dd} Now, I can get around this by using that pattern directly within the "save as filename" box. But then the version variable as exposed in the columns appears to be one version behind each time, which forces another update ad infinitum. Some of these are very large files, so it's a huge waste of bandwidth. I *really* want to be able to use the timestamp from the Last-Modified header (formatted as yyyymmdd) stored in a "version" variable. Is there another method of obtaining what I want? Any recommendations welcome. Link to comment Share on other sites More sharing options...
Tomorrow Posted October 29, 2010 Report Share Posted October 29, 2010 I've recently created a couple new jobs for apps that don't have exposed versions. I posted on this same issue recently on another thread, but can't find it. I'm trying to use the datestamp of the file from the URL to compose a version number, which I use for file naming. The issue is that on NEW jobs, before the app is downloaded the first time, this pattern will not work in the version variable assignment: {f:yyyy}{f:MM}{f:dd} Now, I can get around this by using that pattern directly within the "save as filename" box. But then the version variable as exposed in the columns appears to be one version behind each time, which forces another update ad infinitum. Some of these are very large files, so it's a huge waste of bandwidth. I *really* want to be able to use the timestamp from the Last-Modified header (formatted as yyyymmdd) stored in a "version" variable. Is there another method of obtaining what I want? Any recommendations welcome. Hmm yes i have sometimes noticed this behaviour too.I use {f:dd}.{f:MM}.{f:yyyy} .After update the old date is displayed in version column.After another update or Ketarin restart and update it will change to correct date. Have not noticed any infinite update cycle tho. Link to comment Share on other sites More sharing options...
floele Posted October 29, 2010 Report Share Posted October 29, 2010 Since "f" refers to the currently existing file, it will always be "one off", that is, refer to the date of the previous (that is, existing) file. Link to comment Share on other sites More sharing options...
Tomorrow Posted October 29, 2010 Report Share Posted October 29, 2010 Since "f" refers to the currently existing file, it will always be "one off", that is, refer to the date of the previous (that is, existing) file. So if a new file is downloaded and i recheck this app then the value should be updated in Version column? Link to comment Share on other sites More sharing options...
floele Posted October 29, 2010 Report Share Posted October 29, 2010 Yep. Link to comment Share on other sites More sharing options...
shawn Posted October 29, 2010 Author Report Share Posted October 29, 2010 Is there another method of getting the correct value for the first iteration? Maybe a different way to handle {f:*} that utilizes a temp filename or something so the date can be preserved? If I share these jobs with others, using the "f:*" functionality, they won't work. At least not until the job successfully creates a file the first time, which means users are likely to assume the job is broken instead of follow whatever funky instructions are necessary to ensure that the app is consistently downloaded. I guess I could write a step variable that handles these situations by stripping ":" out of the version...but that seems like an unnecessary step. Link to comment Share on other sites More sharing options...
floele Posted November 28, 2010 Report Share Posted November 28, 2010 I will add a change to the next version so that the "current" file date (actually, {f:*} was meant to support that) will also work in textual variables, and thus your first attempt (which I believe did not work because of an invalid file name error mesage because the f variables could not be resolved) should work fine. Link to comment Share on other sites More sharing options...
shawn Posted November 28, 2010 Author Report Share Posted November 28, 2010 Thank you, Flo! Link to comment Share on other sites More sharing options...
appyface Posted November 2, 2014 Report Share Posted November 2, 2014 Ressurecting an old thread... For some time now, first time download using textual content variable {f:yyyy}{f:MM}{f:dd} for 'vers' column shows 16001231. When download ends, still shows 16001231. I also use 'vers' variable in downloaded filename, and the downloaded filename has the correct file date as part of the name. Request a force download and 'vers' column temporarily changes to show correct date during the download. When download is complete 'vers' column again shows 16001231. The downloaded filename still has correct file date as part of the name. Possible to fix the display in Ketarin to show the correct file date? Link to comment Share on other sites More sharing options...
floele Posted November 16, 2014 Report Share Posted November 16, 2014 Can you send in the XML of your application so that I can check? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now