1. 08 Jan, 2020 3 commits
  2. 07 Jan, 2020 8 commits
  3. 30 Dec, 2019 3 commits
  4. 28 Dec, 2019 3 commits
  5. 27 Dec, 2019 2 commits
  6. 26 Dec, 2019 15 commits
  7. 25 Dec, 2019 6 commits
    • Arnaud Fontaine's avatar
      ZODB Components: Preparation of erp5_base migration from FS: Fix pylint... · 42999daf
      Arnaud Fontaine authored
      ZODB Components: Preparation of erp5_base migration from FS: Fix pylint undefined-variable errors: Remove dead code.
      
      keywordsplitter() has never been defined so this code has been broken
      since its introduction.
      42999daf
    • Arnaud Fontaine's avatar
      ZODB Components: Preparation of erp5_base migration from FS: Fix pylint... · ba9baeb7
      Arnaud Fontaine authored
      ZODB Components: Preparation of erp5_base migration from FS: Fix pylint undefined-variable errors: get_transaction() removed in ZODB 3.6.
      ba9baeb7
    • Arnaud Fontaine's avatar
      ZODB Components: Preparation of erp5_base migration from FS: Fix pylint... · 2c8868fe
      Arnaud Fontaine authored
      ZODB Components: Preparation of erp5_base migration from FS: Fix pylint undefined-variable errors: ResourceLockedError.
      2c8868fe
    • Arnaud Fontaine's avatar
    • Jérome Perrin's avatar
      Improve read only HTML · d296f504
      Jérome Perrin authored
      We receive feedback from users saying that "when I view a mail message in event module, I see ugly html source", this was because user had set preferred text editor to monaco. Improve a bit monaco integration so that we display something better than code in a `<pre>`  for non editable editors.
      
      We had another feedback that when using CKEditor as preferred text editor in old UI, users can not click on links when viewing an html Mail Message. But it works in new UI. I did something minimal so that this looks working until the migration to new UI is complete.
      
      /reviewed-on nexedi/erp5!1011
      d296f504
    • Jérome Perrin's avatar
      renderjs_ui: "Touch" cache manifest in Post-Upgrade · 3eafdf3f
      Jérome Perrin authored
      With the current architecture of cache manifest, it was required that
      developpers change the cache manifests referencing a web page every time
      they change a web page. In practice, developers were never doing this,
      so we sometimes had issues where client keep using old version of
      website even though a new version has been deployed, when after
      deployment we did not change the cache manifest.
      
      To automate the scenario of modifying the cache manifest, introduce a
      post-upgrade constraint that will check that the manifest is newer than
      all of the referenced pages. If that's the case, the constraint can fix
      by modifying the manifest content, which also changes the modification
      date of the manifest, which might be used in "if-modified-since"
      negociations.
      
      According to spec [1], cache manifest is updated if the HTTP responses
      is not "304 not modified" and if the manifest content is not
      byte-for-byte identical to the previously cached version.
      
      [1] https://www.w3.org/TR/2008/WD-html5-20080122/#updating1
      
      /reviewed-on nexedi/erp5!1009
      3eafdf3f