1. 29 Oct, 2020 6 commits
    • Jérome Perrin's avatar
      content_translation: Also index translations from message catalogs · f14811fa
      Jérome Perrin authored
      Now that we are able to search using content translation, we also want
      to extend this so that columns like "group__title" can be searchable in listboxs,
      but categories are usually translated with `erp5_content`, which was not indexed
      in content_translation table.
      
      Extend content translation indexing to also support translations coming from
      Localizer catalog make this possible.
      
      The only limitation I could think of is that categories will need to be reindexed
      when the messages are modified in catalog.
      f14811fa
    • Jérome Perrin's avatar
      ERP5Catalog/content_translation: support translated related keys · aee8bcac
      Jérome Perrin authored
      Translated properties are indexed in content translation table,
      so nothing prevent us from using them in related keys. Since in
      many places we show to user translated titles in relations, it
      makes sense to also support searching and sorting in catalog.
      
      This extends related keys syntax only for the newest syntax, so
      related keys like `source__translated__title=X` would allow searching
      for document who have a source relation to a document with title X.
      
      Since any properties can be translated, if for example a property
      `foo` would exist and be translatable, it would be possible to search
      using `source__translated__foo=X`
      
      This is only available when content_translation business template
      is installed.
      aee8bcac
    • Vincent Pelletier's avatar
      ERP5Type.patches.CookieCrumbler: Fix balancer cookie logic. · 0732d589
      Vincent Pelletier authored
      Ever since the introduction of X-Balancer-Current-Server in SlapOS
      haproxy configuration in:
        commit c7f104fbf1f5948928f5545286afbb94fc39102b
        Author: Cédric Le Ninivin <cedric.leninivin@tiolive.com>
        Date:   Tue May 26 13:27:33 2015 +0200
      
            erp5_cluster: leave ERP5 set the haproxy cookie
      
      the balancer will overwrite this cookie's value, so do not compare it
      to our name: balancer may be calling us a name completely unrelated to
      the value getCurrentNode returns.
      So simplify this function's logic to only do what the docstring says:
      decide when to set and when to unset the balancer cookie, and let the
      balancer decide the value.
      This resolves cases where Zope would set the cookie over and over on
      every request when getCurrentNode and balancer disagree on its value.
      0732d589
    • Vincent Pelletier's avatar
    • Jérome Perrin's avatar
      erp5.util: Release erp5.util (0.4.69) · 9d32ef3a
      Jérome Perrin authored
      9d32ef3a
    • Jérome Perrin's avatar
      Testnode environment variables and log URL · 0a2145dd
      Jérome Perrin authored
      - use environment variables to pass SLAPOS_TEST_LOG_DIRECTORY and SLAPOS_TEST_SHARED_PART_LIST, as discussed on nxdtest!2
      - Fix #20200514-218C705 - [testnode] frontend for log access
      
      See merge request !1304
      0a2145dd
  2. 28 Oct, 2020 9 commits
  3. 27 Oct, 2020 5 commits
  4. 26 Oct, 2020 2 commits
  5. 22 Oct, 2020 4 commits
  6. 20 Oct, 2020 2 commits
  7. 19 Oct, 2020 7 commits
  8. 15 Oct, 2020 3 commits
  9. 14 Oct, 2020 2 commits
    • Jérome Perrin's avatar
      pdm: show default supply quantity unit on resource · e0528922
      Jérome Perrin authored
      Now that this is supported, make it available also for default sales,
      purchase or internal supply lines directly on resources. Until now,
      this was only available on supply line view.
      e0528922
    • Jérome Perrin's avatar
      pdm: support defining price in another quantity unit · 3b0e01ed
      Jérome Perrin authored
      So far price were always assumed to be defined in the default
      quantity unit of the resource, even though supply lines had a
      quantity unit field, it was ignored. But it can be useful to
      define prices using another quantity unit than the default quantity
      unit of the resource, for example when a resource is purchased
      in kg but managed in m³.
      
      To support such scenario, we adjust the priced quantity unit
      when applying price.
      3b0e01ed