Skip to content
Snippets Groups Projects
  1. Sep 06, 2016
  2. Sep 05, 2016
  3. Sep 02, 2016
  4. Aug 30, 2016
    • Thibault Delavallée's avatar
      [IMP] tools: sanitizer: add and clean sanitize options · 02c748be
      Thibault Delavallée authored
      Now having
      
       * sanitize: run the sanitizer to clean the html (removing javascripts,
         unwanted tags, ...)
       * sanitize_tags: only a subset of tags is allowed in html content.
         Unwelcomed tags are remove dand their content stripped.
       * sanitize_attributes: only a subset of attributes is allowed.
       * sanitize_style: only a subset of style attributes is allowed. Style
         attributes are parsed to keep only a white list.
       * strip_style: all style is removed. It bypasses sanitize_style as there
         is no need to sanitize something that is removed.
       * strip_classes: remove class attributes
      
      Fields parameters have also been updated to match the sanitize options. Html
      fields by default are sanitized with sanitize_tags activated but without any
      further options. All addons have been updated to match the new options
      according to their previous behavior.
      02c748be
  5. Aug 29, 2016
  6. Aug 26, 2016
  7. Aug 22, 2016
  8. Aug 21, 2016
  9. Aug 19, 2016
  10. Aug 18, 2016
  11. Aug 14, 2016
  12. Aug 10, 2016
  13. Aug 05, 2016
  14. Aug 04, 2016
  15. Jul 31, 2016
  16. Jul 26, 2016
  17. Jul 24, 2016
  18. Jul 19, 2016
    • qsm-odoo's avatar
      [FIX] *: use html_translate for non-sanitized html fields · 7aa9f239
      qsm-odoo authored
      Commit c21568e1 deactivated the sanitization of frontend html fields so
      that their modification through the editor worked again. However,
      this broke the possibility to display their traduction and to modify
      them.
      
      The problem is that the translate option of html fields should not
      equal "True" but instead be the html_translate function defined in
      openerp.tool.translate. The translate=True option is automatically
      change in html_translate though but there is a condition: the field
      should be sanitized, which is why this broke since the sanitization
      is disabled.
      
      This commit sets the translate option of non-sanitized html fields
      to html_translate. Maybe we should investigate for this to be automatic
      for non-sanitized html fields as well.
      
      Thanks to @rco-odoo.
      7aa9f239
    • Odoo Translation Bot's avatar
  19. Jul 17, 2016
  20. Jul 11, 2016
    • qsm-odoo's avatar
      [FIX] *: html fields sanitization · c21568e1
      qsm-odoo authored
      Since commit c9e38cae in saas-10, the html fields are sanitized in
      strict mode by default. This breaks all html fields behaviour when it
      is editable in the website editor.
      
      This commit deactivate the sanitization for such HTML fields (like it
      was already the case for blogs contents or products descriptions for
      example). A more specific sanitization will be implemented in future
      versions.
      c21568e1
  21. Jul 10, 2016
  22. Jul 05, 2016
  23. Jul 03, 2016
  24. Jun 30, 2016
    • Yannick Tivisse's avatar
      [IMP] Classified each module in its category to display them correctly on odoo/apps · 692d41c6
      Yannick Tivisse authored
      To be displayed correctly on odoo app (In a given category and not only in all or hidden)
      the module category in the __openerp__.py file should be one of these:
      
          "Accounting",
          "Discuss",
          "Document Management",
          "eCommerce",
          "Human Resources",
          "Industries",
          "Localization",
          "Manufacturing",
          "Marketing",
          "Point of Sale",
          "Productivity",
          "Project",
          "Purchases",
          "Sales",
          "Warehouse",
          "Website",
          "Extra Tools",
      
      'Accounting & Finance' will not work, as 'Project Management', ...
      692d41c6
  25. Jun 26, 2016
Loading