3 users online. Create an account or sign in to join them.Users

Search

I know there is a technical focussed thread about the google custom search engine extension, but am interested in some real-world symphony user cases;

The different options as I understand;

  • cse the free version with the limitation of max 10 results
  • sitesearch the commercial version , same feats but more results
    they both get their data by crawling your site

  • commercesearch sitesearch but for webshops; (starting at $50K …) an on-site search engine (hosted by google) serving as a frontend to enable customers to find what they want under 8 seconds, because your real webshop doesn’t offer good usability.
    The data is get from uploading xml to merchant center the google base for products.

Now I wonder if a good new shop design really needs commercesearch at all… With good I mean;

  • inspired by commercesearch ui
  • using cse
  • featuring synonym search

And why isn’t there a free option (like cse) for small webshops. I would love to skip my symphony frontend alltogether and only use the commercesearch as my webshop (fed by symphony xml data)

I use sitesearch on Public Culture. The XML search results are pulled into a Dynamic XML data source and then styled appropriately. You can see a sample search results page here.

@czheng
So indeed the only bonus for sitesearch over cse is unlimited results? Or also immediate indexing?

I don’t believe you can get XML results with cse…

Hm.. confused… Doesn’t the gcse-extension work with xml? Does it use cse or ajax?

This extension uses Google AJAX API for non-javascript environments to get search results and add them to XML.

this is a site using csee.

I think the standard(free) GCSE only offers an AJAX-based result. I think this has changed in the past few years; I seem to remember getting XML from GCSE in the past.

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.2 or above
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.0 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details