The Silva Find extension has been renovated to take
advantage of the PDF and Word file fulltext cataloging. It now supports
search by all metadata fields, including those in your custom sets. The
search and result views can be extensively customized. Silva Find is
included in the silva-extra tarball.
Many thanks to all who contributed. See HISTORY.txt in the Silva core package for more information about changes in Silva 1.6. For developer-level changes, see doc/developer_changes. Also see the changes in components such as Silva Metadata, External Sources, etc.
In the Silva 1.6 release there are some changes that might affect how
you and your users work. Following are five topics:
In previous Silva versions the published state of a container was
determined by checking whether there was any content in it, or in its
nested containers, that was published. We've changed this so that now
the state of a container is determined solely by its index document. If
the index is published, the folder is published. If the index is not
published, the folder is not published. This brings a significant
performance gain, as it's not necessary to check an entire hierarchy of
content for anything that might be published.
This makes it much easier to unpublish a branch of content in your site;
just close the top index, and the entire branch won't be visible in the
navigation any more. The underlying published content is still
accessible, so if you want to close everything you should do it as
before, via the publish screen.
It could be that you have containers in your site without an index
document. In that case Silva falls back to the old method, and the
container is published if any of its contents are published.
Silva 1.6 has a change in the index items to make them conform to the
XHTML spec. In short, you now have anchors, and you have anchors with
titles which makes them index items. If you want your anchor to show up
in the Indexer, give it a title when editing. See an illustrated
explanation in the documentation:
http://www.infrae.com/products/silva/docs/author_basic/kupu_content_editor#Links_to_named_anchors
Silva 1.6 requires a minor upgrade for this feature. The upgrader will
change all existing index items to XHTML valid anchors with a title.
Many existing index items contain illegal characters, e.g. "Links to
named anchors" has spaces. The upgrader will change the illegal
characters to underscores, which will render so:
<a class="index-element" id="Links_to_named_anchors"></a>
In Kupu the anchor will have a title with spaces: "Links to named
anchors". This is used in the Indexer as the text for the link display.
If there are other illegal characters in your index items, they'll all
become underscores, e.g. "Fermer items publiés" will become
"Fermer_items_publi_s".
You may want to incorporate a base tag into your existing layout
templates. This is a feature from the Silva 1.5.10 release, explained in
detail in the Changes update here:
http://infrae.com/mailman_/pipermail/silva-general/2007-February/001083.html
The default layout macro now includes this base tag:
<base tal:attributes="href here/absolute_url" />
The base tag ensures that anchors will work properly, but it could
affect other things, such as the way forms are submitted.
The Silva TOCs (both the TOC element in a document and the AutoTOC
content type) have a ‘modern’ rendering now. The indent that indicates
the nesting was previously done with images (going back to the Netscape
4 era). The new rendering uses nested lists, which make the rendering
easier to style, and better accessible for screen readers. The lists are
unordered (ul) types and have the class="toc", Thanks to Andy Altepeter
for this feature.
Besides the class on the TOC there is no other default styling. The
browser typically changes the bullet depending on the degree of nesting.
You may need to update your stylesheet to conform to the house style.
Tocs used to display links with a trailing slash, e.g.:
http://www.infrae.com/products/silva/docs/manager/template_design/
This was because, if there is no base tag in the template, Zope
automatically inserts one that includes a trailing slash. If you depend
on the trailing slash for your navigation code, you may need to update
it if you add a base tag as described above, which won't have a trailing
slash.
The css styling of the preview publisher buttons has been changed,
making it easier for template designers to integrate the publisher into
their public layout. It appears in a <div class="publisher"> that can be
positioned more easily.
Mult-language sites can now make use of the language metadata to insert
a lang attribute into the html tag of their layout macro. In the default
layout macro you'll find the following in the html tag:
tal:define="lang python: here.get_metadata_element('silva-extra',
'language') or nothing"
tal:attributes="
lang lang;
xml:lang lang;
If the language field in the metadata is set to German, this will render to:
lang="de" xml:lang="de"
If your site is not multilingual you should make this hard coded and
avoid the call to the metadata for every page view. Just remove the
tal:define and tal:attributes and replace it with:
lang="en" xml:lang="en"
If you have existing layout templates this is probably already the case.
© Copyright 2002-2007 Infrae.
All rights reserved. 
