v6 submenu doesn't work if there is a diagram view

Bug #611631 reported by GEM
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Web Client
Fix Released
Undecided
Jiten (OpenERP)

Bug Description

if I have a diagram at the screen, and I clic on the left menu to have submenu, submenu doesn't appear (same problem before the merge).
Promise, my last report ;)
Bye

Revision history for this message
Navrang Oza (noz-tiny) wrote :

Hi GEM,

Can you check that in trunk after merge, is it working or not ?
Or if you provide path then we can check.

Thanks.

Revision history for this message
GEM (nimp3) wrote :

I tested with trunk branch before and after merge 26-28, same problem (with trun dev too).
Sorry..
Bye

Revision history for this message
Navrang Oza (noz-tiny) wrote :

Hello,
You are talking about which diagram ?
How can we generate this bug ?

Thanks.

Revision history for this message
GEM (nimp3) wrote :

Hi,
it's when I use the diagram view button, by example :
administartion->customization->workflow definition->processus
I push buton diagram view at the top on the right of the page.
(sorry for the time to answer)
bye

Changed in openobject-client-web:
status: New → Confirmed
assignee: nobody → Jra (Open ERP) (jra-openerp)
Revision history for this message
Jiten (OpenERP) (jiten-openerp) wrote :

Hi GEM,

Its fixed with revision no:2999
<email address hidden>

Thanks.

Changed in openobject-client-web:
status: Confirmed → Fix Released
milestone: none → 6.0
Revision history for this message
GEM (nimp3) wrote :

Hi,
tested with trunk-web-dev rev 3629,
and always the same problem for the tree in submenu.
does your modification of rev 2999 of trunk branch is in trunk-web-dev too ?

Revision history for this message
Navrang Oza (noz-tiny) wrote :

You can check in trunk only.
We are not using trunk-dev-web now.

Thanks.

Revision history for this message
GEM (nimp3) wrote :

Hi Noz,
I 'm looking dates of last revision on trunk web dev and understood now I should use just trunk.
But as I said on this post, for trunk, the config file folder of sources on launchpad and downloaded with bazaar is missing (i use this of trunk web dev), but now service openerp web with last sources can't be run in control panel\administration tools\ services (same problem than with 5.0.12 and windows xp), see this bug :
https://bugs.launchpad.net/openobject-client-web/+bug/622712
and
https://bugs.launchpad.net/bugs/599373
hope this will be solved, because I can't answer to all the answer to my bug I posted before my holidays.
To be continued.
Bye

Revision history for this message
Navrang Oza (noz-tiny) wrote :

Yes, I confirmed.
Config folder has been removed by mistake.

Thanks.

Revision history for this message
Navrang Oza (noz-tiny) wrote :

Sorry,

Its not removed, but moved in doc/openerp-web.cfg
Thanks.

Revision history for this message
GEM (nimp3) wrote :

during the build, the build do an error and stopped with message :
error in script "..\setup.nsi" on line 161 :
in fact in client-web\win32\setup.nsi line 161 :
File "/oname=openobject-web.cfg" "..\config\openobject-web.cfg"

change config by doc or you will put a folder config ?

Revision history for this message
GEM (nimp3) wrote :

other precision, in script .nsi, the name of config file is openobject-web.cfg, in sources it is openerp-web.cfg (I'm lost sometimes with openerp/openobject too :) )

Revision history for this message
GEM (nimp3) wrote :

I tested with last revision and now it's ok
(sorry for the time to answer holiday + I couldn't build client v6 for windows since more 3 weeks, because script setupt.py has been change (doesn't work for build for windows actually), some names in script .py have change (openobject-web becomes openerp, openobject_web becomes openerp_web, use in path '/'' instead '\\' for windows, in folder win32 ....), I build actually with all corrections of scripts (but for folders addons and openobject I just corrected name openobject-web), and I use script setup.py of v5.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.