Skip to content
Snippets Groups Projects
  1. Sep 06, 2016
  2. Sep 02, 2016
    • Denis Vermylen (dve)'s avatar
    • Martin Trigaux's avatar
      [FIX] all: remove external ids fakely from base · 11812b0b
      Martin Trigaux authored
      Several modules defines records with the external ID `base.foo_bar` while it is
      created inside this module (typically menus and groups).
      While there is no technical reasons to do so but this may introduce issues:
      
      - these records will not be deleted during uninstall
      - if a language is loaded before the installation of the module, it won't be
        translated
      
      The uninstallation will only remove the records with an external id linked to
      this module (these would only be removed when removing base).
      
      Installing a language before the module will drop the translations not linked
      to an existing external id (as it can not be resolved).
      
      This commit correct all the external ids tagged as from base or other incorrect
      modules.
      11812b0b
  3. Sep 01, 2016
    • Damien Bouvy's avatar
      [IMP] website_sale: allow saving card data from checkout · d9c9d0c9
      Damien Bouvy authored
      Instead of having to register a card then do a payment, a little
      checkbox during the checkout process is usually simpler.
      d9c9d0c9
    • Damien Bouvy's avatar
      [IMP] website_(portal_sale|sale|quote), payment: add authorization payment flow steps · a2d249f1
      Damien Bouvy authored
      This allows using a modern e-commerce flow where amounts are first
      authorized at checkout then captured when the picking is in fact
      shipped instead of immediately capturing the amount.
      
      To access this flow, a new selection value is available on the payment
      acquirer: "Authorize the amount and confirm the SO on acquirer
      confirmation". If this value is selected, s2s/form transactions should
      only require authorization to the acquirer; the user can then
      capture/void the payment manually from the Odoo backend transaction
      form view by simply using buttons.
      a2d249f1
  4. Aug 31, 2016
  5. Aug 30, 2016
  6. Aug 29, 2016
  7. Aug 26, 2016
  8. Aug 22, 2016
    • Martin Geubelle's avatar
      [ADD] product,website_sale: attribute without variant · b94ddcbd
      Martin Geubelle authored
      A new field `create_variant` has been added on `product.attribute`.
      If unchecked, the attribute will not create variant.
      
      These attributes will be added on the sale order description if bought from the shop.
      The lines of a product with these attributes will be splitted to keep the description.
      b94ddcbd
  9. Aug 19, 2016
  10. Aug 11, 2016
  11. Aug 08, 2016
  12. Aug 05, 2016
  13. Aug 01, 2016
  14. Jul 30, 2016
  15. Jul 28, 2016
    • Jeremy Kersten's avatar
      [FIX] website_sale: fix new checkout display · 5f868f5e
      Jeremy Kersten authored
      Fix "Remove cart line button isn't a proper link"
      Fix "col-md for title (Billing Address, Shipping Address) where 'The underline of the title stops too early'
      Fix "First load from adress, display zip/city in right order to avoid flickering if zip/city instead of city/zip
      Fix "Select the billing address as the shipping after edit the billing address from the shipping list"
      Fix "Disable the selection of address in checkout while in edit mode"
      Fix "Fix validation of the extra checkout step: 'extract_data got an exepected keyword argument'
      5f868f5e
  16. Jul 18, 2016
  17. Jul 05, 2016
  18. Jul 04, 2016
    • Jeremy Kersten's avatar
    • Jeremy Kersten's avatar
      [ADD] website_sale: checkout process · e4a317a1
      Jeremy Kersten authored
      Change checkout process.
      
      - Billing address is always the connected partner_id or neww partner_id.
      - Shipping address is contact of current commercial_partner_id
      - New checkout design for address selection
      - Add delete a line in my cart
      - Fix input quantity size
      - Refactor/Reindent xml template from website_sale
      - Improve the modularity for checkout (preprocess, posprocess, required fields, ...)
      - Allow to use form builder in extra step for OEE (No edit mode)
      - Add route to have states according country selected (need to be overridable for website_sale_delivery)
      - ...
      e4a317a1
  19. Jun 23, 2016
  20. Jun 17, 2016
    • Jeremy Kersten's avatar
      [IMP] website_sale: B2B-B2C - display price with or without taxes. · 3834a894
      Jeremy Kersten authored
      Allow to display price on the website tax included or not.
      
      Price for product is computed with a new function display_price
      which one compute an estimated price based on taxex and fiscal
      position of the current partner for the current product.
      
      Once the product is in the cart, it is the behaviour of previous commit
      odoo/odoo@5f5f8d8 which is used to diplay price with or without taxes.
      3834a894
    • Jeremy Kersten's avatar
      [IMP] sale: allow to show total of order line tax inc or based on unit price. · 5f5f8d8e
      Jeremy Kersten authored
      Allow to set in configuration mode b2b or b2c.
      Change the column of order line in sale view and in reports depending of sale.
      
      Fix price_reduce field (wrong if tax was included in price)
      and merge with code discounted_price from website_sale.
      
      Change header from reports "Price Tax Excluded' by 'Price' in report.
      That is wrong, sometime the amount can haxe tax included in the price.
      5f5f8d8e
    • Joren Van Onder's avatar
      [IMP] payment: add options to automatically confirm SO's through website · 8a761721
      Joren Van Onder authored
      Introduces two new options:
      - confirm_so: to confirm the sale order on acquirer confirmation
      - generate_and_pay_invoice: confirm_so + generation of invoice and
                                  payment registration
      8a761721
  21. Jun 14, 2016
  22. Jun 09, 2016
    • Yannick Tivisse's avatar
      [IMP] base,sales_team: Move res_groups and menuitems to sales_team · 9e571854
      Yannick Tivisse authored
      Purpose:
      Having the res_group defined in base and sales_team auto installed
      with mail doens't make sense.
      
      - Move the empty res_config class and the related view from
        base_setup to sales_team (base_setup only contains the 'General Settings'
        model and views
      - Move the 'sale' related content from product to sale module (Access rights,
        menuitems,...)
      - Set sales_team at autoinstall False. The module is installed when needed by
        crm or sale for example
      - Set sales_team as a dependency of voip. (Access rights defined for configuration
        purpose)
      - Set sales_team ad a dependency of subscription (Access rights issue too)
      
      [FIX] account: move some ir.model.access to sale module
      [FIX] payment: Move some ir.rule to website_sale
      [FIX] stock: move some ir.model.access rule to sale_stock
      [FIX] project: Move some ir.model.access rules to crm_project_issue
      [FIX] mrp: Move some ir.model.access rules to sale_mrp
      [FIX] calendar: move some ir.model.access rules to crm
      
      Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes
      sales_team.group_sale_manager.
      
      [ADD] sales_team: See own documents => See only his sales team
      Moved the "User: Own Leads Only", "User: All Leads" and "Manager" groups from sale and crm
      into sales_team module. Add the record rules so that user can see only his Own Sales Team
      if "See Own Leads" is sales right and can see all sales teams if he is having sales rights
      of "See All Leads" or manager.
      9e571854
  23. Jun 06, 2016
    • Yannick Tivisse's avatar
      Revert "[IMP] base,sales_team: Move res_groups and menuitems to sales_team" · ccdb5cbf
      Yannick Tivisse authored
      This branch need more testing instead of doing 10 fixes. A lot of issues are occuring
      when installing modules in different orders.
      
      This reverts commit fa6e415c.
      ccdb5cbf
    • Yannick Tivisse's avatar
      [IMP] base,sales_team: Move res_groups and menuitems to sales_team · fa6e415c
      Yannick Tivisse authored
      Purpose:
      Having the res_group defined in base and sales_team auto installed
      with mail doens't make sense.
      
      - Move the empty res_config class and the related view from
        base_setup to sales_team (base_setup only contains the 'General Settings'
        model and views
      - Move the 'sale' related content from product to sale module (Access rights,
        menuitems,...)
      - Set sales_team at autoinstall False. The module is installed when needed by
        crm or sale for example
      - Set sales_team as a dependency of voip. (Access rights defined for configuration
        purpose)
      - Set sales_team ad a dependency of subscription (Access rights issue too)
      
      Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes
      sales_team.group_sale_manager.
      fa6e415c
Loading