View Issue Details

IDProjectCategoryView StatusLast Update
16WADFCorepublic22 Feb 2008 13:30
Reportermrosenquist Assigned Totimj  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version0.6.5Fixed in Version0.6.5 
Summary16: The .wadf-instance file gets corrupted when deploying with macros including %%
DescriptionIf there are macros defined using the %% syntax, these are prompted for and then added to the .wadf-instance file upon deployment or reprocessing.

However, the code which then adds these values to the .wadf-instance file has a bug and corrupts the .wadf-instance file by appending the first defined option to the end of the first line (which is supposed to be the instance file)

This has a knock-on impact on deployments in general including crontab deployments, subsequent reprocesses etc.
TagsNo tags attached.

Activities

timj

17 Feb 2008 11:53

manager   ~12

I think this may be due to using an old WADF version

timj

22 Feb 2008 13:11

manager   ~18

Fixed in r969

Issue History

Date Modified Username Field Change
12 Feb 2008 11:52 mrosenquist New Issue
12 Feb 2008 14:06 timj Target Version => 0.6.4
12 Feb 2008 14:06 timj Status new => assigned
12 Feb 2008 14:06 timj Assigned To => timj
17 Feb 2008 11:53 timj Note Added: 0000012
17 Feb 2008 11:53 timj Status assigned => feedback
17 Feb 2008 12:04 timj Target Version 0.6.4 =>
22 Feb 2008 12:56 timj Status feedback => assigned
22 Feb 2008 12:58 timj Summary The handling of crontab uses the incorrect site id as it uses all the content from the .wadf-instance file => The .wadf-instance file gets corrupted when deploying with macros including %%
22 Feb 2008 12:58 timj Description Updated
22 Feb 2008 12:59 timj Target Version => 0.6.5
22 Feb 2008 13:11 timj Status assigned => resolved
22 Feb 2008 13:11 timj Fixed in Version => 0.6.5
22 Feb 2008 13:11 timj Resolution open => fixed
22 Feb 2008 13:11 timj Note Added: 0000018
22 Feb 2008 13:30 timj Status resolved => closed