* Fix Firefox MFA login error by adding logic that checks for the Firefox edge
case where redirect_with_hash returns a Response object rather than a string
* Add test case for this scenario
Includes:
- Normal migration steps.
- Usage of brand new `_inherit = "base"` in Odoo 10, which implies
removing a lot of monkey-patching code.
- Log a warning when multiple matches are found.
* Fix wrong README format.
* [FIX][base_import_match] Avoid UnicodeEncodeError.
When the model or field you chose was translated and had some non-ascii
character, you got an error like this: `UnicodeEncodeError: 'ascii' codec can't
encode character u'\xed' in position 15: ordinal not in range(128)`.
Now, using unicode strings, that won't happen again.
* Do not require a hidden field.
* Further unicode protection, add ondelete clause.
By default, when importing data (like CSV import) with the ``base_import``
module, Odoo follows this rule:
1. If you import the XMLID of a record, make an **update**.
2. If you do not, **create** a new record.
This module allows you to set additional rules to match if a given import is an
update or a new record.
This is useful when you need to sync heterogeneous databases, and the field you
use to match records in those databases with Odoo's is not the XMLID but the
name, VAT, email, etc.
After installing this module, the import logic will be changed to:
1. If you import the XMLID of a record, make an **update**.
2. If you do not:
1. If there are import match rules for the model you are importing:
1. Discard the rules that require fields you are not importing.
2. Traverse the remaining rules one by one in order to find a match in
the database.
1. If one match is found:
1. Stop traversing the rest of valid rules.
2. **Update** that record.
2. If zero or multiple matches are found:
1. Continue with the next rule.
3. If all rules are exhausted and no single match is found:
1. **Create** a new record.
2. If there are no match rules for your model:
1. **Create** a new record.
Without this sudo get_param would fail when the first user reading a parameter that has changed in the configuration file does not have write access to system parameters.
* [ADD] possibility to deactivate users not found in ldap while populating
* [IMP] search in ldap for every possibly unknown user to be really sure it
actually is not present there
* [FIX] refactoring mistake
* [IMP] don't use self.query() to be sure to be stopped if any error occurs
* [IMP] remove superfluous check as exceptions are not supressed any more
* [FIX] typo in variable name
[FIX] handle unicode characters in search filter
[FIX] search for user's login, not her name
* [FIX] don't pass user_name as assertion_value
* [FIX] don't deactivate users if we got a non-existent ldap configuration
* [FIX] flake8
* [FIX] more flake8
* [FIX] make form usable
* [FIX] name clash between function and field
* [ADD] test
[FIX] Updated travis postgresql version
[FIX] Updated phantom_js version in travis
[FIX] Configured travis to run tests for this module in isolation mode
[FIX] Configured travis to run tests for this module in isolation mode
[FIX] Added group to demo_user for test purposes
[FIX] Changed waiting condition on Phantom JS test
[FIX] Removed Travis configuration for isolated test environment
[FIX] Changed waiting condition in phantom_js test
[FIX] Changed target action in phantom_js test
[FIX] Changed target action in phantom_js test
Dave Lasley
Daniel Reis
OCA Git Bot
Oleg Bulkin
Pedro M. Baeza
Jairo Llopis
OCA Transbot
cubells
Jairo Llopis
Moisés López
Jairo Llopis
Stéphane Bidoul (ACSONE)
Guewen Baconnier
Benjamin Willig
Simone Orsi
Holger Brunn
sebalix
Roberto Fichera
Sylvain LE GAL
David Vidal
antonio
Stefan Rijnhart