Labels

accessibility (2) ADF (1) archiver (3) cmu (1) contributor (13) cookie (1) DAM (3) date (3) download (3) dynamic list (4) ephox (5) fatwire (1) fck (1) filters (1) folders (4) headers (2) IBR (3) ImageAlchemy (3) java (4) javascript (2) layout/template (4) link (6) locale (2) multilingual (1) rendition (3) replicator (4) rules (1) schema (1) search (11) sites (1) sitestudio (24) ssp/sspu (5) SSUrlFieldName (2) stellent (4) timezone (1) urm (1) weblogic (1) workflow (2)

Monday, 5 December 2011

OracleTextSearch: sorting by multiple fields = multiple problems

OracleTextSearch mangles the multi-sorting functionality of UCM search results. The MultiSort or SearchSortOptions components won't work, I don't know if there are newer versions that will. But the ability to sort on multiple fields is still possible, read on to figure out how to do it.

Tuesday, 8 November 2011

Tinkering with the search query

Sometimes the search query isn't enough. Sometimes the administrator needs to add a few restrictive clauses or maybe inject some SQL to tweak the results. Content Server is very careful about tidying up search strings which means that modifying search behaviour is not something that can be done with Idoc. But access points do exist that provide a safe way to unobtrusively alter the query.

Thursday, 29 September 2011

Multilingual Websites

A few years ago I wrote a system that produced multilingual websites in UCM. I was asked about it recently so I thought I'd talk about the solution here.

Tuesday, 30 August 2011

Static Publish of Query String URLs & Dynamic Pages

The Site Studio Publisher (SSP) and the pre-11g versions (SSPU) are tools that take your virtual dynamic SiteStudio website and convert it into a bunch of fair-dinkum files. This does mean that all "dynamic" functionality is lost, including any query string variables in the URL. But there actually is a way for SSP to produce multiple pages from a URL query string.

Wednesday, 3 August 2011

The Secret to Unlimited Search Results

The Content Server search results can't go past the first 200 items. This frustrates users and developers. By comparison, Google reports millions of results. Why does UCM, with potentially millions of content items, stop at 200? The answer is that just because the interface stops, you don't have to as well.