v8.0rc1 - Blog Module - Can't change the header background image.

[adfra]

When creating a new blog entry the website builder does not save the settings related to the Heading background image. So effectively the blogging functionality as such is not usable at the moment.

Version v8.0rc1

[mart-e]

Hello,

It works fine on my side, can you give more detail on the flow you are using ? You are using the "change cover" button ? Got any error (web or server side) ?

Thanks

PS: saying the blog module is not usable because you are unable to change one image is probably a bit excessive...

[russell07]

I have issues with this aswell. After clicking "Change cover" and selecting an image, the "Save" button does not respond and the dialog stays open

Platform: Mac OS 10.9.3 Safari Version 7.0.4 (9537.76.4)

[mart-e]

@russell07 you are using the latest v8, right ? Do you have any error in the web console of your browser ? Can you reproduce it on other browser or only safari ?
Thanks

[wtaferner]

@mart-e
Seems to be a duplicate of #2470...
Javascript Problem: Uncaught TypeError: Cannot read property 'nodeName' of undefined...and the reason seemed to be remove() instead of hide()

[mart-e]

@wtaferner Not sure, the #2470 was about the wizard not opening. Here it seems it's the popup not closing.

[wtaferner]

@mart-e
Hmm, not sure too, but by now I can not reproduce it on my side...maybe @russell07 and @adfra can try to reproduce it with the latest version again and give feedback here.
Thx for the fix. I have shortly reported some showstopper with screenshots on "website_sale" which are most likely hot...maybe you can tag/assign them...

[adfra]

Hi there,

My instance will get upgraded to the latest v8 on Tue.
Happy to give it a go then and report back.

Thanks,
Frank

On Saturday, September 20, 2014, Wolfgang Taferner notifications@github.com
wrote:

@mart-e https://github.com/mart-e
Hmm, not sure too, but by now I can not reproduce it on my side...maybe
@russell07 https://github.com/russell07 and @adfra
https://github.com/adfra can try to reproduce it with the latest
version again and give feedback here.
Thx for the fix. I have shortly reported some showstopper with screenshots
on "website_sale" which are most likely hot...maybe you can tag/assign
them...

—
Reply to this email directly or view it on GitHub
#2480 (comment).

---

Frank C. Adler

Checkd - Buy with Confidence.
16 Loch Street, Yarraville, VIC 3013
ABN: 96 131 204 763

M: +61 4 0826 4615
E: frank.adler@checkd.com.au
W: http://www.checkd.com.au

This message is private and confidential. If you have received this message
in error, please notify us and remove it from your system.

[infomate]

I have a very peculiar problem with the Blog post.
First the "Change cover" button is always displayed on the upper right corner of the background image. So I thought that by upgrading to the latest code (Master) from github might solve the issue. I upgrade website_blog only but the background image does not appear anymore except for about an inch of black background with the "Change cover" still on the upper right corner.
I tried to download website_blog including the dependencies website_mail, website_partner and knowledge. Updated my module list then tried to upgrade website_blog.
The upgrade trows-out an error (which I wasn't able to capture) and breaks the whole web client with a Server internal error 500.
The only way to get it back running is by deleting website_blog from /addons.

[mart-e]

@infomate I don't advice to run master code (except for testing purposes), stick to branch 8.0.
When you have 500 errors like this, please post the error you get in your logs.

[russell07]

@mart-e Yes I have just tried it on a brand new Odoo Trial SaaS instance and have the same problem in Safari on Mac (problem doesn't exist in Chrome). I've also notices the same issue on other buttons in the Odoo front end when using Safari on Mac. Below is the error in the JS console. Apologies for not sending this before. Note the "19" increments each time I try to click the button.

[Yenthe666]

Hey everybody,

This problem can no longer be reproduced on the latest source code of Odoo 8.

Regards,
Yenthe