[bug] null blob field displays view/download icons

[claudiobosticco]

SmartClient Version: v8.3p_2012-12-20/PowerEdition Deployment (built 2012-12-20)
and
v8.3p_2013-01-02/PowerEdition Deployment (built 2013-01-02)

chrome 23.0.1271.101 on Mac OSX

a null blob field displayed in a grid shows the view and download icons (which obviously will open blank windows)

[Isomorphic]

Read the binary fields overview - we decide whether there's a file available based on whether the filename metadata field is null.

[claudiobosticco]

I beg your pardon, I didn't specify that actually the filename also is null.

[claudiobosticco]

and if I switch back to v8.2p_2012-10-02 it works correctly.

[claudiobosticco]

I managed to make a sample in the showcase: try to add this code to the 'listGrid' object in the #customBinaryField sample:

dataProperties:{
  transformData:function (newData, dsResponse){
    return newData.map(function(item){
                                   tem.file_filename = null; 
                                   return item;
                                });
  } 
},

and the result is as in the attached image

[Isomorphic]

This problem was a regression introduced in June last year. It is corrected now for 3.1p and 4.0d builds - the fix will appear in nightly builds as of tomorrow (January 4). Thanks for the bug report.

[claudiobosticco]

I can confirm it's fixed, thank you very much.

btw, now warning messages appear in the developer console:

11:40:18.390:MUP1:WARN:ListGrid:passaggiDiStatoPerContrattoGrid:dynamicContents eval error - returning empty string for block -->${viewer.getSummaryTitle(field)}<-- error was: {}

for every field of every grid

[Isomorphic]

Are those warnings definitely something that only started happening with today's build, or were they also present in earlier builds (your original post mentions using builds from December 20 and January 2)?

[claudiobosticco]

they were also present with v8.3p_2013-01-02 build, but not present with v8.3p_2012-12-20 build

[Isomorphic]

OK, it seems apparent that this must be something to do with using out-of-date locale files. Does that observation make the problem obvious to you?

[claudiobosticco]

Yes, that was the problem! Thank you very much!