Connector fails to install on clean 6.1 database with no demo data

Bug #988953 reported by ValdecDev on 2012-04-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenERP-Asterisk connector
Undecided
Unassigned

Bug Description

Steps to replicate:
- New 6.1 Database (bzr pull-61 26th April)
- Install CRM
- Install Sales
- Install click2dial

Error:

12-04-26 15:31:12,833 2697 ERROR astInstTest openerp.tools.convert: Parse error in /srv/openerp/<..path..>/openerp-6.1/addons/asterisk_click2dial/security/asterisk_server_security.xml:33:
<record id="group_asterisk_cid" model="res.groups">
    <field name="name">Asterisk CallerID</field>
</record>

... < .. more traceback ..>

 File "/srv/openerp/6.1/openerp-tools/server/6.1/openerp/osv/orm.py", line 1448, in _validate
    if not fun(self, cr, uid, ids):
  File "/srv/openerp/work/<..path..>/openerp-6.1/addons/asterisk_click2dial/asterisk_click2dial.py", line 322, in _check_validity
    plom = check_string[1].encode('ascii')
AttributeError: 'bool' object has no attribute 'encode'

Alexis de Lattre (alexis-via) wrote :

It should be fixed in rev 33. Sorry for this bug ; it's my fault :)

Changed in openerp-asterisk-connector:
status: New → Fix Committed
Ramón Lozano (ramoncio) wrote :

I get the same error with OpenERP 6.0 and sources from lp:openerp-asterisk-connector/6.0
Maybe this fix was just applied to the 6.1 branch?

Ramón Lozano (ramoncio) wrote :

This is the error log, I forgot to attach it. Very similar to Alexis report:

  File "/usr/local/lib/python2.6/dist-packages/openerp-server/addons/asterisk_click2dial/asterisk_click2dial.py", line 323, in _check_validity
    plom = check_string[1].encode('ascii')
AttributeError: 'bool' object has no attribute 'encode'

Alexis de Lattre (alexis-via) wrote :

Yes, I forgot to backport it to the 5.0/6.0 branch. It is not fixed in rev 33 of that branch.

Ramón Lozano (ramoncio) wrote :

Hi Alexis, I just noticed you are the developer of this addon.
Thanks for your great work!

Are you planning to backport it to 6.0 branch?

If we want full spanish translations we need 6.0, or wait until 6.1 translation is more complete.
I tried it with 6.1 and it works like a charm.

Anyway, I'm not in a hurry, this is just for testing, I'm still in the early learning stages.

Alexis de Lattre (alexis-via) wrote :

@Ramon

Unfortunately, we do not plan a backport to the 6.0 branch.

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

Other bug subscribers