1. 08 Nov, 2014 1 commit
    • use fulltext search in title and description. · d47df833
      * to quickly setup catalog_full_text table, you can use the following SQL.
      
        REPLACE INTO catalog_full_text SELECT uid, title, description FROM catalog;
      
      * non fulltext queries like '=abc', '>abc', '%abc%' are supported.
      
      * now erp5_full_text_mroonga_catalog is used for unit tests thus I recommend using it instead of erp5_full_text_myisam_catalog.
      
      * to migrate existing MyISAM full_text table into Mroonga, you can use the following SQL.
      
        ALTER TABLE full_text DROP KEY SearchableText,
          ENGINE = mroonga,
          ADD FULLTEXT KEY SearchableText (`SearchableText`) COMMENT 'parser "TokenBigramSplitSymbolAlpha"';
      
      * fulltext search score is no longer provided as (column_name) but now provided as (column_name)__score__.
      
      * (category)_title, like source_title, related keys are automatically generated. (category)_description keys as well.
      Kazuhiko Shiozaki committed
  2. 11 Sep, 2014 2 commits
  3. 11 Aug, 2014 1 commit
  4. 30 Jan, 2014 1 commit
  5. 10 Sep, 2013 3 commits
  6. 27 Feb, 2013 1 commit
  7. 15 May, 2012 1 commit
  8. 11 May, 2012 1 commit
  9. 07 Feb, 2012 1 commit
  10. 01 Sep, 2011 2 commits
  11. 30 Aug, 2011 1 commit
  12. 25 Aug, 2011 1 commit
    • Cleanup shacache and shadir restfulness. · b43adf6c
      Follow the specification of shacache and shadir: PUT is used in shadir,
      POST is used in shacache in order to create new content. erp5_web can be used
      without any modification to serve fully restfull POST interface.
      
      Create special action for Web Site which reacts on POST type of request and
      support it by low level functionality. This action is available in web view
      only and affects only Web Sites configured for shacache.
      
      Other changes:
      
       * do not check uploaded content, just return calculated sha
       * break compatibility during upload (better now then later)
       * avoid hiding errors during publishing content by hiding exceptions in
         WebSite_publishDocumentByActivity
       * do randomisation in tests and make them live test safe
       * connect to running web server in tests in order to use all stacks during
         uploading and downloading content
       * cleanup erp5_web_shacache and erp5_web_shadir business templates and remove
         not needed scripts
       * during testing treat running site as blackbox and do not try to be too smart
      Łukasz Nowak committed
  13. 28 Jul, 2011 2 commits
  14. 19 Jul, 2011 1 commit
  15. 18 Jul, 2011 1 commit
  16. 06 Jul, 2011 2 commits
  17. 05 Jul, 2011 6 commits
  18. 04 Jul, 2011 1 commit