Conversation
|
Thanks for the PR. May I ask what you tested ok on Ooo v8 if you couldn't get a working example ? A excerpt from the error could help, I can't remember if you can get it in the JSON answer from the server. The runbot logs are available easily on the each instances in the buttons provided next to the live test button. Anyway, I'll look into this next week. There are probably ways to probe the server for the correct format. And I can't remember if in 7.0 this argument was required, so maybe this could be tested also. |
|
I was only able to test the I'll check the logs and see what is the issue with the example. I confirm that the I also wanted to make a more clean way to do it, for example by probing Odoo as you said, but I currently don't know if there is a method to do it, with or without being authenticated. But since the authentication seems to work without the |
|
Okay, I figured that we can use the |
|
The automated legacy mode is working, however I've still an Odoo server error on 7.0 runbots that I can't check. The logs on the runbot page are only containing INFO logs regardless of what filter I choose. The 8.0 is working fine tho. |
I fixed the
session_idbug encountered with Odoo 8.0+ by adding alegacyboolean (falseby default) in the constructor. If the legacy mode is enabled, thesession_idattribute will be added to the JSON requests.I tested it on the
107189-8-0-38c9deOdoo 8.0 runbot and the connection works. I couldn't test further because I couldn't get a working example (even with the one you provide, so I guess that it comes from the runbot), I get a Odoo server error that I'm not able to check.If you know how to see the runbot's logs then tell me and I will check what is causing this error, but it's not from me, the merge will just be safer.