OCA
/
server-tools
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1251 Commits
13 Branches
0 Tags
45 MiB
Tree: 1329206100
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1329206100'
${ noResults }
server-tools/auth_supplier/README.rst

79 lines
2.2 KiB
Raw Normal View History

[MIG][9.0][auth_supplier] Migrate. (#434) * [ADD] auth_supplier: New Module. * [ADD] auth_supplier: New Module. * [FIX] auth_supplier: Change author order. * [MIG][9.0][auth_supplier] Migrate. Update to v9, with mostly cosmetic changes. * Update XML tags. * Inform about the need to have technical features enabled. * Don't assume website is installed. * Add known issue
9 years ago
​
​
​
​
​
​
​
[9.0][FIX][auth_supplier] Right permissions. (#440) * [9.0][FIX][auth_supplier] Right permissions.
9 years ago
[9.0][IMP][auth_supplier] Remove useless group. Mark as customer. The whole purpose of this module was to be able to separate a customer and a supplier portals. Given the status of the upstream implementations of portals, it is not possible to have a supplier portal without portal permissions. Thus, it would be required to make the group this module was creating inherit from `base.group_portal`, which would give suppliers access to all customers portal. As such, that group becomes useless. From now on, this distinction should be made with simply checking if `user.customer` or `user.supplier` is `True`. This means no additional problems since `ir.rule` domains can use the `user` variable. To allow that, I'm implementing what was discussed at https://github.com/OCA/server-tools/pull/434#discussion-diff-64883758. Tests had to be removed because https://github.com/odoo/odoo/issues/12237 makes the created record to disappear, so there's no way to actually check the created user was created with customer or supplier flag on.
9 years ago
​
[MIG][9.0][auth_supplier] Migrate. (#434) * [ADD] auth_supplier: New Module. * [ADD] auth_supplier: New Module. * [FIX] auth_supplier: Change author order. * [MIG][9.0][auth_supplier] Migrate. Update to v9, with mostly cosmetic changes. * Update XML tags. * Inform about the need to have technical features enabled. * Don't assume website is installed. * Add known issue
9 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
[9.0][FIX][auth_supplier] Right permissions. (#440) * [9.0][FIX][auth_supplier] Right permissions.
9 years ago
[9.0][IMP][auth_supplier] Remove useless group. Mark as customer. The whole purpose of this module was to be able to separate a customer and a supplier portals. Given the status of the upstream implementations of portals, it is not possible to have a supplier portal without portal permissions. Thus, it would be required to make the group this module was creating inherit from `base.group_portal`, which would give suppliers access to all customers portal. As such, that group becomes useless. From now on, this distinction should be made with simply checking if `user.customer` or `user.supplier` is `True`. This means no additional problems since `ir.rule` domains can use the `user` variable. To allow that, I'm implementing what was discussed at https://github.com/OCA/server-tools/pull/434#discussion-diff-64883758. Tests had to be removed because https://github.com/odoo/odoo/issues/12237 makes the created record to disappear, so there's no way to actually check the created user was created with customer or supplier flag on.
9 years ago
[MIG][9.0][auth_supplier] Migrate. (#434) * [ADD] auth_supplier: New Module. * [ADD] auth_supplier: New Module. * [FIX] auth_supplier: Change author order. * [MIG][9.0][auth_supplier] Migrate. Update to v9, with mostly cosmetic changes. * Update XML tags. * Inform about the need to have technical features enabled. * Don't assume website is installed. * Add known issue
9 years ago
​
​
​
​
​
​
​
​
​
​
[9.0][IMP][auth_supplier] Remove useless group. Mark as customer. The whole purpose of this module was to be able to separate a customer and a supplier portals. Given the status of the upstream implementations of portals, it is not possible to have a supplier portal without portal permissions. Thus, it would be required to make the group this module was creating inherit from `base.group_portal`, which would give suppliers access to all customers portal. As such, that group becomes useless. From now on, this distinction should be made with simply checking if `user.customer` or `user.supplier` is `True`. This means no additional problems since `ir.rule` domains can use the `user` variable. To allow that, I'm implementing what was discussed at https://github.com/OCA/server-tools/pull/434#discussion-diff-64883758. Tests had to be removed because https://github.com/odoo/odoo/issues/12237 makes the created record to disappear, so there's no way to actually check the created user was created with customer or supplier flag on.
9 years ago
​
[MIG][9.0][auth_supplier] Migrate. (#434) * [ADD] auth_supplier: New Module. * [ADD] auth_supplier: New Module. * [FIX] auth_supplier: Change author order. * [MIG][9.0][auth_supplier] Migrate. Update to v9, with mostly cosmetic changes. * Update XML tags. * Inform about the need to have technical features enabled. * Don't assume website is installed. * Add known issue
9 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
  1. .. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg
  2. :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
  3. :alt: License: AGPL-3
  5. =============
  6. Auth Supplier
  7. =============
  9. This module was written to extends the functionality of auth signup and allows
  10. the user to create an account as a supplier or customer, marking his related
  11. created partner as such.
  13. Configuration
  14. =============
  16. To enable users to create accounts:
  18. * *Developer mode* should be activated first to have access to technical features.
  19. * Go to *Settings > General settings*.
  20. * Enable *Allow external users to sign up*.
  21. * Enable *Activate the customer portal*.
  23. Usage
  24. =====
  26. To use this module, you need to:
  28. * Log out.
  29. * If you have a website, in home page press *Sign in*.
  30. * Press *Sign up* to go to `the sign up page </web/signup>`_.
  31. * Select *Supplier* or *Customer* in account type.
  32. * Fill the form.
  34. .. image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas
  35. :alt: Try me on Runbot
  36. :target: https://runbot.odoo-community.org/runbot/149/9.0
  38. Known issues / Roadmap
  39. ======================
  41. * If you have nothing in the portal, the user will be redirected to an empty
  42. page.
  43. * Tests are not possible due to https://github.com/odoo/odoo/issues/12237.
  44. They should be added when that is fixed.
  46. Bug Tracker
  47. ===========
  49. Bugs are tracked on `GitHub Issues
  50. <https://github.com/OCA/server-tools/issues>`_. In case of trouble, please
  51. check there if your issue has already been reported. If you spotted it first,
  52. help us smashing it by providing a detailed and welcomed feedback.
  54. Credits
  55. =======
  57. Contributors
  58. ------------
  60. * Rafael Blasco <rafabn@antiun.com>
  61. * Pedro M. Baeza <pedro.baeza@serviciosbaeza.com>
  62. * Carlos Dauden <carlos@incaser.es>
  63. * Sergio Teruel <sergio@incaser.es>
  64. * Jairo Llopis <jairo.llopis@tecnativa.com>
  66. Maintainer
  67. ----------
  69. .. image:: https://odoo-community.org/logo.png
  70. :alt: Odoo Community Association
  71. :target: https://odoo-community.org
  73. This module is maintained by the OCA.
  75. OCA, or the Odoo Community Association, is a nonprofit organization whose
  76. mission is to support the collaborative development of Odoo features and
  77. promote its widespread use.
  79. To contribute to this module, please visit https://odoo-community.org.