1. 03 Jul, 2020 6 commits
  2. 02 Jul, 2020 18 commits
  3. 01 Jul, 2020 1 commit
  4. 30 Jun, 2020 4 commits
    • Jérome Perrin's avatar
      SecurityTestCase: generate assertUserCanNot... methods · 1266c706
      Jérome Perrin authored
      the "failIf..." naming scheme is deprecated in unittest, we should at
      least have new-style named methods
      1266c706
    • Jérome Perrin's avatar
      trade: Display tax lines in order printout · b7b5f217
      Jérome Perrin authored
      So far, simulated tax is not included in printed Orders. This allow to include expected tax in vat_list for printout.
      
      This is done using `getPreferredTaxUseList` which is probably wrong and will hopefully be rewritten using more modern technologies (html not odt) and to use base amount, but this allows to make order printout show tax lines again.
      
      See merge request nexedi/erp5!1168
      b7b5f217
    • Jérome Perrin's avatar
      renderjs: update translation data in post-upgrade · a39b74c2
      Jérome Perrin authored
      Firstly, rework a bit the action to create translation data, the action no longer allow choosing the translation data script to update, but uses the one referenced in the translation gadget html.
      
      In post upgrade, compare the actual content of the translation data script with the expected content, calculated from web site languages, data-i18n attributes from referenced pages and Localizer messages.
      
      This makes the requirement that web sites with different configurations for translations need to use different translation gadget stronger, when it's not met post upgrade will always report consistency issues. To address this, modify existing web sites so that they all use different translation gadgets - or at least don't use translation gadget explicitly. 
      
      This was made by:
       - all web sites by default do not have a translation gadget
       - smart_assistant use a dedicated translation gadget, to confirm that using a different translation gadget is possible with an officejs web site, where the translation gadget is defined in the "app" web section.
       - officejs_support_request_ui uses a dedicated translation gadget, because we need this for a customer project and for ourselves.
       - other web sites do not support translation by default, but enabling would be easy: 
          - set the allowed languages on web site
          - create an empty web script ( `{website}_translation_data.js` )
          - create a translation gadget web page ( `{website}_translation.html` ) using same content as `gadget_translation.html`, except that the translation data script should be the one created above ( `{website}_translation_data.js` )
          - configure the web site to use translation gadget in layout properties. In the case of an OfficeJS web site, this should not be set on the web site but on the main web section
          - use "Update Translation Data" action on web site or run post-upgrade step of upgrader.
      
      This revealed problems (page does not load with javascript error) when using different translation gadgets, that were addressed by not pre-loading the default translation gadget.
      
      See merge request nexedi/erp5!1151
      a39b74c2
    • Jérome Perrin's avatar
      Make ERP5JS login pages look like ERP5JS Dialogs · 1833f952
      Jérome Perrin authored
      ![login](/uploads/d270b602f784466dcc8d0806ec0ab9e1/image.png)
      
      ![recover](/uploads/da5bca427e6053a4724a4f7171db71db/image.png)
      
      ![reset password](/uploads/27e3519dfaf96cd66ce3adf9d6184ba8/image.png)
      
      
      See merge request !1165
      1833f952
  5. 29 Jun, 2020 9 commits
  6. 26 Jun, 2020 2 commits