Images not getting loaded openerp 6.1 webclient with postgres 9.1 in windows

[kalmen]

Hi,

When I install OpenERP Server with postgres 9.1 in windows, Home page Images not getting loaded in openerp webclient .

When I check the Image view It shows

 "data:image/png;base64,x6956424f5277304b47676f414141414e5355684555674141414751414141426b43414141414142566
...............

Image cannot be displayed because it contains errors ".

I have tested from windows 2003 , PostgresSQL 9.1.5 to AWS windows 2008 , PostgresSQL 9.1.5 ,
i t has the same problem .

~ i have tested both 32 bit and 64 bit of postgressql on 64bit AWS windows 2008 , SAME PROBLEM
~ i have tested edit the field ,in the ir.menu table , it is also not working .

However, i can quite sure that after insllation or restore of db , the database saved into the
ir.menu fields is not correct ,

My suspect to this issue when i use Chrome to display and confirm my thoughts ,

1. data:image/png;base64,x6956424f5277304b47... , it cannot display properly.

2. data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAGQAAABkCAMAAABHPGV .... , THIS is from the working
    version which display the same image icon , SALES
3. check the content of the field in the ir_ui_menu.

As I can see that the data after BASE64 is different , so i went to the postgresSQL field and check the content of the field ir_ui_menu.web_icon_data , and COPY the data in the field and tested it and confirmed that it restored correctly and the data CAN display the image. So the data in the postgresSQL data is correct.

then finally , i can be sure that OPENERP when it trying to display the content , it somehow miss interpreted the base64
image to something else.

Looking for a fix.

Thanks

[Amit Bhavsar (Open ERP) (amb-openerp)]

Hello Kalmen,

I have checked your Issue with latest revision, But It's working fine. That's why I have attached the screen-sort. would you please check it and notify us where you have faced the problem.

Thanks and waiting for your reply!

[Mario Arias (the-clone-master)]

Hi,

Go to postgresql.conf and replace the line

#bytea_output = 'hex' # hex, escape

with:
bytea_output = 'escape' # hex, escape

Regards,
-Mario

[RASHIK EP (rashikep)]

Thanks to Mario Arias...!

Your post solved my issue exactly..!

Regards,

Rashik

[kalmen (kalmenchia)]

Yes , i have flag this bug as invalid , as this is not a setting from postgres.
Thanks , Mario & Amit.

Regards,
kalmen.

[Geoffrey Guerrier (geoffrey-guerrier)]

Thanks a lot of Mario Arias.
I was on this problem since 1 year.