lp:~akretion-team/partner-contact-management/base-location-geonames-import

Branch merges

Propose for merging

No branches dependent on this one.

Ready for review for merging into lp:~partner-contact-core-editors/partner-contact-management/7.0

Lorenzo Battistini (community): Needs Resubmitting on 2014-07-23

Nicolas Bessi - Camptocamp (community): Needs Fixing on 2014-04-11

Diff: 437 lines (+400/-0)

7 files modified

base_location_geonames_import/__init__.py (+23/-0)
base_location_geonames_import/__openerp__.py (+47/-0)
base_location_geonames_import/i18n/base_location_geonames_import.pot (+68/-0)
base_location_geonames_import/i18n/fr.po (+68/-0)
base_location_geonames_import/wizard/__init__.py (+23/-0)
base_location_geonames_import/wizard/geonames_import.py (+127/-0)
base_location_geonames_import/wizard/geonames_import_view.xml (+44/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

44. By Alexis de Lattre on 2014-06-11

[MERGE] merge with trunk revno 40.

43. By Alexis de Lattre on 2014-06-02

Remove France-specific code ; moved to new module l10n_fr_base_location_geonames_import on lp:openerp-french-localization

42. By Alexis de Lattre on 2014-04-11

Add a FOR UPDATE NOWAIT at the beginning of the transaction.

41. By Alexis de Lattre on 2014-04-11

Insist on the fact that the wizard deletes current better zip entries in the module description and in the wizard itself.
Better error message when the country code inside the file is wrong.

40. By Alexis de Lattre on 2014-04-07

Allow to skip entries in the _prepare method.

39. By Alexis de Lattre on 2014-04-07

Add support for states (if states are already present in res.country.state).
Add POT file and FR translation.

38. By Alexis de Lattre on 2014-03-30

Add module base_location_geonames_import

37. By Sandy Carter (http://www.savoirfairelinux.com) on 2014-03-21

Adapt user form to look like partner form
* Name field replaced by Firstname and Lastname

36. By Joao Alfredo Gama Batista on 2014-03-21

[MRG][IMP] Adapt user form to display first name and last name like partner form

35. By Jonathan Nemry (Acsone) on 2014-03-12

[MRG]

For Partner:

1) Create always the SQL constraint on 'lastname'
2) Better implementation of "_write_name" allowing more intuitive update of the partner name when processing from another model (ex: res_user), i.e., try to keep the firstname if unchanged
3) When duplicating a partner, avoid to repeat the firstname in the name
4) Beautify the inner form for children contacts (placing fields as in the main form)
5) Allow edition of the field name in the inner form if child is a company

For User:

1) Reintegrate the name as "required"
2) When duplicating a user, avoid to repeat the firstname in the related partner name