Lscs comes with a debug panel (actually a REST API) that can be very useful if you need to debug your livesite lscs-queries. The manual is very brief on this section so here some usefull urls and remarks.

http: //server:port/lscs/admin/debugpanel/ [default port is 1876, I believe]

This is the most usefull url which gives you access to lscs-status, -diagnostics, -projectsnames and document query.

With the 'document query' you can query lscs for all metadata stored for a document. F.i. if you enter in field 'q' under 'Metadata Search' a query like 'TeamSite/Templating/DCR/Type:category/type' you will see a list of of dcr's of the dct 'category/type' within the project. Enter '*' in field 'q' and *all* documents will be returned. If you leave the project field empty it will use the first project name a listed under 'List project names'.

http: //server:port/lscs/v1/metadata-info

This returns a list of all known metadata fields with lscs.

http: //server:port/lscs/v1/document/path/sites/mysite/default.site?project=myproject

This returns the document (e.g. file contents, NOT the metadata) from the path (in the workarea) sites/mysite/default.site from myproject. Again you can leave the project out to query the default project.

Now, with this info read the manual again for further details.

Devnet was showing this error all through the weekend (which in a european timezone includes the monday morning!). Would somebody at Interwoven be aware of this?

New in Teamsite 7.2 is the "Globalized Content Manager" which is a marketing name for the long waiting support for localisations and translations. From the 7.2 manual:

"With TeamSite's Globalized Content Management (GCM) solution, site authors, owners, and editors can quickly and easily launch a Web site into different markets on an international basis and then maintain the family of localized sites. Using ContentCenter Professional, an author can initiate the localization process for a Web site and then monitor the progress of that localization effort."

The idea behind the tool is that every file (.page, dcr, site(-map), ...) has a master 'copy' and 0 or more localised 'copies'. Teamsite manages the relation between them and can thus 'manage' the translation (e.g. take action when a master-copy is updated so that the change is propagated to the localised copies). The localised version are stored with the locale in the name or directory path.

Each localised site has it own site-map and every localised page must be created and updated by the content editor. This is a crucial remark. The localised version of the page is NOT generated at request time but MUST be created beforehand. There is not fallback to default language mechnism. I am not sure which mechanism I like best.

See chapter 14 of the "ContentCenter Professional User Guide Version 7.2" for more detail.