If you look at a recent CCK Wizard, you'll notice a couple things. The first is that using the "Choose file" buttons doesn't result in the new file name being entered into the text field. If you look closely, you'll then notice that it's actually being put in whatever the next previous widget was based on the X,Y coordinates. The cause of this problem is two-fold. The first problem is that the code assumes that any BrowseFile or BrowseDir button targets the immediately preceding widget. The second is that we decided to sort the widget array to implement tab ordering. Once the array is sorted, the knowledge of who was "immediately preceding" (i.e. the preceding widget in the INI file definition) is lost. The simplest fix for this is probably to change the INI files to use TARGET= for all of the BrowseFile and BrowseDir buttons and add code to the wizard machine to handle this.

I fixed this by adding target= parameters to all BrowseFile widgets in every INI file. All BrowseFile widgets must have a target= parameter if a text field should be updated with the result.

Marking this Verified Fixed